Marrow
Docs Log in Sign up

MCP

Status: roadmap. Marrow does not ship an MCP server today. The hosted API is the integration surface for now. See the API Reference and Marrow CLI. This page describes the planned MCP shape so agent platforms can prepare.

A Model Context Protocol server in front of Marrow is on the roadmap. It will let MCP-compatible clients (Cursor, Claude Desktop, VS Code, OpenAI tools) read the authenticated account's professional context as a tool, with the same scoping and rate-limit semantics as the hosted API.

Planned configuration

Once shipped, the MCP server will accept the same API key as the hosted API. Expected client config sketches:

Cursor (~/.cursor/mcp.json):

{
  "mcpServers": {
    "marrow": {
      "url": "https://marrow.example.com/mcp",
      "headers": { "Authorization": "Bearer ${MARROW_API_KEY}" }
    }
  }
}

Claude Desktop (Settings → Developer → Edit Config):

{
  "mcpServers": {
    "marrow": {
      "command": "npx",
      "args": ["mcp-remote", "https://marrow.example.com/mcp", "--header", "Authorization: Bearer ${MARROW_API_KEY}"]
    }
  }
}

VS Code (.vscode/mcp.json):

{
  "servers": {
    "marrow": {
      "type": "http",
      "url": "https://marrow.example.com/mcp",
      "headers": { "Authorization": "Bearer ${MARROW_API_KEY}" }
    }
  }
}

Planned tools

The MCP surface will mirror the customer-facing hosted endpoints, one tool per logical operation:

Tool Backing endpoint Purpose
marrow_query POST /v1/query Evidence-backed query with ranked records and source-note excerpts
marrow_style_profile POST /v1/style/profile Typed style observations, preferences, vocabulary rules
marrow_source_runs GET /v1/source-runs List ingest runs
marrow_inspect_run GET /v1/source-runs/{id}/inspect Counts, predicates, facets, warnings for one run
marrow_evidence GET /v1/source-runs/{id}/evidence Cited evidence pack from a run
marrow_neighbors GET /v1/nodes/{type}/{id}/neighbors Local subgraph around a node
marrow_ingest_url POST /v1/ingest/url Plan or queue URL ingest
marrow_ingest_file POST /v1/ingest/file Plan or queue file ingest
marrow_correction POST /v1/feedback/corrections Plan or write a reviewed correction

Scoping will follow the API: an MCP key with scope query exposes marrow_query only.

Today: HTTP from any MCP-shaped agent

Until the MCP server ships, MCP-aware agents can call the hosted endpoints directly through their built-in HTTP tool. The API Reference pages cover request, response, scopes, and rate-limit headers in full.

For local development, the Marrow CLI is the fastest path. It covers every read and write the API offers, plus graph analysis the API does not yet expose.