Wire up MCP in your editor

Goal: connect the Chiron MCP server to your editor so an agent can call Chiron's tools directly.

You need the server's URL (HTTP transport) or command (stdio), and a way to authenticate — either a pre-issued token or the interactive authenticate tool.

Option A — HTTP transport

Point your client at the running server. In a .mcp.json (Claude Code, and other clients that read it):

{
  "mcpServers": {
    "chiron": { "type": "http", "url": "http://localhost:3001" }
  }
}

Or via the Claude Code CLI:

claude mcp add --transport http chiron http://localhost:3001

On first use, call the authenticate tool; it returns a sign-in URL. Open it, sign in, and the session stores your token. After that every tool works with your account's data.

Option B — stdio transport

Launch the server as a subprocess and pass a pre-issued token:

MCP_AUTH_TOKEN=<your-jwt> node dist/mcp.js

With MCP_AUTH_TOKEN set, you skip the authenticate step entirely.

Verify

Ask the agent to list your projects, then run an ontology search:

list_projects()
ontology_search(project_id="acme-platform", query="where is auth handled?")

If ontology_search returns Not authenticated, your session has no token — run authenticate (HTTP) or set MCP_AUTH_TOKEN (stdio). If it returns a service-credential error, the server's INTERNAL_SERVICE_KEY does not match the Ontology Layer's. See Errors & limits.

Next: Connect a database.