Skip to content

Cursor inaturalist mcp server inaturalist_resolve_name

How to: Cursor inaturalist mcp server inaturalist_resolve_name

client:Cursor transport:streamable-http tool:inaturalist_resolve_name

Add inaturalist mcp server to Cursor

  1. 01

    Open ~/.cursor/mcp.json and merge this in. Keep any servers already there.

{
  "mcpServers": {
    "inaturalist-mcp-server": {
      "url": "https://inaturalist.caseyjhand.com/mcp"
    }
  }
}
  1. 02

    Save the file and restart Cursor.

  2. 03

    Ask for something inaturalist_resolve_name does. Cursor lists the server's tools on connect and calls inaturalist_resolve_name itself — you do not invoke it by name.

  3. 04

    If nothing happens, check the server is running and that inaturalist mcp server's identifier in your config matches the one above exactly.

Use .cursor/mcp.json in a project root instead to scope it to that project. Cursor merges both. Cursor docs

Set these first

inaturalist mcp server will not start until these are set, so inaturalist_resolve_name never becomes available.

  • MCP_LOG_LEVEL
  • INATURALIST_USER_AGENT
  • INATURALIST_MIN_REQUEST_INTERVAL_MS
  • INATURALIST_MAX_CONCURRENT_REQUESTS
  • INATURALIST_DAILY_REQUEST_BUDGET

Same tool, other clients

This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what the server actually exposes, not what its listing claims.

Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.