How to Use the Emissions API MCP in Claude Code

Q: How do I add the Emissions API to Claude Code?

Run claude mcp add --transport http emissions-api -- . Make sure you put all flags before the server name.

Q: How do I verify the Emissions API is working in Claude Code?

Run claude mcp list in your terminal. You should see all six tools registered and ready for invocation.

Pipe live environmental data directly into your terminal workflows using Claude Code and this MCP Server.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Emissions API MCP to Claude Code

Create your Vinkius account to connect Emissions API to Claude Code and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Emissions API with Claude Code

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Headless Environmental Auditing

You live in the terminal, and now your air quality data does too. Run a single command and watch your agent pull `get_carbon_monoxide` stats right into your shell. This makes it trivial to hook environmental checks into your existing bash scripts. Pipe the output to jq, filter for dangerous thresholds, and trigger alerts without ever opening a browser.

Automated CI/CD Pollution Checks via MCP Server

Build automated pipelines that verify local air conditions before deploying physical infrastructure. Your agent runs `get_nitrogen_dioxide` as part of a GitHub Action. If the levels exceed your defined limits, the pipeline halts. This MCP Server acts as the bridge between your deployment logic and the physical world's atmospheric data.

Raw Data Extraction and Mapping

Sometimes you just need raw spatial data dumped into a file. You tell your agent to fetch the latest grid, and it executes `get_geojson_emissions`. It also scans `get_available_products` to see what else is trackable, then pulls `get_methane` or `get_ozone` numbers. You get clean, structured data saved directly to your local filesystem.

Setup guide

Set up Emissions API MCP in Claude Code

Prerequisites

Claude Code CLI installed (npm install -g @anthropic-ai/claude-code)
Active Vinkius subscription with a valid endpoint token

1

Run the add command

Open your terminal and run the command shown on the right. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com. Use --scope user to make it available across all projects.
2

Verify the connection

Start a Claude Code session and type /mcp to list connected servers. You should see emissions-api-mcp with a green status indicator.
3

Start using tools

Ask Claude Code something like "Check my latest Emissions API transactions." It will automatically discover and invoke the available Emissions API tools.

Terminal

claude mcp add --transport http emissions-api-mcp https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp

Get your connection token →

Prerequisites

Claude Code CLI installed
Active Vinkius subscription with a valid endpoint token

1

Open the config file

Create or edit .mcp.json in your project root for project-level scope, or ~/.claude.json for user-level scope.
2

Add the Emissions API MCP

Paste the JSON snippet shown on the right into the mcpServers object. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Restart Claude Code

Start a new Claude Code session. Type /mcp to confirm the server is connected. The tools will be automatically available in your conversation.

.mcp.json

{
  "mcpServers": {
    "emissions-api-mcp": {
      "type": "url",
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Emissions API. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Emissions API now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Emissions API MCP in Claude Code

Run `claude mcp add --transport http emissions-api -- `. Make sure you put all flags before the server name.

Yes. Schedule headless executions that pull daily gas readings and append them to a log file.

Run `claude mcp list` in your terminal. You should see all six tools registered and ready for invocation.

It supports stdio, http, and sse. For remote execution, the HTTP transport is usually the easiest to configure.

Your bounding box coordinates and specific gas requests never persist. The infrastructure provisions a temporary sandbox for your `get_ozone` calls and destroys it immediately after the terminal receives the response.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript