MCP connection
Already have a Model Context Protocol server? Connect it and the agent gets all of its tools.
Requirements
- MCP streamable HTTP transport (a single POST endpoint, JSON or SSE replies).
- Public https URL. Private and local hosts are blocked.
- Optional single auth header, e.g.
Authorization: Bearer ….
Connect
POST /api/connectors/
{
"kind": "mcp",
"name": "CRM",
"url": "https://mcp.example.com/mcp",
"auth_header": "Authorization",
"auth_secret": "Bearer sk_live_…"
}
Then press Test (POST /api/connectors/{id}/test/). Oydin runs initialize and tools/list, stores the tool list and reports the result. Run Test again whenever your server's tools change.
How tools reach the agent
- Each server tool becomes
c<connector id>_<tool name>with your description andinputSchema. - When the agent calls one, Oydin opens a session, sends
tools/calland returns the text content. - Tool results are truncated to 20,000 characters; the timeout is 15 seconds per request.
- Disable a connector with
{"enabled": false}to hide its tools without deleting it.
Write good tool descriptions: the agent decides when to call a tool only from the name and description.
Secrets are encrypted at rest and never returned; responses only show
has_secret: true. Only the owner can manage connectors.