Skip to main content

Manage MCP servers

Learn how to connect personal or org-wide MCP servers in Pod.

Written by Patrick Monnot
Updated today

MCP Servers lets you connect remote MCP endpoints to Pod and decide which discovered tools are available for Deal Agent runtime. Use this page when you want Pod's AI workflows to reach external tools without hard-coding those connections into each agent by hand.

How to access

  1. Open Pod.

  2. Go to Settings.

  3. Select MCP Servers.

What you'll find

The page is split into two tabs:

  • Personal for servers only you can use

  • Org-wide for shared servers available across the workspace

Each server card shows the server name, URL, health state, and the number of runtime-eligible tools Pod discovered. From the card, you can:

  • enable or disable the full server

  • connect OAuth if the provider requires it

  • refresh the server

  • edit or delete the server

  • expand the card to review discovered tools and enable tools one by one

How to add a server

  1. Choose the Personal or Org-wide tab.

  2. Click Add Personal Server or Add Org-wide Server.

  3. Choose a setup method:

    • Directory searches the official MCP registry and prefills server metadata.

    • Manual Entry lets you paste any remote MCP server URL directly.

  4. Select an authentication method: None, Bearer token, Custom header, or OAuth.

  5. Save the server.

If the server uses OAuth, Pod saves the server first and then opens the provider authorization flow so you can finish the connection.

How to control runtime tools

  1. Expand a server card.

  2. Review the Discovered tools table.

  3. Use the top-level server switch to enable or disable the whole server.

  4. Use the per-tool Enabled switches to control which tools Pod can actually use at runtime.

  5. Use Refresh server after authentication changes or when the provider's tool inventory changes.

Permissions and shared access

  • Personal servers are for your own workflows.

  • Org-wide servers are shared across the workspace.

  • Non-admin users can view org-wide servers, but only workspace admins can add, edit, validate, or toggle them.

  • Some org-wide OAuth setups can depend on an admin-owned grant. If that grant is revoked or loses access, the shared server can stop working for the workspace.

If you still need to create the saved agent that will use these tools, start with Build a new agent.


πŸ’‘ Need help? Send us a message via the in-app chat or email us at [email protected].

🀝 Want to talk to someone? Book a session with one of our specialists!

Did this answer your question?