Cdt Express Mcp

Name: Cdt Express Mcp
Author: RiskThinking

by RiskThinkingcommunityv0.5.3

An MCP server for interacting with Riskthinking.AI's CDT Express API to retrieve climate exposure, impact, probability-adjusted impact, distribution, physical assets, companies, and markets data. It supports local stdio transport and is packaged as an MCPB extension for the Claude desktop app.

From the registry: Interact with climate metrics via Riskthinking.AI's CDT Express API in supported AI chat experiences

GitHub Repository

Install & configure

Prerequisites

optional
Install Node.js
Node.js is needed to run the local stdio MCP server. The README optionally suggests using nvm to manage Node.js versions and running `nvm use` for the version in `.nvmrc`.
https://github.com/nvm-sh/nvm
required
Obtain a CDT Express API key
Create or retrieve your CDT Express API key from Riskthinking.AI. The server requires this key to access the CDT Express API.
https://velo.riskthinking.ai/cdt-express

Install in your client

Paste into the AI you're chatting with — it will figure out the rest

Please install the `cdt-express-mcp` MCP server into my current AI client (that's you).

Required prerequisites (do these first if not already done):
- **Obtain a CDT Express API key** — Create or retrieve your CDT Express API key from Riskthinking.AI. The server requires this key to access the CDT Express API. (https://velo.riskthinking.ai/cdt-express)

Optional prerequisites:
- Install Node.js — Node.js is needed to run the local stdio MCP server. The README optionally suggests using nvm to manage Node.js versions and running `nvm use` for the version in `.nvmrc`. (https://github.com/nvm-sh/nvm)

Canonical MCP server config (stdio transport):
- command: `node`
- args: ["<path-to-cdt-express-mcp-built-server>"]
- required environment variables:
  - `CDT_EXPRESS_API_KEY`: API key for accessing the Riskthinking.AI CDT Express API. (example: `<your-api-key>`)

Note: The README confirms stdio transport is supported, but it does not provide a canonical command/args invocation for running the server directly outside the Claude Desktop MCPB extension flow. The local server appears to require building from source (`npm i`, then packaging/build steps), so the executable path must be supplied from the built project output. No HTTP or SSE remote transport is currently supported according to the README.

Add this MCP server to my current client's config in the correct format for you. If you need secrets or credentials I haven't provided, ASK me — do not invent values or leave raw placeholders. After adding it, tell me how to verify the server is connected.

Note: The README confirms stdio transport is supported, but it does not provide a canonical command/args invocation for running the server directly outside the Claude Desktop MCPB extension flow. The local server appears to require building from source (`npm i`, then packaging/build steps), so the executable path must be supplied from the built project output. No HTTP or SSE remote transport is currently supported according to the README.