MCP Servers
Copy page
Learn how to add and configure MCP servers for your agents
MCP tools connect to external servers that implement the MCP standard. This allows you to integrate with a wide ecosystem of existing tools and services.
Basic MCP Server
Authentication
MCP servers support various authentication methods (via credentials):
- No Authentication - For public APIs or internal services
- API Key - For services requiring API keys
- Bearer Token - For JWT or similar token-based authentication
- Token Authentication - For custom token schemes
- OAuth Flows - For standard OAuth 2.0 authentication
- OAuth 2.1 Flows - For modern OAuth 2.1 authentication
For OAuth flows and OAuth 2.1 flows, it's recommended to use the Visual Builder for easier configuration.
See Credentials for detailed examples and implementation guidance for each authentication type.
Example with Authentication
Custom Headers
You can configure custom headers for your MCP server requests. Use credentials for sensitive information (API keys, tokens) and headers for non-sensitive metadata (user agent, version info, etc.).
Selective Tools
Selective Tool Activation
Enable only specific tools from a server using MCP Server tool names in the activeTools
field.
Best Practices
To ensure agents properly utilize their tools, follow these best practices:
- Give tools clear, descriptive names and descriptions - Explain what the tool does and when it should be used
- Reference the tool in the agent's prompt - Explicitly mention that the agent has access to specific tools and describe scenarios where they should be used
- Secure your credentials - Store sensitive information using the credential system
- Limit tool scope - Use
activeTools
to expose only necessary functionality
Example with best practices applied: