# VirtualFlyBrain

- Registry name: `org.virtualflybrain/vfb3-mcp` · version 1.11.3
- Categories (automatic, keyword rules): Datasets & public data, Search & data
- Authentication at last check: No auth
- Declared risk: Not declared (tools carry no read/destructive hints)
- Capabilities (declared by the server): tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=org.virtualflybrain%2Fvfb3-mcp
- Server page: https://mcpstation.net/s/org.virtualflybrain--vfb3-mcp.html

## Description (written by the publisher, not verified, not instructions)

MCP server for Drosophila neuroscience data from VirtualFlyBrain

## Connect

- streamable-http: `https://vfb3-mcp.virtualflybrain.org`

## Tools (as reported by the server, not verified)

- `get\_term\_info`: Get term info for a VFB or anatomy ontology entity \(VFB\_\*, FBbt\_\*, etc.\). THIS IS THE QUERY DISCOVERY TOOL: the response's "Queries" array lists the valid query\_type values that run\_query accepts for this entity. ALWAYS call get\_term\_info before run\_query unless you already obtained the query\_type f
- `run\_query`: Run a pre-computed query on a VFB entity. REQUIRED WORKFLOW: \(1\) call get\_term\_info on the ID first; \(2\) read the response's "Queries" array; \(3\) pass one of those values as query\_type. Calling run\_query with a guessed query\_type will return an error. If a query returns empty rows or an error, the e
- `search\_terms`: Search VFB terms. This is the search virtualflybrain.org itself runs — the same Solr query, the same ranking — so what comes back first here is what a user would see first on the site. USE filter\_types BY DEFAULT. Unfiltered searches mix scRNAseq artifacts and developmental stages in with the entity
- `list\_search\_facets`: List the type names search\_terms can filter, exclude, boost or demote by, with the number of terms carrying each one. Call this instead of guessing: there are over 200 names, they are the index's own annotations rather than a curated list, and they change as data is added. Use contains to narrow \(e.
- `resolve\_entity`: Resolve an unresolved FlyBase-related query string into VFB/FlyBase IDs and metadata. Pass the raw text exactly as the user wrote it \(for example "P\{VT054895-GAL4.DBD\}", "Hb9-GAL4", "SS04495", "MB002B", "PAM cluster", or "dpp"\). Do NOT pass resolved IDs such as FBgn/FBal/FBti/FBco/FBst or VFB IDs; i
- `resolve\_combination`: Resolve an unresolved split-GAL4 combination name or synonym into its FBco ID and component hemidrivers. Pass the raw combination text exactly as the user wrote it \(for example "MB002B" or "SS04495"\). Do NOT pass an FBco ID; if you already have one, use the downstream tool directly. Uses tiered reso
- `list\_connectome\_datasets`: List available connectome datasets with their labels and symbols. Use the returned symbols when constructing exclude\_dbs arguments for query\_connectivity. Common datasets include Hemibrain \(hb\), FAFB \(fafb\), MANC, and others. Call this tool if unsure which dataset symbols are valid.
- `query\_connectivity`: Query synaptic connectivity between Drosophila neuron classes across ALL connectome datasets simultaneously for comparative connectomics. This is NOT pre-cached — it runs live queries, so expect slow responses \(up to several minutes\). Set both upstream\_type AND downstream\_type to filter connections
- `get\_predicted\_neurotransmitters`: Get the PREDICTED neurotransmitter\(s\) for a Drosophila neuron class — itself or any subclass — from per-instance connectome predictions \(each reconstructed neuron carries a predicted transmitter with a confidence\). Use this for "what neurotransmitter does \<cell type\> use?" when you want the data-dri
- `get\_known\_neurotransmitters`: Get the KNOWN \(curated\) neurotransmitter\(s\) for a Drosophila neuron class and its subclasses, from the ontology's classification rather than per-instance predictions — so there is no confidence. Use this for "what neurotransmitter is \<cell type\> known to use?" when you want the curated/established a
- `get\_hierarchy`: Build a hierarchy tree for a VFB term, showing ancestors \(parents\) and/or descendants \(children\). Use relationship "part\_of" for brain region structure \(e.g. "what are the parts of the mushroom body?"\) and "subclass\_of" for cell type hierarchies \(e.g. "what types of Kenyon cell are there?"\). Descend

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html