Typed, directed, mechanistic protein interactions, with their pathway placement and their source papers, served as JSON. The API is public, keyless, and rate limited. ATXN3 is fully mapped today.
There is no account and no key. Every endpoint is a GET request returning JSON.
The config above works in Claude Desktop or any MCP client. uvx fetches and runs the server, so there is nothing to install first.
Every interaction in the graph is returned with five properties. All of them are filterable.
What one protein does to the other, from a controlled vocabulary.
Direct or indirect, and upstream, downstream, or bidirectional.
How the interaction happens in molecular terms, with kinetics where the literature reports them.
The papers behind each claim, as PubMed identifiers, with the assay and system that produced the result.
The biological processes the interaction belongs to, at every level of the ontology.
Call /api/interaction-types for the live vocabulary with meanings and counts.
Base URL https://www.propaths.net
| Endpoint | Returns |
|---|---|
| /api/search?q= | A protein by symbol, alias, or name. q=SCA3 resolves to ATXN3. |
| /api/protein/{symbol} | The full protein record: metadata, interactions, and pathways. |
| /api/interaction/{id} | One interaction with its full mechanism and evidence. |
| /api/edge/{a}/{b} | The interaction or interactions between two proteins. |
| /api/protein/{symbol}/interactions | Filtered and sorted rows. Takes kind, type, pathway, min_evidence, sort, and limit. |
| /api/interaction-types | The controlled vocabulary with counts. |
| /api/pathway/{id} | A pathway node with its lineage and member interactions. |
| /api/pathways/tree | The full pathway scaffold. |
| /api/highlights | The best evidenced interactions. |
| /api/protein/{symbol}/network?format= | Network export as tsv, sif, or graphml, for Cytoscape and networkx. |
Every parameter and response schema is documented in the interactive API reference.
propaths-mcp exposes the same reads as read-only tools over the Model Context Protocol. It is a thin client over this API, so tool output is the API's JSON unchanged. It also ships MCP resources and prompts, so an agent can orient itself without being told the schema.
The API is public, keyless, read only, and rate limited per client. Nothing in it writes to the graph.
For higher rate limits, enrichment access, a hosted MCP server, or a protein mapped for your lab, get in touch.
The demo reads from this same graph. Every interaction you open there is one API call away.