Model Context Protocol

Bring MCP tools into customer conversations.

Ayooda discovers tools from remote MCP servers, converts their input schemas for the agent runtime, and makes each connection available only to the agent you choose.

Transports

Streamable HTTP and SSE endpoints are supported over public HTTPS.

Authentication

Connect without auth, with a bearer token, or with a custom secret header.

Safety

Private and unsafe network targets are blocked, redirects are rejected, and calls use hard timeouts.

Isolation

A failing MCP server is skipped for that turn without taking down the rest of the agent.

Connect an MCP server

  1. Open the agent’s MCP tabFrom the dashboard, choose an agent and open MCP in its navigation.
  2. Add the server URLEnter a public HTTPS Streamable HTTP or SSE endpoint and choose its authentication method.
  3. Test tool discoveryAyooda connects live and lists the tools the server exposes before you enable it.
  4. Save and test the agentUse the Test tab to confirm when the agent selects the tools and how their results affect its reply.

What the agent receives

Tool names are namespaced by server to prevent collisions. JSON Schema inputs are translated into validated runtime parameters, and tool results are returned to the model as conversation context. Customer tools keep precedence if two integrations expose the same runtime name.

Try MCP with an Ayooda agent

Start with a free workspace, add your server, verify its tools, and exercise them in the isolated sandbox.

Start free