MCP servers let Pod connect to external tool providers and discover the runtime tools your AI workflows can use. This is the right workflow when you want to extend Deal Agent runtime with capabilities that live outside Pod.
How to access
Open Pod.
Go to Settings.
Select MCP Servers.
How to connect a server
Choose the Personal or Org-wide tab.
Click Add Personal Server or Add Org-wide Server.
Choose a setup path:
Directory searches the official MCP registry.
Manual Entry lets you paste a remote MCP server URL yourself.
Choose the right authentication mode for the provider.
Save the server and complete OAuth if the provider requires it.
How tool access works
After a server is connected, Pod discovers runtime-eligible tools from that server.
Use the server-level switch to enable or disable the full server.
Expand the server card to review Discovered tools.
Use the per-tool Enabled switches to decide which tools Pod can actually use at runtime.
Use Refresh server when auth changes or the upstream tool list changes.
Personal vs org-wide servers
Personal servers are for your own workflows.
Org-wide servers are shared across the workspace.
Only workspace admins can add or manage org-wide servers.
Some shared OAuth setups can depend on an admin-owned grant. If that provider grant is revoked, the shared server can stop working for the whole workspace.
When to use MCP servers
when you want agents to reach external systems at runtime
when you need tool access that is broader than Pod's built-in product context
when a workflow should be available only to you or shared across the workspace
If you still need the saved AI workflow itself, 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!