Synapse MCP Server

The official MCP server for Synapse.org, maintained under the Sage-Bionetworks GitHub organisation, this Workstream's own co-chairing institution, and confirmed real and actively developed (deployed to production AWS ECS via a companion infrastructure repository, MIT licence confirmed by direct fetch of the repository's own root LICENSE file, copyright Sage Bionetworks 2025). It exposes Synapse entities, Datasets, Projects, Folders, Files, and Tables, as MCP tools, and its own description names genomics, imaging, and clinical data on cancer, neurodegenerative disease, and rare disease as the content it makes searchable.

What distinguishes this from a bare data-browsing wrapper: the server's own tool set, confirmed directly from its README, includes real access-governance tooling over that data, not just reads, get_entity_provenance (data lineage, inputs, outputs, the activity that generated an entity), list_entity_acl/get_entity_acl/update_entity_acl/delete_entity_acl (auditing and managing sharing settings, recursively across a project subtree), and get_entity_permissions (what the authenticated caller may do). Authentication is real: OAuth2 login by default, or a Synapse Personal Access Token for headless use, with read and write tools dispatched through separate proxies so a client can be configured read-only.

Recorded as a marginal fit, honestly: Synapse does not implement a named GA4GH standard, and its access control (OAuth2/PAT/ACL) is Synapse's own platform security, not GA4GH Passport or DUO-style controls. It is nonetheless the strongest instance in this candidate pool of this registry's alternate relevance test, exposing genomic and health data under real, auditable access controls, at a genuine, Workstream-affiliated biomedical data platform, which is why it is included despite that gap.