Emissions Database MCP server
{
"mcpServers": {
"mycelium-emissions-database": {
"type": "http",
"url": "https://mycelium.global/mcp/server"
}
}
}{
"mcpServers": {
"mycelium-emissions-database": {
"type": "http",
"url": "https://mycelium.global/mcp/server"
}
}
}{
"mcpServers": {
"mycelium-emissions-database": {
"type": "http",
"url": "https://mycelium.global/mcp/server"
}
}
}{
"servers": {
"mycelium-emissions-database": {
"type": "http",
"url": "https://mycelium.global/mcp/server"
}
}
}{
"mcpServers": {
"mycelium-emissions-database": {
"type": "http",
"url": "https://mycelium.global/mcp/server"
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsonversion 1.0.0
What it does
This server provides access to the Mycelium open corporate carbon emissions database, allowing AI assistants to search companies and retrieve their greenhouse gas figures across Scope 1, 2, and 3 emissions, along with Mycelium Scores and transparency ratings. It is for developers building applications that need to incorporate corporate emissions data and carbon disclosure information.
- Search for a company's carbon emissions profile and retrieve its Mycelium Score and industry ranking.
- Get detailed greenhouse gas figures for a specific reporting year, broken down by emission scope and category.
- Compare multiple companies' emissions data to understand their carbon footprint relative to industry peers.
Tools this server exposes
| Tool | Does |
|---|---|
| search-entities | Search the emissions database for companies by name, with optional filtering by country and result limit. |
| get-entity-profile | Retrieve a company's Mycelium profile including identity, Mycelium Score, Transparency Score, and yearly emissions summaries. |
| get-emission-figures | Get full greenhouse gas figures for a specific reporting year, with per-scope breakdowns tagged as reported or estimated. |
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.