Skip to main content

Add External MCP Servers

Connecting SixDegree to Claude exposes your graph to an AI client. This is the other direction: registering an external MCP server with a SixDegree environment so its tools join the toolset your agents (and any connected Claude client) can call.

Once registered, an endpoint's tools are surfaced alongside SixDegree's own graph tools, so a single connection to your environment reaches both.

Add an endpoint

Use the degree CLI:

degree mcp create "Database Tools" "https://mcp-db.example.com" "PostgreSQL query tools" \
--header "Authorization:Bearer YOUR_TOKEN"

Arguments are the name, the URL, and an optional description. Headers are key:value pairs and may be repeated with --header (or -H).

Transports

The transport is inferred from the endpoint, and may be one of:

  • streamable-http: remote HTTP servers (the common case for hosted MCP servers).
  • sse: remote servers using Server-Sent Events.
  • stdio: a local process.
  • unix: a Unix domain socket.

Authentication

Choose whichever the target server expects:

  • Custom headers: pass credentials directly, for example --header "Authorization:Bearer YOUR_TOKEN".
  • SixDegree auth: --sixdegree-auth injects SixDegree's own credentials, for servers that trust SixDegree.
  • OAuth service: --oauth-service-id <id> links a configured OAuth service so tokens are obtained and refreshed for you.

Limit which tools are exposed

A server may offer more tools than you want available. Restrict them with allow and deny lists in the API (allowed_tools, denied_tools). A denied tool is never disclosed to the agent; if an allow list is set, only those tools are exposed.

Renderers

If the server returns rich HTML resources you want rendered in SixDegree, enable them with --allow-renderers.

Manage endpoints

degree mcp list # list configured endpoints
degree mcp get <id> # inspect one endpoint
degree mcp update <id> --url … # change configuration
degree mcp delete <id> # remove an endpoint

Inspect available tools

After adding an endpoint, list the tools it advertises:

GET /api/v1/mcp/endpoints/{endpoint-id}/tools

Endpoints are created with POST /api/v1/mcp/endpoints and managed under /api/v1/mcp/endpoints/{id}. The environment is derived from your API token.

Next steps