Pondlog Inaturalist
Let your coding agent query iNaturalist wildlife observations, species counts, taxa, and places while you build nature or field-guide products.
Overview
Pondlog iNaturalist is a Build-phase MCP server that lets coding agents fetch wildlife observations, species counts, taxa, and places from iNaturalist worldwide.
What is this MCP server?
- stdio MCP transport via npm package @pondlog/mcp-inaturalist (v0.1.3)
- Worldwide wildlife observations, species counts, taxa, and place lookups
- Part of the Pondlog citizen-science MCP family on GitHub (andrewschristison/pondlog)
- No API key described in the server manifest—suited for quick local agent registration
- Pairs with other Pondlog servers (phenology, water, fungi) for multi-source nature apps
- Server schema version 0.1.3; npm identifier @pondlog/mcp-inaturalist
- Transport: stdio per MCP server manifest
- Source repository: github.com/andrewschristison/pondlog
What problem does it solve?
Building nature or citizen-science features means repeatedly explaining iNaturalist endpoints to your agent instead of calling structured observation tools in-chat.
Who is it for?
Indie builders making species lists, biodiversity dashboards, or research assistants that must cite real iNaturalist observations and taxa.
Skip if: Teams that only need a one-off CSV export with no ongoing agent-driven development, or apps that require official iNaturalist OAuth flows this MCP does not document.
What do I get? / Deliverables
After you register the MCP server, your agent can query iNaturalist-backed entities while you scaffold APIs, copy, and data models for your product.
- Registered stdio MCP server exposing iNaturalist observation and taxa tools to your agent
- Agent-generated queries and prototypes grounded in live biodiversity entities
- Reusable integration pattern alongside other Pondlog nature MCP servers
Recommended MCP Servers
Journey fit
MCP servers are cataloged on the Build shelf because they wire external APIs into Claude Code, Cursor, and similar agents during product development. Integrations is the right subphase: this stdio MCP exposes iNaturalist as agent-callable tools rather than a standalone app feature.
How it compares
MCP data integration for iNaturalist, not a hosted iNaturalist mobile app or skills.sh prompt-only skill.
Common Questions / FAQ
Who is pondlog-inaturalist for?
Solo and indie developers using Claude Code, Cursor, or Codex who are building products that depend on iNaturalist wildlife and taxonomy data.
When should I use pondlog-inaturalist?
Use it during Build when you want your agent to search observations, species counts, taxa, and places while implementing features or drafting data-backed specs.
How do I add pondlog-inaturalist to my agent?
Install @pondlog/mcp-inaturalist from npm, add a stdio MCP entry pointing at that package in your agent’s MCP config, and restart the agent so tools load.