MCP Providers
MCP providers are external services that host and serve tools via the Model Context Protocol (MCP). Data Designer uses provider configurations to establish connections to these services.
Overview
An MCP provider defines how Data Designer connects to a tool server. Data Designer supports two provider types:
When you create a ToolConfig, you reference providers by name, and Data Designer uses those provider settings to communicate with the appropriate MCP servers.
MCPProvider (Remote)
Use MCPProvider to connect to a pre-existing MCP server. Both SSE (Server-Sent Events) and Streamable HTTP transports are supported:
MCPProvider Fields
LocalStdioMCPProvider (Subprocess)
Use LocalStdioMCPProvider to launch an MCP server as a subprocess:
LocalStdioMCPProvider Fields
API Key Configuration
The api_key field can be specified in two ways:
-
Environment variable name (recommended): Set
api_keyto the name of an environment variable (e.g.,"MCP_API_KEY"). Data Designer will resolve it at runtime. -
Plain-text value: Set
api_keyto the actual API key string. This is less secure and not recommended for production.
YAML Configuration
Both provider types use a provider_type discriminator field in YAML configurations. When writing YAML configs manually (e.g., in ~/.data-designer/mcp_providers.yaml), include the discriminator:
Using Multiple Providers
You can configure multiple MCP providers and use them together in a single ToolConfig:
See Also
- Tool Configurations: Configure tool access with ToolConfig
- Configure MCP with the CLI: Use the CLI to manage MCP providers
- Enabling Tools on Columns: Use tools in LLM columns