Docs / Strand / connectors/mcp-server

MCP Server

Direction: Read / Write | Type: mcp.server

Model Context Protocol (MCP) server connector for providing external tools to AI nodes. MCP connectors are not used as standalone nodes; they are selected within an AI node's configuration to give the model access to external tools.

Operations

Operation Direction Description
tool_call Read / Write Discover and execute tools from the MCP server

Connector Configuration

Field Required Default Description
URL Yes - MCP server endpoint (Streamable HTTP)
Auth Type No none Authentication method: none, api_key, or bearer
API Key No - API key (sent as Authorization: Bearer <api_key> header, encrypted)
Bearer Token No - Bearer token (sent as Authorization: Bearer <bearer_token> header, encrypted)
Custom Headers No - Additional HTTP headers for requests
Tool Prefix No - Prefix added to all tool names (avoids collisions)
Timeout No 30 Request timeout in seconds (5-300)

Using MCP with AI Nodes

  1. Create an MCP server connector with the server URL and authentication
  2. Add an AI connector node (OpenAI, Anthropic, or Gemini) to your workflow
  3. In the AI node configuration, select the MCP server connector(s)
  4. The AI model can then invoke tools provided by the MCP server
Tip

You can attach multiple MCP server connectors to a single AI node, giving the model access to tools from multiple servers. Use Tool Prefix to avoid name collisions (e.g., prefix mydb makes tool query available as mydb_query).

Health Monitoring

MCP server connectors include health monitoring with a circuit breaker:

Example

Connector Setup:

json

{
  "url": "https://mcp.example.com/mcp",
  "auth_type": "api_key",
  "api_key": "your-api-key",
  "tool_prefix": "myapi",
  "timeout": 60
}

AI Node Configuration: