Connect Continue to Entalpa
Continue supports MCP blocks and remote HTTP-based transports. Add Entalpa through Continue MCP configuration, then use Entalpa server instructions for workflow guidance.
before you start
Continue 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- Continue installed with Agent Mode enabled.
- Browser access for OAuth if the current Continue build supports OAuth for remote MCP.
Add remote MCP config
mcpServers:
- name: entalpa
type: streamable-http
url: https://api.entalpa.com/mcpStandalone MCP server block
If you use a .continue/mcpServers/entalpa.yaml block instead of inline config, include Continue's required block metadata such as name, version, and schema alongside the server definition.
SSE compatibility fallback
If the installed Continue version only exposes SSE examples, do not force Entalpa through SSE unless Entalpa publishes a compatible SSE endpoint.
Install from entalpa/entalpa-mcp's default branch for the latest skill, or use a release tag for a reproducible install.
Use server instructions
Continue's official MCP docs do not document local Agent Skills installation. Use the Entalpa MCP server instructions and these docs as the workflow guide until runtime skill loading is validated.
- Switch Continue to Agent Mode and confirm Entalpa tools appear.
- Continue's MCP configuration format has changed over time. Treat exact YAML keys as version-specific and validate before sharing a team config.
Where these instructions come from
Connecting a different client?
Stuck on a step? Email contact@entalpa.com