MCP Servers
MCP Servers connect an agent to external systems through the Model Context Protocol.
MCP Servers
MCP Servers connect an agent to external systems through the Model Context Protocol.
In plain language: MCP gives the agent a structured way to use external tools from systems that already expose an MCP server.
What MCP Servers Are For
Use MCP when you want the agent to work with external tools or services such as:
- GitHub
- Slack
- Notion
- keyless web search through SearXNG or DuckDuckGo
- databases
- custom services
What The MCP Page Supports
The page lets you:
- view configured servers
- browse a catalog of available integrations
- create a custom server
- connect supported services through OAuth
- enable or disable servers
- control which tools are enabled per server
Catalog vs Custom Server
| Option | Use it when |
|---|---|
| Catalog | The integration already exists and you want the fastest supported setup |
| Custom Server | You need a private or unsupported MCP endpoint |
Catalog vs Custom vs Tools
Use the catalog when the integration already exists and you want the fastest supported setup.
SearXNG Search and DuckDuckGo Search do not require users to enter an API key. SearXNG uses the platform-operated search service and is the preferred option. DuckDuckGo is a best-effort fallback that may be rate-limited by its upstream service.
Use a custom MCP server when your team already has a private MCP endpoint or needs a broader custom integration.
Use Tools instead when one direct HTTP action is enough and you do not need a larger MCP tool surface.
Good Setup Flow
- browse the catalog first
- connect with OAuth when supported
- enable only the tools the agent truly needs
- test behavior in a safe environment
- review conversation transcripts to confirm the agent uses the integration well
Best Practices
- avoid exposing too many tools to one agent at once
- give each agent only the integrations that match its job
- validate permissions and expected outputs before launch
- compare MCP-based workflows with custom Tools if you are unsure which abstraction fits best
Setup Checklist
- decide whether catalog, custom MCP, or a normal tool is the right fit
- connect with OAuth or configure the custom endpoint
- enable only the tools the agent actually needs
- test the integration in a safe environment
- review real transcripts to confirm the agent is using the integration correctly
Related Docs
Tools
Enable built-in tools and create custom HTTP tools for your agent.
API Keys
Create and manage keys for chat, retrieve, and ingest use cases.
API Reference
Interactive endpoint docs for chat, retrieval, and source management.