Connect Cursor to Entalpa
Use Cursor's self-service Add to Cursor link for one-click MCP setup, with MCP settings or .cursor/mcp.json as fallbacks, then install the skills separately.
before you start
Cursor 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- Cursor version with remote MCP and OAuth support.
- Browser access for OAuth.
One-click Add to Cursor path
Open cursor://anysphere.cursor-deeplink/mcp/install?name=entalpa&config=eyJ1cmwiOiJodHRwczovL2FwaS5lbnRhbHBhLmNvbS9tY3AifQ, review the remote-server configuration, and complete OAuth when Cursor prompts.
Add through Cursor settings
Open Cursor Customize, then MCP, add a new remote server named entalpa, and use URL https://api.entalpa.com/mcp. You can also edit project .cursor/mcp.json or global ~/.cursor/mcp.json.
Manual project config
{
"mcpServers": {
"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
npx skills add entalpa/entalpa-mcp --skill "*" --agent cursor -g -yGitHub CLI alternative
gh skill install entalpa/entalpa-mcp entalpa-implement --agent cursor --scope user
gh skill install entalpa/entalpa-mcp entalpa-prd --agent cursor --scope user- Reload Cursor and confirm Entalpa appears in MCP tools.
- Ask Cursor to call
users_get_meor list projects.
- Keep manual settings available when workspace policy blocks deep links, and retain OAuth runtime validation before treating the published one-click link as the only path.
Where these instructions come from
Connecting a different client?
Stuck on a step? Email contact@entalpa.com