Consuming Third-Party MCP Servers

Senda can also act as an MCP Client — consuming tools from external MCP servers (GitHub, Slack, Notion, etc.) as actions in the action catalog.

How It Works

1. In the Senda admin panel, create a new action with action_type = "mcp"
2. Set mcp_server_url to the external MCP server URL
3. Set mcp_tool_name to the tool you want to call
4. When the agent triggers this action, Senda connects to the external MCP server and calls the tool

Configuration Example

Field	Value
Action Type	mcp
MCP Server URL	https://mcp.github.com/v1
MCP Tool Name	create_issue
Parameters	repo, title, body

Flow

User → "Create a GitHub issue for this bug"
  → Senda Router → Agent with MCP action
    → Action Engine → MCP Client Proxy
      → External GitHub MCP Server
        → tools/call("create_issue", { repo, title, body })
      ← JSON-RPC result
    ← "Issue #142 created ✅"
  ← User sees confirmation

Authentication

The MCP Client uses the action's headers_json field for authentication. You can use Vault interpolation for OAuth tokens:

{
  "Authorization": "Bearer {{USER_CREDS.github}}"
}