Connect your agent

A connected agent searches, reads, writes and comments in one vault of your team over MCP, under its own name and never with more rights than you.

Address and name

MCP address

https://app.pumice.cloud/mcp

Name in your tool

pumice-<team>

The address is the same for every team. You pick the team when you sign in, and the sign-in counts for that team only. So give each team its own entry in your tool: pumice-<team>, where <team> is your team’s short name.

In Pumice, Connect agent (under Settings › Agents) shows every command below with your team filled in. Only owners and admins can connect agents.

Your tool

Every tool ends in the same sign-in in your browser, described below.

Claude Code

  1. Run in a terminal:

    claude mcp add --transport http --scope user pumice-<team> https://app.pumice.cloud/mcp
    claude mcp login pumice-<team>
  2. Your browser opens. Sign in, pick team and vault, click Allow.

Without a browser on the machine (SSH): claude mcp login pumice-<team> --no-browser, open the printed address on your computer and paste the address your browser ends up on back into the terminal.

Codex

  1. Run in a terminal:

    codex mcp add pumice-<team> --url https://app.pumice.cloud/mcp
  2. Codex starts the sign-in on its own. If no browser opens, run:

    codex mcp login pumice-<team>
  3. Sign in, pick team and vault, click Allow.

The Codex CLI and the Codex IDE extension share this entry.

Cursor

  1. In Pumice, open Connect agent, choose Cursor and click Open in Cursor.

  2. Cursor opens its install dialog with the entry for your team. Install it, then sign in to the server in Cursor.

  3. Your browser opens. Sign in, pick team and vault, click Allow.

VS Code

  1. In Pumice, open Connect agent, choose VS Code and click Open in VS Code.

  2. VS Code shows the server with the entry for your team. Install it; on first start VS Code asks whether the server may sign in.

  3. Your browser opens. Sign in, pick team and vault, click Allow.

Pumice then works in GitHub Copilot chat in agent mode.

Claude (web, desktop and mobile)

  1. On claude.ai open Customize › Connectors, click + Add, then Add custom connector.

  2. Name Pumice <team>, address https://app.pumice.cloud/mcp, click Continue. Under OAuth client choose Register automatically, then click Add.

  3. Sign in to Pumice when Claude asks, pick team and vault, click Allow. In a chat, turn Pumice on under + › Connectors.

The connector works in claude.ai and in the Claude desktop and mobile apps. On Team and Enterprise plans an owner adds it under Organization settings › Connectors, then each member clicks Connect. The Free plan allows one custom connector.

ChatGPT

  1. Open ChatGPT Plugins, click +, then Add custom MCP server.

  2. Name Pumice <team>, address https://app.pumice.cloud/mcp, authentication OAuth. Confirm I understand and want to continue and click Create as a plugin.

  3. Sign in to Pumice when ChatGPT asks, pick team and vault, click Allow. In a chat, type @ and pick the plugin.

Whether you can add custom MCP servers depends on your ChatGPT account and workspace settings.

Other tools

  1. Any MCP client that signs in with OAuth (dynamic client registration, PKCE) works with the address https://app.pumice.cloud/mcp. Pumice sends the sign-in back only to your own computer (127.0.0.1, localhost) or to the known addresses of the tools above.

  2. An agent without a browser (CI, a server, a script) uses a key instead: Connect agent, then Without a browser: connect with a key. It sends the key as Authorization: Bearer <key>.

Sign-in and team

The first call opens Pumice in your browser. Sign in if you are not signed in yet.

If you belong to several teams, Pumice asks Which team? first. The next page shows which tool is asking and where the sign-in returns to. Pick the vault, keep or change the agent’s name (suggested from the tool, for example claude-code) and click Allow. If you connect the same tool again, for example on a second computer, Pumice suggests the same agent and keeps using it.

The tool gets an access token for one hour and renews it by itself. The token works only for the MCP address and only in this team. A connection that goes unused for 90 days ends.

To disconnect, click Disconnect under Settings › Agents, or sign out in the tool (claude mcp logout pumice-<team>, codex mcp logout pumice-<team>). The next call is refused, and the tool asks you to sign in again.

What the agent may do

It may read and write everywhere in the vault you picked. It never manages or approves, and never has more rights than you: if you lose a right, the agent loses it too, and if you leave the team, the agent can do nothing until someone else connects it.

Other vaults stay closed to it until an admin shares them. Owners and admins of the team change the agent’s rights later under Settings › Agents, in every vault where they are admin: Read or Read and write, Remove, and Share another vault for one more vault with its rights. The change counts from the agent’s next call, without a new sign-in. Connecting always picks exactly one vault.

Everything it does over MCP carries its name: in the history, on comments and as a ring in the file tree. It never merges silently: if someone changed a file after the agent read it, its write is refused and it gets the current version. No tool deletes or moves files.

If you sync a vault to a folder with the desktop client, the agent asks pumice_devices which of your computers holds which vault in which folder. If it runs on that computer, it reads and writes right there in the folder, and your client uploads the changes under your name and with your rights. Otherwise it uses pumice_read and pumice_write. It sees only folders it has rights in, and never the devices of other members.

Agents count towards your plan. The Free plan has 3 agents per team.

Tools

If it does not work

The name is already taken

Claude Code reports that pumice-<team> already exists: the entry is there already. Sign in with claude mcp login pumice-<team>, or remove it with claude mcp remove pumice-<team> -s user and add it again. An old entry named pumice from an earlier guide goes the same way: claude mcp remove pumice -s user.

The sign-in page says “Another agent in the team already has this name”: choose a different name there.

The agent is in the wrong team

A sign-in belongs to the team you picked. Sign out in the tool and sign in again with the right team: claude mcp logout pumice-<team>, then claude mcp login pumice-<team> (Codex: codex mcp logout pumice-<team>, then codex mcp login pumice-<team>). In Claude or ChatGPT, remove the connector and add it again. Then disconnect the agent in the wrong team under Settings › Agents.

For two teams, add two entries, one per team.

The sign-in stops

“… an owner or admin connects agents”: ask one of the people the page names.

“The team already has 3 of 3 agents”: remove an agent under Settings › Agents.

“This agent is not (or no longer) registered with Pumice” or “redirect address is not allowed”: start the connection in the tool again. In Claude, choose Register automatically as OAuth client.