list_themesReturn ranked themes by opportunity score.
limit?: 1-100
themes[], total
Find the highest-impact work before asking for specs.
Use the Coherence MCP server to give agents read access to ranked themes, approved specs, source evidence, and revenue context.
Tools are invoked through standard MCP JSON-RPC. This example asks for the top five ranked themes.
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_themes",
"arguments": { "limit": 5 }
}
}Find work
Call list_themes or list_specs.
Load context
Call get_spec for implementation details.
Check receipts
Call get_spec_evidence and get_revenue_context.
Implement
Use the spec and citations inside your coding agent.
Write tools are intentionally not exposed in this public MCP surface. Agents can read product context, specs, and evidence, then implement in the connected coding environment.
list_themesReturn ranked themes by opportunity score.
limit?: 1-100
themes[], total
Find the highest-impact work before asking for specs.
list_specsReturn specs in the workspace, newest first.
status?: draft | review | approved | pushed | shipped, limit?: 1-100
specs[], total
Find approved work that is ready for implementation.
get_specFetch one full agent-native spec.
spec_id: uuid
metadata, content, evidence_links, revenue_context, markdown
Load the implementation context before writing code.
get_spec_evidenceFetch only the evidence excerpts behind a spec.
spec_id: uuid
evidence[], total
Review receipts without pulling the full spec body.
get_revenue_contextFetch the business context attached to a spec.
spec_id: uuid
arr_at_risk, customers, segments, accounts
Understand why the work matters commercially.
get_related_specsFind sibling specs targeting the same theme.
spec_id: uuid, limit?: 1-50
related[], total
Avoid duplicating work in the same problem area.
searchSearch themes, signals, specs, and customers.
query: string
themes, signals, specs, customers
Answer a targeted product-context question.
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.