LandOS MCP Server

Docs

LandOS MCP Server

Connect Claude and other AI assistants to your LandOS data using the Model Context Protocol.

Overview

LandOS exposes an MCP (Model Context Protocol) server so AI assistants like Claude can answer questions about your organization's projects, polygons, and analysis results directly — no copy-pasting data back and forth.

The MCP server is read-only and organization-scoped: it can only see data belonging to the organization that issued the API key you connect with.

Get an API key

API keys and the MCP server are available on the Pro plan.

Every connection is authenticated with a LandOS API key, scoped to one organization.

Go to Settings → Organization → Developers in your organization
Click Create key, give it a description, and copy the key — it's shown once

Treat this key like a password. Anyone with it can read all of your organization's projects, polygons, and analysis results.

Connect a client

Claude Code

claude mcp add --transport http --scope user landos https://api.landos.eco/mcp --header "X-API-Key: YOUR_API_KEY"

Start a new session and ask Claude to list your projects. Run /mcp in the session to confirm it connected.

Claude.ai / Claude Desktop

This is not supported by the LandOS MCP server doesn't support yet, but you can connect to it using the Claude Code client above.

Other MCP clients

Any client that supports streamable HTTP with a custom header can connect. The general shape:

{
  "mcpServers": {
    "landos": {
      "url": "https://api.landos.eco/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Some clients only support a bearer token rather than a custom header. If so, pass the same API key as the bearer token instead:

{
  "mcpServers": {
    "landos": {
      "url": "https://api.landos.eco/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Available tools

Tool	Description
`get_organization`	Returns the organization associated with the API key
`list_projects`	Lists projects, filterable by stage, country, or name search
`get_project`	Returns a project's details and its polygons
`get_polygon`	Returns a polygon's area, location, and analysis count
`list_analyses`	Lists all analyses run on a polygon, with status and progress
`get_analysis`	Returns an analysis's status and its result widgets as summaries
`get_widget`	Returns a single result widget's full data payload

get_analysis returns widget summaries (title, short and long summary text) rather than full data, since a single widget's payload can be very large. Use get_widget when the raw data is actually needed.

Managing access

API keys are managed the same way whether they're used for the REST API or the MCP server. Revoke a key at any time from Settings → Organization → Developers — this immediately disconnects any MCP client using it.

Reference

Each MCP tool calls a corresponding endpoint on the LandOS public REST API. If you're building your own integration rather than connecting an AI assistant, see the interactive API reference and try requests directly at the root of the API domain (Swagger UI, authenticated the same way with your API key).

Natural Risk 10 steps to develop a carbon project