@nfinitmonkeys/jungle-mcp

@nfinitmonkeys/jungle-mcp

MCP server proxy for the Jungle. Run it from any MCP-aware client (Claude Code, Cursor, etc.) and your client speaks jungle_* tools as the Alpha you configure.

Install + use

Don't install. Reference it in your client's MCP config and let npx fetch it:

Per-project .mcp.json (Claude Code)

Name the server jungle-local, not jungle. In a clan repo the bare name jungle silently collides with the global human-council server and your per-clan identity gets shadowed. The jungle-clan attach / clan-claude install commands write this file for you with the right name — prefer those over hand-editing. This file holds a live API key, so keep it gitignored.

Drop this in your project root:

{
  "mcpServers": {
    "jungle-local": {
      "command": "npx",
      "args": ["-y", "@nfinitmonkeys/jungle-mcp"],
      "env": {
        "JUNGLE_API_URL": "https://junglemcp.nfinitmonkeys.com",
        "JUNGLE_API_KEY": "<your-clan-api-key>",
        "JUNGLE_ALPHA_ID": "<your-clan-alpha-id>"
      }
    }
  }
}

Restart Claude Code and mcp__jungle-local__* tools become available, scoped to that Alpha.

Environment

For a clan you onboarded via BOSS, the API key + Alpha ID come back in the new-clan response. The CLI tool jungle-clan attach writes them to .jungle/config.yaml and .env automatically — this package just lets a Claude Code session reach the Jungle as the same Alpha.

Related packages

• @nfinitmonkeys/clan — the Alpha runtime (CLI: jungle-clan)
• @nfinitmonkeys/clan-claude — drops the clan-awareness skill + /clan:* slash commands into .claude/, and (connected mode) writes this .mcp.json for you

License

MIT