Third-Party MCP Servers

You can integrate Agent Factory with third-party MCP servers to extend agents with tools hosted outside Agent Factory.

Before integrating a third-party MCP server, confirm the following:

• The MCP server supports an HTTP transport that Agent Factory can reach, such as an /mcp or /sse endpoint.
• The endpoint is reachable from the Agent Factory application container.
• The authentication mode is one that Agent Factory supports: direct/no auth, bearer token, OAuth authorization code, client credentials, or Auth Request.
• If OAuth is required, the provider allows you to register the exact Agent Factory callback URL.
• The server’s tool names, descriptions, and input schemas are clear enough for an LLM to choose and call the right tool.

Integration Checklist

1. Create or identify the provider-side application registration.
2. Configure scopes and permissions for only the tools the agent needs.
3. Register the Agent Factory callback URL if using OAuth.
4. Add the MCP server in Agent Factory.
5. Run Test connection and confirm tools are discovered.
6. Add the MCP Server node in Agent Builder.
7. Restrict allowed tools when the server exposes more tools than the workflow needs.
8. Run the workflow in Playground and inspect server logs if a tool call fails.

Example Public MCP Servers

The following examples are useful for evaluating connectivity and tool discovery. Public services can change without notice; verify endpoint availability and terms of use before using them.

Endpoint	Authentication	Notes
https://mcp.deepwiki.com/mcp	No auth required	Provides repository-oriented question answering for GitHub repositories indexed by DeepWiki.
https://remote.mcpservers.org/sequentialthinking/mcp	No auth required	Provides a sequential-thinking style tool for structured reasoning.
https://mcp.api.coingecko.com/sse	No auth required, limited calls	Provides cryptocurrency market data tools.

See Add MCP Server and Build Your Own MCP Server.