Skip to main content

MCP

The MCP integration lets you register any external server that speaks the MCP (Model Context Protocol) so the tools it exposes appear inside SimplAI just like native capabilities. Once a server is connected, its tools can be dropped into a Tool or AI Chain as a step and attached to an Agent. SimplAI supports MCP as both a client (connecting to external servers, described here) and a server (hosting your own tools for external MCP clients — see SimplAI as an MCP server).

Where it lives​

  • Open Connections.
  • Go to the MCP tab. (This sits alongside the A2A Agents tab and follows the same connection pattern.)
  • Click Add Connection to open the connection drawer.

Connect an MCP server​

The connection drawer asks for:

  • Connection name — a label for the connection.
  • Description — what the server provides, to help others pick its tools later.
  • Server type — the transport the server uses (for example, SSE or WebSocket, as supported).
  • Server URL — the MCP endpoint you were given.
  • Headers — credentials passed on each call, for example Authorization: Bearer <token>. Stored securely.

Click Connect to validate the credentials. On success, SimplAI discovers the tools the server exposes and makes them available within the current project.

Project scoping​

MCP connections are project-scoped — a connection you create is usable only inside the project where it was added, along with that project's users, limits, and audit trail. To use the same server in another project, connect it again there. This mirrors how A2A connections behave.

Add from where you need it​

Besides the Connections screen, you can add a new MCP connection inline from:

  • Agents screen → Add tools drawer — the MCP tab, "Add new".
  • Tools / AI Chains screen → node picker — "Add new".

Use MCP tools​

Once a server is connected, the tools it exposes can be used in two places.

As a node in Tools / AI Chains​

In the node picker, MCP tools are selectable as an MCP Server step, alongside Pre-built Steps, Tools, and Agents. An MCP node runs like any other step, with the same inputs/outputs, error handling, and logs. See Tool steps basics.

On an agent​

  • Open your agent in Studio.
  • In the Tools card, click Add.
  • In the Add tools drawer, switch to the MCP tab — it lists the tools exposed by connected MCP servers.
  • Click the + icon to attach a tool.

An attached MCP tool behaves the same as any native tool: the agent's planner can call it, pass it inputs, and interpret its result. For attaching and tuning tools on an agent, see Add Tools.

SimplAI as an MCP server​

SimplAI can also expose its own tools to external MCP-compatible clients (for example, Cursor, Claude Desktop, or a custom SSE client). From the Integrations / Deployment area of a Tool, generate the MCP server configuration and supply the hosted URL — which includes an embedded auth token — to your MCP client. For the AI Chain hosting flow, see Legacy AI Chain Deployment → MCP Configuration.

  • A resource must be Published to be callable through the MCP server.
  • Treat the configuration URL as a secret; rotate it by regenerating the server or your API key.
  • Limit each server to only the resources you intend to host.

Governance​

  • Keep MCP tokens in project env. variables (Secret) and reference them in the connection Headers where supported, rather than hard-coding them.
  • Rotate credentials on a schedule and disable or delete unused connections.

Troubleshooting​

  • MCP tools not listed? Ensure the MCP server is reachable from your network and that the Server URL includes any required token; re-check the Headers.
  • Can't see the connection in a node? Confirm the connection is in the same project and your role has access.
  • Tool not callable from an agent? Improve the tool description and confirm limits aren't blocking calls.
  • Resource not visible in external MCP clients? Ensure it is Published and included in the selected MCP server; re-copy the configuration URL with token.

Notes​

  • The A2A connection UX intentionally mirrors this MCP connection flow for familiarity.
  • Connections are usable only in the project where they were created.
  • Every connection action — create, edit, delete, enable, disable — is captured in the Audit log under the MCP resource type.