The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Animal Checklist listing page.
Animal Checklist offers two remote MCP servers over Streamable HTTP.
| Server | URL | Access |
|---|---|---|
| Species catalogue | https://animalchecklist.com/mcp | Public, read only |
| Your account | https://animalchecklist.com/mcp/account | Personal MCP key |
The public server searches animal species and returns names, habitats, countries, photos and source credits. The account server also reads your synced sightings. A read-write key can mark a catalogue species seen.
Create a personal key on your Account page. Choose a read key unless your MCP app must mark animals seen. Copy the key when it appears; Animal Checklist shows it only once. Remove it from the same page when you no longer use the app. Keys expire after 90 days.
Configure the account server with this HTTP header:
Keep the key in your MCP client's secret store. Do not commit it to a repository. The public mcp.json contains only the keyless catalogue server because the Agent Plugins 1.0.0 format does not define portable secret references.
The server.json and server-account.json files describe both servers for the official MCP Registry. The mcp.json file provides a portable public-server connection. See the developer guide for tool details and a client config example.