Koskamo

Remote Impact MCP

An official MCP server providing structured data on remote job opportunities at impact organizations. It allows AI agents to search for roles by area, eligibility, pay, and level, retrieving verification status, organization details, and application links to facilitate job searching and research.

Endpoint and access

No sign-in: your client connects and lists tools immediately, with no account or key.

Remote Impact MCP logo, by Remote ImpactNo sign-inEndpoint checked 2026-10-18Operated by Remote Impact
MCP endpoint (Streamable HTTP)
https://remoteimpact.org/mcp/
Vendor documentation

What you can do with it

  • Search for remote climate roles eligible from specific countries
  • Retrieve detailed job information including pay and experience level
  • List available job areas and organization details
  • Verify job listing status and source evidence
Tools advertised by the last live check:
  • search_jobs
  • get_job
  • list_areas
  • get_organization

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http remote-impact-mcp https://remoteimpact.org/mcp/

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add remote-impact-mcp --url https://remoteimpact.org/mcp/

Cursor

Merge this server into .cursor/mcp.json in your project, then enable remote-impact-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "remote-impact-mcp": {
      "url": "https://remoteimpact.org/mcp/"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.
Cline configuration
{
  "mcpServers": {
    "remote-impact-mcp": {
      "type": "streamableHttp",
      "url": "https://remoteimpact.org/mcp/",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start remote-impact-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "remote-impact-mcp": {
      "type": "http",
      "url": "https://remoteimpact.org/mcp/"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http remote-impact-mcp https://remoteimpact.org/mcp/

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.
Claude Desktop configuration
{
  "mcpServers": {
    "remote-impact-mcp": {
      "url": "https://remoteimpact.org/mcp/"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "remote-impact-mcp": {
      "serverUrl": "https://remoteimpact.org/mcp/"
    }
  }
}

Do you run Remote Impact MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing