Connect your agents to Podclave

Use ChatGPT, Claude, Grok, or another agent that supports the Model Context Protocol (MCP) to manage your Podclave Sessions.

An outside agent connects to one address:

https://podclave.com/mcp

When the agent connects for the first time, it opens Podclave in your browser. You sign in, choose who the agent acts as and which Worlds it can use, and approve. The agent then can:

• list your Sessions in the approved Worlds and read what they say;
• start a Session with a first instruction;
• send a message, answer a question or an approval request, and stop a turn;
• rename, park, and remove your Sessions;
• turn Keep active on or off for a Session, so that it does not park when idle (compute stays billable while it runs);
• read, download, create, and replace Shared files and your own My files in the approved Worlds (never another person’s My files).

It cannot change World settings, members, or repositories, and it cannot see other members’ private Sessions.

What you choose when you connect

Who the agent acts as. You choose one of:

• You. You tick the Worlds the agent can use. You can choose any World where you are a member.
• A service account. Only a World’s admins see this choice. A service account works in its own World only. Its Sessions are visible to that World’s admins, and Podclave records its actions as the service account, approved by you. See Service accounts.

A connection never mixes the two. To use both, connect twice.

Check the name and the return address. The consent page shows the name that the agent gives for itself and the address that Podclave returns you to. Podclave cannot confirm the name. Approve only when the return address belongs to the agent you are connecting.

Manage your connections

Connections that act as you. Open Account → Agent connections in Podclave. For each connection you can:

• Add Worlds. Podclave shows the exact change and asks you to confirm it. Every app or device that holds the connection’s sign-in gets the new Worlds at once.
• Remove a World. The removal takes effect at once.
• Revoke the connection. Its sign-in stops at once. Sessions, Workspaces, and files stay.

A World’s Agent access page lists your connections that include that World. You can remove that World from a connection there.

If you lose access to a World, the connection stops working there at once, and the World shows as no longer usable. If you join the World again later, it does not come back by itself: on Account → Agent connections, first remove that World from the connection, then add it again and confirm. Connecting again from the same agent makes a new connection; revoke the old one if you do not need it.

Service account connections. These are not on your Account page. A World’s admins see and revoke them on that World’s Service accounts page. A service account connection always stays in its own World: you cannot add other Worlds to it. Disabling the service account revokes all its connections. See Service accounts.

Get told when a Session needs you

An agent can follow your Sessions without asking again and again. Podclave then tells the agent when a Session ends a turn, waits for an answer, or loses its agent. An agent can also follow all the activity of a Session: Podclave then sends a short summary of the work at most every 30 seconds, and sends at once when the Session ends a turn, waits for an answer, or loses its agent. The summaries contain counts and kinds of steps, not message text or step names. The agent chooses the option that its app supports:

1. MCP Events. The agent’s app subscribes to the Session and receives each event at its own address. The app keeps its signing secret, and it renews the subscription before it ends (at most one day).
2. A webhook. If the app has no MCP Events but gives the agent an address that starts its work when it is called with a key, the agent asks Podclave to call that address. The key belongs to that address, not to Podclave. The easiest way, where Podclave offers it for the agent’s app: on Account → Agent connections, select Add webhook on the agent’s connection and enter the address and its key once; your agent can send you a link to that page. The key does not go through the agent, and saving it starts nothing: the agent then chooses the Sessions to follow. An agent can also give Podclave the key through its app’s own secret feature. Never type a key into a chat. This watch stays until the agent deletes it, you remove the saved webhook, the address reports that it is gone, the Session is removed, or the connection loses access to the World (for example, you revoke it).
3. Checking. If neither works, the agent can check only the Sessions it follows, now and then, and stop when they are done. It must tell you that it checks.

Each option follows one Session. When an agent starts a new Session, it sets up the option again for that Session. A message from Podclave only tells the agent to look: the agent then reads the Session in Podclave.

An agent can test a webhook. A successful test shows only that the address accepted a message. Your agent is set up only when a real Session event wakes it.

Costs and credentials

A Session that an agent starts uses an agent credential of the identity it acts as (for example your Claude or Codex sign-in), or the World’s Lab funding when the World offers it. Podclave never switches a request from one to the other. If the World does not offer Lab funding, add your own agent credential in Podclave before you connect.

ChatGPT

ChatGPT connects to Podclave as an app in developer mode. OpenAI offers developer mode on the web for Pro, Plus, Business, Enterprise, and Education accounts; in workspaces, an admin can control it.

1. In ChatGPT, open Settings → Security and login and turn on Developer mode.
2. Open Plugins, select the plus button, and create an app with the URL https://podclave.com/mcp and OAuth sign-in.
3. Sign in to Podclave, make your choices, and approve.
4. In a chat, choose Developer mode in the plus menu and select the Podclave app.

See OpenAI’s guide: ChatGPT developer mode.

Codex in the ChatGPT desktop app

Codex can use the same address as an MCP server: open Settings → MCP servers, add a server of type Streamable HTTP with the URL https://podclave.com/mcp, restart, and select Authenticate. See OpenAI’s guide: Model Context Protocol.

Claude

Claude connects to Podclave as a custom connector.

• Free, Pro, and Max plans: open Customize → Connectors, select Add custom connector, and enter https://podclave.com/mcp.
• Team and Enterprise plans: an Owner adds the connector in Organization settings → Connectors. Members then connect in Customize → Connectors.

If the dialog asks for an OAuth client, choose Register automatically. Then sign in to Podclave, make your choices, and approve.

See Anthropic’s guide: Add a connector that isn’t in the directory.

Grok

Grok connects to Podclave as a custom MCP connector.

1. Open grok.com/connectors, select New Connector, then Custom.
2. Enter https://podclave.com/mcp and complete the sign-in.

On Grok Business and Enterprise plans, a team admin first adds the connector in the xAI console (Grok Business → Connectors, Add Connector, Other). See xAI’s guide: Connectors.

Grok bots: These steps are for the Grok app. If you connect a Grok bot, check the name and the return address on the consent page before you approve. To be told about Sessions, a bot uses an option from Get told when a Session needs you above that its current features support.

Other agents

An agent that supports remote MCP servers with OAuth sign-in can connect to https://podclave.com/mcp. Give it the address, and approve the connection on Podclave’s consent page.

Get help

Write to hello@podclave.com.