energy-claude-mcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@energy-claude-mcpAsk Claude to summarize this conversation thread."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Energy Claude MCP
Use an existing Claude subscription inside Energy without changing Energy itself.
Energy's GPT agent sees one MCP tool, ask_claude. The tool invokes the official authenticated Claude Code CLI and keeps one Claude session per Energy thread, including across bridge restarts.
Energy GPT -> localhost MCP -> Claude Code CLI -> Claude subscriptionRequirements
Node.js 20 or newer
Claude Code installed and signed in
An Energy version that can connect to a custom HTTP MCP server
Check Claude before starting:
claude --version
claude auth statusRelated MCP server: Collaborative MCP Proxy Server
Run
git clone https://github.com/noahljungberg/energy-claude-mcp.git
cd energy-claude-mcp
npm ci
npm run build
npm startThe bridge listens at http://127.0.0.1:4379/mcp.
In Energy:
Open the profile menu and choose Connect Tools.
Open MCP, choose Add MCP server, and paste
http://127.0.0.1:4379/mcp.Connect it and start a new task.
Keep the bridge process running while using it.
Options
npm start -- \
--claude /path/to/claude \
--data-dir ~/.energy-claude-mcp \
--port 4379The defaults are claude, ~/.energy-claude-mcp, and port 4379. Claude Code uses its configured default model.
Boundaries
The server binds only to
127.0.0.1and uses the MCP SDK's localhost host validation.It invokes Claude Code in safe mode with Claude-side tools disabled.
It never reads or copies Claude OAuth credentials.
Energy-thread mappings are stored in
~/.energy-claude-mcp/sessions.jsonwith owner-only permissions.GPT remains Energy's outer coordinator. The tool description tells it to delegate and return Claude's answer verbatim, but this is not a direct model-provider replacement: GPT can still decide how to use the tool, consumes its own allowance, and may rewrite the result.
Verify
npm test
npm run typecheck
npm run buildThe tests exercise the MCP protocol, first-turn and resumed Claude calls, restart persistence, concurrent thread mappings, and error boundaries with a fake Claude executable. They do not consume Claude allowance.
License
MIT
This server cannot be deployed
Maintenance
Related MCP Connectors
- QuallaaOAuthcom.quallaa
Talk to your public-facing AI from any MCP client — Claude, ChatGPT, Cursor, Cline, Windsurf.
Hosted MCP server connecting claude.ai, ChatGPT and other AI apps to your own computer
Share one project context across ChatGPT, Claude, Telegram and any MCP client.
One MCP endpoint for Claude, GPT & Gemini: 100+ tools + no-code connectors + agent workers.
Related MCP Servers
- AlicenseNot gradedqualityFmaintenanceThe self-hosted MCP bridge between Claude Chat and Claude Code.46AGPL 3.0
- FlicenseNot gradedqualityDmaintenanceEnables multi-AI collaborative analysis by proxying requests to existing login-based MCP servers (Gemini CLI and Codex CLI) from Claude Desktop or Claude Code.-
- AlicenseNot gradedqualityDmaintenanceEnables Claude Code Desktop to call OpenAI Codex/GPT-5 and Gemini APIs via stdio MCP, without requiring local CLI tools.MIT
- AlicenseNot gradedqualityBmaintenanceAn MCP server that bridges Claude Desktop with Claude Code, allowing users to delegate tasks to Claude Code directly from Claude Desktop conversations, supporting both synchronous and background execution with session reuse.2 npmMIT