synapse-mcp

susheel/synapse-mcp

3.3

If you are the rightful owner of synapse-mcp and would like to certify it and/or have it hosted online, please leave a comment on the right or send an email to henry@mcphub.com.

A Model Context Protocol (MCP) server that exposes Synapse Entities (Datasets, Projects, Folders, Files, Tables) with their annotations and supports OAuth2 authentication.

Synapse MCP Server

synapse_wordmark

A Model Context Protocol (MCP) server that enables AI agent access to Synapse entities (Datasets, Projects, Folders, Files, Tables, and more).

You (your AI agent) can:

  • Retrieve entities by ID
  • Get entity annotations
  • List entity children
  • Search Synapse entities with path and type filters
  • Inspect provenance/activity recorded for an entity version

Available Tools

ToolFriendly NameDescription
get_entity(entity_id)Fetch EntityFetch core metadata for a Synapse entity by ID.
get_entity_annotations(entity_id)Fetch Entity AnnotationsReturn custom annotations associated with an entity.
get_entity_provenance(entity_id, version=None)Fetch Entity ProvenanceRetrieve provenance (activity) metadata for an entity, optionally scoped to a specific version.
get_entity_children(entity_id)List Entity ChildrenList children for container entities such as projects and folders.
search_synapse(query_term=None, ...)Search SynapseSearch Synapse entities by keyword with optional name/type/parent filters. Results are provided by Synapse as data custodian; attribution and licensing follow the source entity metadata.

Available Resources

Resources provide ready-to-present context that clients can pull without extra parameters. When you need to search or compute derived results, prefer tools instead.

ResourceFriendly NameDescription
synapse://feeds/blogSage Blog RSSLive RSS XML for the latest Sage Bionetworks publication posts.

Usage

This guide provides typical user instructions for connecting to the Synapse MCP server. For contributor setup, please see .

Authentication

The Synapse MCP server supports two authentication methods:

  1. OAuth2 (Default): This is the primary and recommended authentication method. It provides a secure, browser-based login flow. When your AI agent needs to access protected resources, it will prompt you to log in to Synapse in your browser. This method is used by default for both local and remote servers.

  2. Personal Access Token (PAT): This method is available for local development or in environments where a browser-based login is not feasible. It requires you to provide a Synapse Personal Access Token to the server.

MCP Server setup

Remote Server

Use this URL in your client: 🔌 https://mcp.synapse.org/mcp

Claude Desktop Instructions

Go to Settings > Connectors > Add custom connector

image
Claude Code

claude mcp add --transport http synapse -- https://mcp.synapse.org/mcp

Local Server

For running local server, see

Example Prompts

See

Contributing

Contributions are welcome! Please see our for instructions on setting up a development environment, running tests, and more.

License

MIT

Contact

synapse_icon

For issues, please file an issue. For other contact, see https://sagebionetworks.org/contact.