PhyloPic MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_taxaA | Search for phylogenetic nodes (taxa) in PhyloPic by name. Returns matching nodes with their UUIDs, names, parent taxa, and primary images. The search text should be lower-case with non-alphabetic characters removed and whitespace trimmed (e.g. "primates", "homo sapiens", "aves"). |
| autocomplete_taxaA | Get autocomplete suggestions for taxonomic names based on partial text. Useful for discovering what taxa are available in PhyloPic before doing a full search. Returns a list of matching name suggestions (e.g. query 'prim' returns 'primates', 'primatiformes', etc.). |
| get_nodeA | Get detailed information about a specific phylogenetic node by its UUID. Returns the node's names, parent node, primary image, and child nodes. Can optionally embed the parent node and primary image data in the response. |
| get_node_lineageB | Get the ancestral lineage (chain of parent taxa) for a given phylogenetic node. Returns a list of nodes from the immediate parent up to the root of the tree of life. Useful for understanding the taxonomic classification of an organism. |
| get_root_nodeA | Get the root phylogenetic node (the ancestor of all organisms in PhyloPic's database). This is the top of the tree of life. Can optionally embed the primary image data. |
| get_imageA | Get detailed information about a specific silhouette image by its UUID. Returns the image's contributor, taxonomic nodes, license, and links to all available file formats (source file, vector SVG, raster PNG files at various sizes, and thumbnail files). Can optionally embed the contributor, specific node, general node, and full lineage nodes. |
| search_images_by_nodeA | List silhouette images that directly represent a specific phylogenetic node. Use this to find all images of a particular taxon (e.g. all images of Homo sapiens). For ancestral nodes, consider using 'search_images_by_clade' instead to get images of all descendant taxa as well. |
| search_images_by_cladeA | List silhouette images within a clade (a node and all its descendants). This is useful for ancestral nodes — for example, getting all images of mammals, birds, or insects. Images are roughly sorted by their subject matter's proximity to the clade root node. |
| list_images_by_contributorB | List silhouette images contributed by a specific PhyloPic contributor. Use this to browse all images uploaded by a particular artist or contributor. |
| list_contributorsB | List all PhyloPic contributors (artists who have uploaded silhouette images). Contributors are sorted by image count (most prolific first). Each contributor entry includes their name, UUID, total image count, and contact info if available. |
| get_contributorA | Get detailed information about a specific PhyloPic contributor by their UUID. Returns the contributor's name, total image count, creation date, and contact information if available. |
| list_licensesA | List all Creative Commons licenses available for new image submissions to PhyloPic. Each license includes a link to the full license text. Useful for understanding what licenses are accepted when contributing images. |
| list_namespacesA | List all authorized external taxonomic database namespaces that can be used for resolving external identifiers to PhyloPic nodes. These include databases like GBIF, Open Tree of Life, NCBI, Paleobiology Database, and more. Each namespace has an authority and a namespace identifier. |
| resolve_external_idA | Resolve an external taxonomic database identifier to the closest matching PhyloPic phylogenetic node. For example, resolve a GBIF species key or an NCBI taxon ID to find the corresponding PhyloPic node. Use 'list_namespaces' first to see available authorities and namespaces. |
| get_api_infoA | Get general information about the PhyloPic API, including the current build number, API version, and available resource endpoints. Useful for checking API status and discovering available endpoints. |
| pingA | Check if the PhyloPic API is operational. Returns a simple status message. Useful for health checks and connectivity verification. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 16 tools
Each tool targets a distinct resource or action: taxa search, autocomplete, node retrieval, lineage, root node, image retrieval, image search by node vs clade, contributor listing/retrieval, licenses, namespaces, external ID resolution, and API health/info. The only mild overlap is search_taxa versus autocomplete_taxa, but their descriptions clearly separate full search from partial-name suggestions.
Tool names consistently use snake_case with predictable verb_noun or verb_noun_phrase patterns such as get_node, search_images_by_node, list_contributors, and resolve_external_id. The only deviation is ping, which is a conventional single-verb health-check name and does not disrupt the overall consistency.
At 16 tools, the server is slightly above the ideal 3–15 range but still reasonable for a read-only taxonomic image API with several resource families. Each tool appears to earn its place rather than being redundant, though a few could potentially be consolidated if the API surface were trimmed.
The surface covers the core read-only lifecycle well: taxa search/autocomplete, node details/lineage/root, image retrieval and search by node or clade, contributor metadata, licenses, namespaces, external ID resolution, and API health/status. Minor gaps include no direct text-based image search or binary file retrieval, though get_image provides links to available file formats.