Contextforge MCP Server

What the code does

We read the source, 20 h ago · rules 3dff92dd89df

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

# Placeholder credentials so the server passes Glama's startup check
# (zod validates non-empty strings; backend rejects the dummy key at query
# time, but introspection — tools/list, resources/list — is purely static).
# Real users MUST override these via -e CONTEXTFORGE_AP…

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add contextforge-mcp -- npx -y contextforge-mcp

{
  "mcpServers": {
    "contextforge-mcp": {
      "args": [
        "-y",
        "contextforge-mcp"
      ],
      "command": "npx"
    }
  }
}

[mcp_servers.contextforge-mcp]
command = "npx"
args = ["-y", "contextforge-mcp"]

{
  "mcpServers": {
    "contextforge-mcp": {
      "args": [
        "-y",
        "contextforge-mcp"
      ],
      "command": "npx"
    }
  }
}

{
  "mcpServers": {
    "contextforge-mcp": {
      "args": [
        "-y",
        "contextforge-mcp"
      ],
      "command": "npx"
    }
  }
}

This one needs environment variables set before it will start: CONTEXTFORGE_API_KEY (Your API key from the ContextForge dashboard at contextforge.dev), CONTEXTFORGE_API_URL (API endpoint URL (defaults to production)). The author declared them in the registry entry; get the values from the project itself.