Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@WoRMS MCP Look up the taxonomy and common names for the blue whale."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
WoRMS (World Register of Marine Species) MCP — keyless.
Part of Pipeworx — an MCP gateway connecting AI agents to 1684+ live data sources.
Tool | Description |
| Resolve a marine species or genus name to its WoRMS AphiaID, accepted name, authority, status (accepted/unaccepted), rank, and high-level classification (kingdom/family/genus). WoRMS is the authoritative world register of marine species. Keyless. |
| Walk the full taxonomic lineage (root → tip) for a WoRMS AphiaID: returns a flat ordered array of { rank, name, aphia_id } from superdomain down to the taxon itself. Keyless. |
| Get common (vernacular) names for a WoRMS AphiaID across languages. Keyless. |
Related MCP server: mcp-catalogueoflife
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"worms": {
"url": "https://gateway.pipeworx.io/worms/mcp"
}
}
}tools/list at https://gateway.pipeworx.io/worms/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}Both URLs reach the same gateway and the same 1684+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
curl -X POST https://gateway.pipeworx.io/v1/tools/worms_search_species \
-H 'Content-Type: application/json' \
-d '{"name":"Orcinus orca"}'No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/worms_search_species. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.
This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:
{
"mcpServers": {
"worms": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-worms"]
}
}
}Or run it directly to confirm it starts:
npx -y @pipeworx/mcp-wormsIt speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call
for only this pack's tools — none of the shared meta-tools the gateway
connection above adds. Same source, same tools, no ask_pipeworx routing.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Worms data" })The gateway picks the right tool and fills the arguments automatically.
MIT
This server cannot be deployed
GBIF MCP — wraps the Global Biodiversity Information Facility API v1 (free, no auth)
OBIS (Ocean Biodiversity Information System) MCP.
Catalogue of Life MCP — global taxonomic index.
ITIS (Integrated Taxonomic Information System) MCP.