# Adding an MCP server

Going the other direction: add an external MCP server so its tools flow into your Foxora agents. Foxora's entire connector catalog is built on MCP — and meta-connectors let you bring any MCP endpoint you have.

## Catalog connectors are MCP servers

Every entry in the connector catalog is an MCP server. Foxora curates the launch command — you supply only the credentials — and on session start it runs the server over stdio and merges its tools into the agent. So “connecting GitHub” is, under the hood, “adding the GitHub MCP server.”

## Bring your own MCP server

For servers outside the curated catalog, reach them through a meta-connector. Both accept an MCP server URL you paste:

- Composio — create an MCP server in Composio and paste its URL (https://mcp.composio.dev/…). One connection fronts 250+ managed app integrations with OAuth handled for you.
- Zapier — generate your Zapier MCP endpoint (https://mcp.zapier.com/api/mcp/…) and paste it. One connection fronts 30,000+ app actions.

These bridge a remote MCP server to your agents and run any OAuth flow in the browser on first use — you authorize once.

## Where the tools appear

Once connected, an MCP server’s tools behave like any other connection: merged into the agent toolbelt at session start, namespaced under the connection’s name, and toggleable per agent from the agent editor’s Connections tab. See Using connected tools.

> Two ways to extendTo give Foxora more tools, add an MCP server here. To give other apps Foxora’s tools, use Foxora as an MCP server. Same protocol, opposite roles.