Connect Zed to Entalpa
Configure Entalpa as a Zed custom remote MCP server with context_servers, then install the skills in Zed's documented skills path.
before you start
Zed will ask you to log in
The MCP server serves your own projects, so it authenticates you: the first connection opens a browser and asks for your Entalpa account. Register first, otherwise that prompt has nothing to accept. Registration is free, no card, and MCP calls never spend credits.
Create a free account- Current stable Zed build with MCP support.
- Browser access for OAuth.
Add through Zed settings
Open Settings, AI, MCP Servers, choose Add Server, then Add Remote Server. Name it entalpa, use https://api.entalpa.com/mcp, and leave the Authorization header unset so Zed starts standard MCP OAuth.
Direct remote MCP config
{
"context_servers": {
"entalpa": {
"url": "https://api.entalpa.com/mcp"
}
}
}Install from entalpa/entalpa-mcp's default branch for the latest skill, or use a release tag for a reproducible install.
Install the Entalpa skills manually
tmpdir="$(mktemp -d)"
git clone --depth 1 https://github.com/entalpa/entalpa-mcp.git "$tmpdir"
mkdir -p .agents/skills
cp -R "$tmpdir/skills/." .agents/skills/- Open the Zed Agent Panel and confirm the Entalpa MCP server status.
- If Zed prompts for OAuth because no Authorization header is configured, complete the browser authorization flow.
- Validate Entalpa OAuth behavior against the installed Zed build before sharing this as a team standard.
- Do not document a bridge until it is tested against the current stable Zed build.
Where these instructions come from
Connecting a different client?
Stuck on a step? Email contact@entalpa.com