English Français العربية

Gdc

السجل الرسمي أخرى

NCI Genomic Data Commons (GDC) MCP.

الشيفرة المصدرية الموقع التوثيق

التثبيت

أضف هذا إلى إعدادات MCP في عميلك (Claude Desktop: claude_desktop_config.json، وCursor: ‏.cursor/mcp.json، ويستخدم VS Code وغيره الصيغة نفسها «mcpServers»).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http gdc 'https://gateway.pipeworx.io/gdc/mcp'
إعداد JSON (Claude Desktop وCursor وVS Code) 
{
    "mcpServers": {
        "gdc": {
            "type": "http",
            "url": "https://gateway.pipeworx.io/gdc/mcp"
        }
    }
}
NPM package @pipeworx/mcp-gdc
Claude Code 
claude mcp add gdc -e 'PIPEWORX_API_KEY=<your pipeworx_api_key>' -- npx -y @pipeworx/mcp-gdc@0.2.1
إعداد JSON (Claude Desktop وCursor وVS Code) 
{
    "mcpServers": {
        "gdc": {
            "command": "npx",
            "args": [
                "-y",
                "@pipeworx/mcp-gdc@0.2.1"
            ],
            "env": {
                "PIPEWORX_API_KEY": "<your pipeworx_api_key>"
            }
        }
    }
}

متغيرات البيئة

  • PIPEWORX_API_KEY سري Optional Pipeworx API key. Without it calls are anonymous and capped daily; a free key raises the cap.

التوثيق

مأخوذ من ملف README للمشروع على GitHub ويُحدَّث أسبوعيًا. تفتح الروابط على GitHub.

المحتويات
  1. mcp-gdc
  2. Tools
  3. Quick Start
  4. No MCP client? Call it over HTTP
  5. Standalone (no gateway account)
  6. Using with ask_pipeworx
  7. More
  8. License

mcp-gdc

NCI Genomic Data Commons (GDC) MCP.

Part of Pipeworx — an MCP gateway connecting AI agents to 1879+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.

Tools

ToolDescription
list_projectsList NCI Genomic Data Commons cancer-genomics projects (TCGA, TARGET, CPTAC, etc.), ranked by case count. Returns project_id, name, program, primary site(s) and disease type(s). Keyless, open-access metadata.
get_projectLook up a single NCI GDC project by project_id (e.g. "TCGA-BRCA") and get its details plus summary counts (case_count, file_count). Keyless, open-access metadata.
search_casesSearch NCI GDC cancer cases (patients/samples) by primary site and/or project. Returns case_id, submitter_id, primary site, disease type and project_id. Keyless, open-access metadata.
search_filesSearch NCI GDC genomic data files by project and/or data category (e.g. "Transcriptome Profiling", "Simple Nucleotide Variation", "DNA Methylation"). Returns file_id, file_name, data category/type/format, access level and file size. Keyless, open-access metadata.

Quick Start

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

{
  "mcpServers": {
    "gdc": {
      "url": "https://gateway.pipeworx.io/gdc/mcp"
    }
  }
}
What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/gdc/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — ask_pipeworx, discover_tools, 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:

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

Both URLs reach the same gateway and the same 1879+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.

No MCP client? Call it over HTTP

curl -X POST https://gateway.pipeworx.io/v1/tools/gdc_list_projects \
  -H 'Content-Type: application/json' \
  -d '{"size":20}'

No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/gdc_list_projects. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.

Standalone (no gateway account)

This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:

{
  "mcpServers": {
    "gdc": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-gdc"]
    }
  }
}

Or run it directly to confirm it starts:

npx -y @pipeworx/mcp-gdc

It speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call for only this pack's tools — none of the shared meta-tools the gateway connection above adds. Same source, same tools, no ask_pipeworx routing.

Using with ask_pipeworx

Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:

ask_pipeworx({ question: "your question about Gdc data" })

The gateway picks the right tool and fills the arguments automatically.

More

License

MIT

الأسئلة الشائعة

ما هو Gdc؟

NCI Genomic Data Commons (GDC) MCP.

كيف أثبّت Gdc؟

يعمل كخادم بعيد. في Claude Code: claude mcp add --transport http gdc 'https://gateway.pipeworx.io/gdc/mcp'. وفي العملاء الآخرين، الصق إعداد JSON من هذه الصفحة في إعدادات MCP الخاصة بهم.

هل يحتاج Gdc إلى مفتاح API؟

نعم. يتطلب PIPEWORX_API_KEY، وتضبطها في إعداداته.

هل Gdc مفتوح المصدر؟

نعم. شيفرته متاحة على GitHub بترخيص MIT.

من يصون Gdc؟

ينشره pipeworx-io. يدرجه AI.tn لكنه لا يصونه ولا يوصي به.

من سجل MCP الرسمي. الإدراج ليس توصية: راجع شيفرة الخادم وصلاحياته قبل منحه الوصول إلى بياناتك.