This reference covers Eden's MCP (Model Context Protocol) endpoints. MCP servers expose tool APIs that can be used by LLM clients and automation.
Each database endpoint can expose one or more MCP servers. Clients discover the available servers, then connect using the streamable HTTP transport. Streamable HTTP uses:
Get the MCP servers available for an endpoint.
GET /api/v1/endpoints/{id}/mcp
Authorization: Bearer <token>curl http://{host}:8000/api/v1/endpoints/{id}/mcp \
-H "Authorization: Bearer $TOKEN"{
"servers": [
{
"name": "mongodb",
"description": "MongoDB MCP server"
}
]
}Use the MCP server name to connect over streamable HTTP.
/api/v1/endpoints/{id}/mcp/{mcp_server}POST requests:
Authorization: Bearer Accept: application/json, text/event-streamContent-Type: application/jsonGET requests:
Authorization: Bearer Accept: text/event-streamSession headers:
Mcp-Session-Id is returned by the server and must be sent on subsequent requestsLast-Event-Id is optional and used to resume SSE streamsMcp-Session-Id.Mcp-Session-Id.Mcp-Session-Id on subsequent POST and GET requests.Mcp-Session-Id when you are done.Base URL:
/api/v1/mcp/migrationsThis server exposes migration management tools over MCP. Use the same streamable HTTP headers and session flow described above.
Available tools:
list_migrations (optional verbose, updated_since, status, limit, cursor)get_migration (migration_id, optional verbose)define_migration (id, optional description, strategy, data, failure_handling, optional apis, optional interlays)run_migration (migration_id, mode = test|migrate, optional wait)