Team Rollout

Most teams that use Bloque look the same: ten to fifty people, no IT department, and one person — an operations lead, an office manager, the one who is comfortable with settings screens — who ends up owning the tooling.

That person sets the servers up once. Everyone else gets the same tools in ChatGPT or Claude Desktop without ever configuring a server, and without a single company password being passed around.

Who does what

	The admin	Each team member
MCP servers	Adds and authenticates them once	Never configures a server
Credentials	Enters them once, stored encrypted	Never sees them
API keys	Issues and revokes them	Receives one, never creates one
Setup effort	An afternoon	Paste a URL and a key

1. The admin sets up the servers

Sign up at bloque.run — a Hub is created automatically. Then add the servers the team needs and authenticate each one:

• Add an MCP Server — from the registry, a GitHub URL, or manual connection details
• Authenticate — sign in with OAuth, or enter API keys and other secrets

This is the step that would otherwise be repeated on every laptop in the company. Here it happens once. Credentials are encrypted, isolated to the Hub, and decrypted only at runtime — they are never sent to a member's machine, and a member cannot read them back out.

Before involving anyone else, try the tools in the Playground (Starter plan and above). It is far easier to fix a misconfigured server from the admin screen than through five people reporting that "the AI isn't working".

2. The admin creates a team and invites members

On the Team plan, a Hub is owned by the team rather than by one person, so every member reaches the same servers.

1. Open Teams in the sidebar and create a team. You choose the number of seats, and billing is handled once for the whole team rather than per person.
2. Move the Hub you just configured to the team — team settings has a Hubs tab for transferring an existing Hub, so the setup work from step 1 carries over.
3. Invite members by email from the Invitations tab. Each person gets a link, signs up or signs in, and joins the team. Invitations expire, and you can revoke one that has not been accepted.

Members join as member; other admins join as owner. Only owners can invite people, remove them, or manage the team's API keys.

3. The admin issues a key for each member

On a team-owned Hub, API keys are the owner's job. Members cannot create keys for themselves — the owner creates one for each member, and for themselves, from the team's API Keys tab, choosing who the key belongs to.

That keeps two things true at once. Access to the team's tools is granted deliberately, by a person who knows who should have it; and a key still belongs to exactly one member, so a tool call is recorded against the person whose key made it rather than against a shared identity. The same tab lists every key on the team's Hubs with its owner, its Hub, and when it was last used, and you revoke any of them from there.

A key is shown once, when you create it. Send each person theirs privately — a DM or a password manager, not a shared document.

Each plan caps how many API keys one person can hold, and on the Team plan the cap applies per member, so you can issue someone separate keys for their laptop, their phone, and an automation.

Smaller than a team plan?

For two or three people, an admin can skip teams altogether: create several keys in their own Hub, name each one after its owner, and send them out privately. It works the same way from the client's side. The trade-offs are that the number of keys is capped by plan and every key belongs to the admin's account, so in Logs people are told apart by key name rather than by name and email.

4. Each member connects their client

Members need two things: the endpoint URL and the key you sent them.

URL:           https://mcp.bloque.run/mcp
Authorization: Bearer <their API key>

Walk each person through their client once:

• ChatGPT — added as a custom app; needs Developer mode turned on
• Claude Desktop — a custom connector, also works the same way on claude.ai
• Claude Code · Codex — one command
• Connection Reference — VS Code, Cursor, LM Studio, Dify, n8n

Neither the ChatGPT nor the Claude Desktop flow is hard, but both have a step a non-technical person will not guess. Budget fifteen minutes per person the first time, or do it over a screen share with two or three of them at once. After that it is done — their client keeps working as you change what sits behind it.

5. Running it day to day

Adding a tool later. The admin adds and authenticates the server in Bloque. Members get the new tools the next time their client reconnects — nothing to install, nothing to send around.

Someone joins. Invite them, issue their key, help them connect their client once. They start with exactly the same tools as everyone else.

Someone leaves. Revoke their keys from the team's API Keys tab and remove them from the team. No shared credential has to be rotated, and nobody else is interrupted.

Something breaks. Open Logs and filter by Hub, member, API key, or server. The admin can see the failure without asking anyone to send screenshots, then test the fix in the Playground.

What's next

• Automation — point a scheduled agent at the same Hub
• Shared Hubs — publish a curated set of servers for people who run their own Bloque account
• Execution Boundary — where MCP servers actually run, and what they can reach