MCP Integration

The Mangrove MCP server enables you to query your MRV data using natural language through AI assistants like Claude and Cursor. Instead of manually exporting data and building custom queries, you can ask questions conversationally and receive structured insights from your production, accounting, and inventory data.

What is MCP?

The Model Context Protocol (MCP) is an open standard that enables AI assistants to securely connect to external data sources and APIs. The Mangrove MCP server implements this protocol, providing a bridge between your Mangrove account and MCP-enabled tools.

MCP connections are read-only and respect your existing Mangrove API permissions. All queries are authenticated using your Mangrove API key.

Use Cases

The MCP integration is particularly useful for:

Ad-hoc reporting: Query specific metrics without building custom dashboards
Data validation: Quickly audit data completeness and identify gaps
Trend analysis: Ask questions about patterns across time periods or locations
Cross-referencing: Correlate data across events, batches, and locations

Available Data

The MCP server provides access to all Mangrove API endpoints. You can query:

Production Data

Projects, locations, feedstocks, event types, events, data points, and evidence files

Accounting & Reporting

Batches, ledger transactions, reports, models, and model runs

Inventory Management

Orders, issuances, retirements, and transfers

Account Administration

Account settings, user roles, and custom fields

For detailed information about each endpoint, see the API Reference sections.

Setup

Prerequisites

To connect to the Mangrove MCP server, you’ll need:

Mangrove API Key: Generate a read-only API key as an Account Admin in API Settings
MCP Auth Token: Provided by your Mangrove account team
MCP Server URL: https://mcp.gomangrove.com/mcp

Open your Claude Desktop configuration

In Claude Desktop, open Settings, select the Developer tab, and click Edit Config. This opens claude_desktop_config.json in your default editor and creates the file if you don’t have one yet.On macOS, Settings sits in the Claude menu in your top menu bar, not inside the Claude window.If your version of Claude Desktop has no Developer tab, open the file yourself:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json

touch ~/Library/Application\ Support/Claude/claude_desktop_config.json
open -e ~/Library/Application\ Support/Claude/claude_desktop_config.json

notepad "$env:APPDATA\Claude\claude_desktop_config.json"

Add the Mangrove MCP server

Add the following configuration to your claude_desktop_config.json:

{
  "mcpServers": {
    "mangrove": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.gomangrove.com/mcp",
        "--transport",
        "http-only",
        "--header",
        "Authorization:${AUTH_TOKEN}",
        "--header",
        "X-Mangrove-Token:${MANGROVE_API_TOKEN}"
      ],
      "env": {
        "AUTH_TOKEN": "Bearer YOUR_AUTH_TOKEN",
        "MANGROVE_API_TOKEN": "YOUR_MANGROVE_API_KEY"
      }
    }
  }
}

Your auth token and API key go in the env block, and nothing else needs to change:

In AUTH_TOKEN, replace YOUR_AUTH_TOKEN with your MCP auth token, keeping the word Bearer and the space before it ("Bearer abc123").
In MANGROVE_API_TOKEN, replace YOUR_MANGROVE_API_KEY with your API key from Mangrove API Settings.

Leave ${AUTH_TOKEN} and ${MANGROVE_API_TOKEN} in args exactly as written. They read the values from the env block.

Restart Claude Desktop

Close and reopen Claude Desktop to load the new configuration.

Verify the connection

In Claude Desktop, you should now see the Mangrove MCP server available. Try a simple query:“What projects do I have access to in Mangrove?”

Open Cursor settings

Navigate to Cursor Settings > MCP

Add a new MCP server

Click “Add Server” and enter the following configuration:

{
  "name": "mangrove",
  "command": "npx",
  "args": [
    "-y",
    "mcp-remote",
    "https://mcp.gomangrove.com/mcp",
    "--transport",
    "http-only",
    "--header",
    "Authorization:${AUTH_TOKEN}",
    "--header",
    "X-Mangrove-Token:${MANGROVE_API_TOKEN}"
  ],
  "env": {
    "AUTH_TOKEN": "Bearer YOUR_AUTH_TOKEN",
    "MANGROVE_API_TOKEN": "YOUR_MANGROVE_API_KEY"
  }
}

In env, replace YOUR_AUTH_TOKEN with your MCP auth token (keep Bearer and the space before it) and YOUR_MANGROVE_API_KEY with your API key. Leave ${AUTH_TOKEN} and ${MANGROVE_API_TOKEN} in args exactly as written.

Enable the server

Toggle the Mangrove MCP server to “enabled” in your Cursor settings.

Test the integration

Open a new chat in Cursor and ask:“Show me all events from the last week for project [your-project-id]”

VS Code has native MCP support via GitHub Copilot Chat (agent mode). You can configure the server at workspace level (.vscode/mcp.json, shareable with your team) or at user level (applies across all workspaces).

Open the MCP configuration

Open the Command Palette (Cmd/Ctrl+Shift+P) and run MCP: Open User Configuration to edit your personal mcp.json, or create .vscode/mcp.json in your workspace root to share with teammates.

Add the Mangrove MCP server

Add the following to your mcp.json:

{
  "servers": {
    "mangrove": {
      "type": "http",
      "url": "https://mcp.gomangrove.com/mcp",
      "headers": {
        "Authorization": "Bearer ${input:mangrove-auth-token}",
        "X-Mangrove-Token": "${input:mangrove-api-key}"
      }
    }
  },
  "inputs": [
    {
      "id": "mangrove-auth-token",
      "type": "promptString",
      "description": "Mangrove MCP auth token (from your Mangrove account team)",
      "password": true
    },
    {
      "id": "mangrove-api-key",
      "type": "promptString",
      "description": "Mangrove API key (from API Settings)",
      "password": true
    }
  ]
}

VS Code will prompt you for the auth token and API key the first time the server starts and store them securely.

Start the server

Click the Start action above the "mangrove" entry in mcp.json, or open Copilot Chat, switch to Agent mode, and select the Mangrove tools from the tool picker.

Test the integration

In Copilot Chat agent mode, ask:“What projects do I have access to in Mangrove?”

Claude Code is Anthropic’s CLI agent. It can connect to the Mangrove MCP server directly using the claude mcp add command.

Add the Mangrove MCP server

From any terminal, run:

claude mcp add --transport http mangrove \
  --scope user \
  --header "Authorization: Bearer YOUR_AUTH_TOKEN" \
  --header "X-Mangrove-Token: YOUR_MANGROVE_API_KEY" \
  https://mcp.gomangrove.com/mcp

Replace the placeholders:

YOUR_AUTH_TOKEN: Provided by your Mangrove account team
YOUR_MANGROVE_API_KEY: Your API key from Mangrove API Settings

The --scope user flag makes the server available in all your Claude Code projects. Omit it to install only for the current project.

Verify the connection

In any Claude Code session, run /mcp to confirm the mangrove server is connected, then ask:“What projects do I have access to in Mangrove?”

Codex CLI is OpenAI’s terminal agent. It supports remote MCP servers with static Bearer tokens and custom headers through its TOML config.

Set environment variables for your secrets

Add to your shell profile (~/.zshrc, ~/.bashrc, etc.):

export MANGROVE_AUTH_TOKEN="YOUR_AUTH_TOKEN"
export MANGROVE_API_TOKEN="YOUR_MANGROVE_API_KEY"

Reload your shell or run source ~/.zshrc after editing.

Add the server to ~/.codex/config.toml

Add the following block to ~/.codex/config.toml (create the file if it doesn’t exist):

[mcp_servers.mangrove]
url = "https://mcp.gomangrove.com/mcp"
bearer_token_env_var = "MANGROVE_AUTH_TOKEN"
env_http_headers = { "X-Mangrove-Token" = "MANGROVE_API_TOKEN" }

Codex automatically adds Authorization: Bearer ${MANGROVE_AUTH_TOKEN} from the env var.

Test the integration

Start a Codex session and ask:“What projects do I have access to in Mangrove?”

Gemini CLI is Google’s terminal agent. It connects to remote MCP servers over HTTP and sets custom headers itself, so it needs no bridge package.

Add the Mangrove MCP server

From any terminal, run:

gemini mcp add --transport http --scope user \
  --header "Authorization: Bearer YOUR_AUTH_TOKEN" \
  --header "X-Mangrove-Token: YOUR_MANGROVE_API_KEY" \
  mangrove https://mcp.gomangrove.com/mcp

Replace the placeholders:

YOUR_AUTH_TOKEN: Provided by your Mangrove account team
YOUR_MANGROVE_API_KEY: Your API key from Mangrove API Settings

--scope user writes to ~/.gemini/settings.json and makes the server available everywhere. Leave it off and Gemini CLI writes to .gemini/settings.json in your current directory, where the server is available only in that project.

Or configure it by hand

To edit the file yourself instead, add the server to ~/.gemini/settings.json:

{
  "mcpServers": {
    "mangrove": {
      "httpUrl": "https://mcp.gomangrove.com/mcp",
      "headers": {
        "Authorization": "Bearer $MANGROVE_AUTH_TOKEN",
        "X-Mangrove-Token": "$MANGROVE_API_TOKEN"
      }
    }
  }
}

Header values accept $VAR_NAME, so your credentials can live in environment variables rather than in the file. Set them in your shell profile:

export MANGROVE_AUTH_TOKEN="YOUR_AUTH_TOKEN"
export MANGROVE_API_TOKEN="YOUR_MANGROVE_API_KEY"

You can also paste the token values into the headers block directly.

Verify the connection

Run gemini mcp list from your shell, or /mcp inside a Gemini CLI session, to confirm the mangrove server shows as connected. Then ask:“What projects do I have access to in Mangrove?”

Connect multiple Mangrove accounts

If you manage more than one Mangrove account, you can connect all of them to the same assistant and ask about each one by name. Each Mangrove API key belongs to one account, so generate a key in each account’s API Settings and add the server once per account. The MCP auth token stays the same for every connection. Name each connection after its account, so you can tell the assistant which one to use. In Claude Desktop, add one entry per account to mcpServers. Only two things differ between entries: the name, and the API key in env. Each env block belongs to its own entry, so args stays exactly the same in both.

{
  "mcpServers": {
    "mangrove-account-a": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.gomangrove.com/mcp",
        "--transport",
        "http-only",
        "--header",
        "Authorization:${AUTH_TOKEN}",
        "--header",
        "X-Mangrove-Token:${MANGROVE_API_TOKEN}"
      ],
      "env": {
        "AUTH_TOKEN": "Bearer YOUR_AUTH_TOKEN",
        "MANGROVE_API_TOKEN": "ACCOUNT_A_API_KEY"
      }
    },
    "mangrove-account-b": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.gomangrove.com/mcp",
        "--transport",
        "http-only",
        "--header",
        "Authorization:${AUTH_TOKEN}",
        "--header",
        "X-Mangrove-Token:${MANGROVE_API_TOKEN}"
      ],
      "env": {
        "AUTH_TOKEN": "Bearer YOUR_AUTH_TOKEN",
        "MANGROVE_API_TOKEN": "ACCOUNT_B_API_KEY"
      }
    }
  }
}

In Claude Code, run claude mcp add once per account:

claude mcp add --transport http mangrove-account-a --scope user \
  --header "Authorization: Bearer YOUR_AUTH_TOKEN" \
  --header "X-Mangrove-Token: ACCOUNT_A_API_KEY" \
  https://mcp.gomangrove.com/mcp

claude mcp add --transport http mangrove-account-b --scope user \
  --header "Authorization: Bearer YOUR_AUTH_TOKEN" \
  --header "X-Mangrove-Token: ACCOUNT_B_API_KEY" \
  https://mcp.gomangrove.com/mcp

Replace ACCOUNT_A_API_KEY and ACCOUNT_B_API_KEY with each account’s API key. Cursor takes the same env blocks as Claude Desktop. In VS Code, Codex CLI and Gemini CLI, give each entry its own input id or environment variable for the API key (for example MANGROVE_API_TOKEN_A and MANGROVE_API_TOKEN_B); entries that share one read the same key and connect to the same account. Then name the account in your prompt:

"Using mangrove-account-b, list the projects in that account"

Example Prompts

Once connected, you can use natural language to query your Mangrove data. Here are example queries organized by common use cases:

Production & Operations

"Show me all events from project abc123 in the last 30 days that are missing data points"

"What locations are associated with project xyz789 and when was the last event recorded at each?"

Accounting & Compliance

"List all batches created in Q4 2024 with their CI scores, grouped by feedstock type"

"Which events from location loc_xyz have missing evidence files that I need for the upcoming audit?"

Analysis & Insights

"Compare the average mass flow rates across my three production locations over the past quarter"

"Show me the trend in CI scores for corn feedstock over the last 6 months"

Inventory & Credits

"What's the total volume of credits issued, retired, and transferred in 2024 for project abc123?"

"Show me all pending orders and their current status"

Important Considerations

AI-generated insights are produced by language models interpreting your Mangrove data. While powerful for exploration and analysis, always verify critical results against source data. MCP responses should complement, not replace, human judgment for compliance and reporting decisions.

The underlying data returned from Mangrove APIs is accurate and reflects your system of record. However, the AI assistant’s interpretation and summary of that data may occasionally contain inaccuracies or miss nuanced details.

Getting Started

API Cookbooks

Production Data

Accounting and Reporting

Credit Inventory Management

Account Admin

What is MCP?

Use Cases

Available Data

Production Data

Accounting & Reporting

Inventory Management

Account Administration

Setup

Prerequisites

Connect multiple Mangrove accounts

Example Prompts

Production & Operations

Accounting & Compliance

Analysis & Insights

Inventory & Credits

Important Considerations

​What is MCP?

​Use Cases

​Available Data

Production Data

Accounting & Reporting

Inventory Management

Account Administration

​Setup

​Prerequisites

​Connect multiple Mangrove accounts

​Example Prompts

​Production & Operations

​Accounting & Compliance

​Analysis & Insights

​Inventory & Credits

​Important Considerations

What is MCP?

Use Cases

Available Data

Setup

Prerequisites

Connect multiple Mangrove accounts

Example Prompts

Production & Operations

Accounting & Compliance

Analysis & Insights

Inventory & Credits

Important Considerations