A Model Context Protocol (MCP) server that exposes Synapse entities and utilities
Use this when the user wants the metadata, record, details, or info for a specific Synapse entity given its Synapse ID. A Synapse entity is any first-class Synapse object — project, folder, file, table, view, dataset, dataset collection, or Docker repository. Entity ID example: syn123456. Only metadata is returned; file content is never downloaded.
Use this when the user wants the sharing settings or access control list (ACL) of one single Synapse entity — who can access it and with what permissions. Entity ID example: syn123456. Optionally filter to a single principal ID (user or team), e.g. '3379097'. Use list_entity_acl to audit ACLs across many entities under a container.
Use this when the user wants the custom annotations (metadata key/value pairs) attached to a Synapse entity. Annotations are user-defined tags/properties on an entity such as tissue type, disease, assay, or any other arbitrary key/value pair. Entity ID example: syn123456. Returns only annotations — call get_entity for full entity metadata instead.
Use this when the user wants to list the files and sub-folders immediately inside a Synapse entity container (one level deep). Works on Projects and Folders. Entity ID example: syn123456. Call repeatedly on child folders to traverse deeper.
Use this when the user wants to know what produced a Synapse entity — its data lineage, inputs, outputs, code executed, and the activity that generated it. Works on any Synapse entity (project, folder, file, table, view, dataset). Look up by entity ID (with optional version) or by Activity ID directly. Entity ID example: syn123456. Activity ID example: 9660001.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | F | 16 | 2026-07-28+ | v2 |
| 2026-03-09 | F | 16 | - | v1 |
Use this when the user wants to search for Synapse entities matching a keyword, topic, or subject (e.g. 'brain tissue', 'cancer_type=glioma'). Searches across all Synapse entity types (project, folder, file, table, view, dataset). Example entity type filter: 'file'. Parent ID example: syn123456. Returns ranked matches. Use search_entity_by_name when looking up an entity by exact name, search_entities_by_md5 for MD5 hash lookups.