Is an API Key required for Emissions API?

No. Emissions API is a free and open service. This server works out of the box without any static credentials required.

What gases can be audited via the agent?

You can query Carbon Monoxide (`carbonmonoxide`), Methane (`methane`), Ozone (`ozone`), and Nitrogen Dioxide (`nitrogendioxide`) using specialized tools.

Is the data historical or real-time?

The API provides historical measurement data collected by the Sentinel-5P satellite, typically updated daily with a short processing lag.

Emissions API MCP Server for VS Code Copilot 6 tools — connect in under 2 minutes

Name: Emissions API
Availability: InStock
Author: Vinkius

code.visualstudio.com/docs/copilot/chat/mcp-servers

Built by Vinkius GDPR 6 Tools IDE

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Emissions API and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

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

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Emissions API MCP Server

Empower your AI agent to orchestrate your entire environmental research workflow with Emissions API, the open source platform for satellite-based emission data. By connecting Emissions API to your agent, you transform complex gas monitoring into a natural conversation. Your agent can instantly query carbon monoxide, methane, and ozone levels for any country without you ever touching a technical portal. Whether you are conducting climate research or monitoring industrial impact, your agent acts as a real-time environmental analyst, ensuring your data is always grounded in precise, satellite-derived measurements.

GitHub Copilot Agent mode brings Emissions API data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 6 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

What you can do

Gas Auditing — Query real-time and historical levels of Carbon Monoxide, Methane, and Ozone to maintain a clear view of atmospheric composition.
Regional Oversight — Retrieve emission data for specific countries or geographic coordinates to understand local environmental trends.
Temporal Intelligence — Query data across specific date ranges to monitor changes in gas concentrations over time.
Spatial Discovery — Retrieve emission measurements in GeoJSON format to maintain strict control over geographic data distribution.
Product Discovery — List all available gas products in the catalog to identify relevant markers for your research.

The Emissions API MCP Server exposes 6 tools through the Vinkius. Connect it to VS Code Copilot in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Emissions API to VS Code Copilot via MCP

Follow these steps to integrate the Emissions API MCP Server with VS Code Copilot.

Create MCP config

Create a .vscode/mcp.json file in your project root

Add the server config

Paste the JSON configuration above

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown

Start using Emissions API

Ask Copilot: "Using Emissions API, help me...". 6 tools available

Why Use VS Code Copilot with the Emissions API MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with Emissions API through the Model Context Protocol.

VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor

Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

Emissions API + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the Emissions API MCP Server delivers measurable value.

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

Emissions API MCP Tools for VS Code Copilot (6)

These 6 tools become available when you connect Emissions API to VS Code Copilot via MCP:

get_available_products

List all available gas products in the database

get_carbon_monoxide

Get carbon monoxide emission data

get_geojson_emissions

Get emission data in GeoJSON format

get_methane

Get methane emission data

get_nitrogen_dioxide

Get nitrogen dioxide emission data

get_ozone

Get ozone emission data

Example Prompts for Emissions API in VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot agent to start working with Emissions API immediately.

"What is the latest carbon monoxide level in Germany (DE)?"

"List all available gas products in the Emissions API."

"Show methane emission trends for the last 30 days in the US."

Troubleshooting Emissions API MCP Server with VS Code Copilot

Common issues when connecting Emissions API to VS Code Copilot through the Vinkius, and how to resolve them.

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

Emissions API + VS Code Copilot FAQ

Common questions about integrating Emissions API MCP Server with VS Code Copilot.

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.