Docs / MCP reference

MCP server reference.

Use the Coherence MCP server to give agents read access to ranked Workstreams, handoff packages, source evidence, and revenue context.

Set up a client Back to docs

Call a tool

Tools are invoked through standard MCP JSON-RPC. This example asks for the top five ranked Workstreams.

POST https://mcp.getcoherence.ai/api/mcp
Authorization: Bearer coh_live_...
Content-Type: application/json

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "list_workstreams",
    "arguments": { "limit": 5 }
  }
}

Recommended flow

Find work

Call list_workstreams or search_workstream_model.

Load context

Call get_handoff_package for implementation details.

Check receipts

Call get_spec_evidence and get_revenue_context.

Implement

Use the handoff package and citations inside your coding agent.

Tool catalog

Eleven read-only tools.

Write tools are intentionally not exposed in this public MCP surface. Agents can read product context, handoff packages, and evidence, then implement in the connected coding environment. Legacy theme/spec tools remain available while clients migrate.

list_workstreams

Return ranked Workstreams by opportunity score.

Inputs

limit?: 1-100

Returns

workstreams[], total

Find the highest-impact product problems before loading handoff context.

list_handoff_packages

Return handoff packages in the workspace, newest first.

Inputs

status?: draft | review | approved | pushed | shipped, limit?: 1-100

Returns

handoff_packages[], total

Find agent-ready packages tied to validated Workstreams.

get_handoff_package

Fetch one full agent-native handoff package.

Inputs

handoff_package_id: uuid, spec_id?: uuid

Returns

metadata, content, evidence_links, revenue_context, markdown

Load implementation context before a coding agent writes code.

search_workstream_model

Search Workstreams, evidence, handoffs, and accounts.

Inputs

query: string

Returns

workstreams, evidence, handoffPackages, accounts

Find product context across Workstreams, evidence, and handoffs.

get_spec_evidence

Fetch only the evidence excerpts behind a handoff package.

Inputs

spec_id: uuid

Returns

evidence[], total

Review receipts without pulling the full package body.

get_revenue_context

Fetch the business context attached to a handoff package.

Inputs

spec_id: uuid

Returns

arr_at_risk, customers, segments, accounts

Understand why the work matters commercially.

get_related_specs

Find sibling legacy specs targeting the same Workstream/theme.

Inputs

spec_id: uuid, limit?: 1-50

Returns

related[], total

Avoid duplicating work in the same problem area.

search

Legacy search across themes, signals, specs, and customers.

Inputs

query: string

Returns

themes, signals, specs, customers

Support older clients while migrating to search_workstream_model.

list_themes

Legacy alias for ranked Workstreams.

Inputs

limit?: 1-100

Returns

themes[], total

Support existing clients during the Workstream transition.

list_specs

Legacy alias for handoff packages.

Inputs

status?: draft | review | approved | pushed | shipped, limit?: 1-100

Returns

specs[], total

Support existing clients during the handoff package transition.

get_spec

Legacy alias for fetching a handoff package.

Inputs

spec_id: uuid

Returns

metadata, content, evidence_links, revenue_context, markdown

Support existing clients during the handoff package transition.

Troubleshooting

401 means the token is missing, malformed, or revoked. Empty results usually mean the workspace has no evidence yet. Tool names are underscored, not camelCase.

Client setup