Civic MCP server

@pipeworx/civic

Expert-curated clinical interpretation of cancer variants from CIViC — which somatic alterations are clinically actionable, in which disease, with which therapy, and the graded published evidence behind each claim.

Part of Pipeworx — an MCP gateway connecting AI agents to 1679+ live data sources.

Tools

variant / evidence / assertion counts and the CIViC feature id.

• civicsearchgenes(query, limit?) — cancer genes and fusions by name, with

gene, with associated diseases and therapies.

• civicgenevariants(gene, variant_name?, limit?) — the curated variants of a

— individual evidence items with type, level A-E, direction, significance, 1-5 star rating and the PubMed/ASCO source.

• civicvariantevidence(molecularprofile | variantid, evidence_type?, disease?, therapy?, limit?)

AMP/ASCO/CAP-tiered rollups, with FDA companion-test and regulatory-approval flags, ACMG codes and NCCN guideline.

• civicassertions(molecularprofile? | disease? | therapy?, limit?) — the

Auth

Keyless. Public GraphQL endpoint; CIViC's content is CC0.

Data sources

• — POST, {query, variables}.

Things that will otherwise cost you an afternoon:

returns HTTP 200. Measured 2026-09-17: evidenceItems(molecularProfileName: "BRAF V600E") reports 249 matches; adding variantId: null reports 0**, diseaseName: null reports 245, therapyName: null reports 313. Unset filters must be omitted from the variables map entirely. omitNulls() in src/index.ts exists for exactly this and removing it produces a silent zero.

• **An explicitly null variable is a FILTER, not an absent filter — and it

filter arguments.** browseVariants(featureName: "BRAF") and an unfiltered browseVariants both report 5029, the whole catalogue. evidenceItems and assertions DO filter their totalCount. This pack only reports the count for the two that mean it.

• **browseVariants.totalCount and browseFeatures.totalCount ignore their own

the schema and it is not callable. The gene summary lives on the Gene type, which is why civicsearchgenes makes a second call.

• description on the BrowseFeature type 500s the entire query. It is in

search is browseFeatures(featureName:) (substring, unranked — this pack re-ranks exact matches first) or featureTypeahead(queryTerm:).

• genes takes entrezSymbols/entrezIds, not name. Free-text gene

a submitted item has not been through CIViC review yet.

• Evidence and assertion status can be SUBMITTED as well as ACCEPTED;

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "civic": {
      "url": "https://gateway.pipeworx.io/civic/mcp"
    }
  }
}

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/civic/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — askpipeworx, discovertools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via ask_pipeworx, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.

Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:

Shortened. The full README is on GitHub.