Skip to main content

MCP

The MCP connection lets you connect any Model Context Protocol (MCP) server to Siesta AI. An MCP server exposes a set of tools (functions) over a standard protocol, and Siesta AI can call those tools from agents and workflows without a dedicated native connection.

Use MCP when a system already ships an MCP server, or when you want to expose your own tools to agents through a single standard interface. For plain HTTP endpoints without MCP, use the Rest API connection instead.

Overview​

Through an MCP connection, Siesta AI:

  • discovers the tools published by the MCP server,
  • calls those tools with arguments provided by the agent,
  • returns the results into the conversation or workflow.

Requirements​

  • A reachable MCP server endpoint (URL).
  • Any authentication the server requires (for example an API key or bearer token).
  • Knowledge of which tools the server exposes and their write behavior.

1. Add the Connection in Siesta AI​

  1. Open the Connections section.
  2. Click Add Connection.
  3. Search for and select MCP.
  4. Fill in:
    • Name: a recognizable label for the server.
    • Server URL: the endpoint of the MCP server.
    • Authentication: the credential the server requires, if any.
    • Access: Private (visible only to you) or Shared (usable across the organization).
  5. Save. Siesta AI connects to the server and loads the available tools.

2. Review and Govern Tools​

After connecting, review the tools the server exposes:

  • Confirm what each tool does and whether it reads or writes.
  • Put write-capable tools into confirmation mode where supported.
  • Assign the connection only to agents and workflows that need it.

3. Use MCP Tools​

  1. Open an Agent or Workflow.
  2. Attach the MCP connection.
  3. The agent can now call the server's tools during interactions or automatically in the background.

Security & Governance​

  • Treat MCP tool schemas, headers, and write behavior as production contracts.
  • Prefer Private access for servers with sensitive scope, and review shared access.
  • Function governance uses the strictest effective setting: enabled, enabled with confirmation, or disabled.
  • Tool executions record function status and approval state for audit.

Technical Notes​

  • Implementation: MCP tools are defined by the connected server rather than a fixed connection module.
  • Authentication/scopes: depends on the MCP server (API key, bearer token, or other headers). Limit credentials to what the tools actually need.
  • Functions: each tool published by the server maps to a callable function with its own parameters and write behavior.
  • Write behavior: tools that change external systems should require confirmation and narrow allowlists for production agents.

Summary​

The MCP connection brings any Model Context Protocol server into Siesta AI as a set of callable tools for agents and workflows. It is the standard way to expose custom or third-party tools through one interface, with the same access, confirmation, and audit controls as other connections.

Last updated on