Connecting Encore's MCP Servers
Instructions
Pick the servers
| Server | Gives the agent | Needs |
|---|---|---|
Local (encore-local) |
The app on this machine: services and endpoints, calling endpoints, local traces, database schemas and queries, Pub/Sub, buckets, caches, cron jobs, and Encore docs | The Encore CLI (encore-install) and an Encore app |
Encore Cloud (encore-cloud) |
Deployed apps: environments, deploys and build logs, traces, metrics, database schemas and queries, infrastructure, secrets metadata, and the deployed source | An Encore Cloud account, and a person to approve access, or an API key |
Most agents benefit from both: local while building, Encore Cloud for deploys and production. Set up the ones the user asked for. If they didn't say, ask.
Most tools load MCP servers when they start. After adding one, ask the user to restart or reload their tool, then check that it's connected.
Local server
From the app's root directory, get the app's ID:
encore mcp startIt prints
MCP stdio Command: encore mcp run --app=<app-id>and an SSE URL. Use this ID, not theidinencore.app: apps that aren't on Encore Cloud have an emptyidthere and a local ID here.Add the server to the user's tool:
Claude Code: run from the app's root directory:
claude mcp add --transport stdio encore-local -- encore mcp run --app=<app-id>This adds it for this project, for this user. Add
--scope projectto share it with the team through.mcp.json.Cursor: add to
.cursor/mcp.json:{ "mcpServers": { "encore-local": { "command": "encore", "args": ["mcp", "run", "--app=<app-id>"] } } }VS Code: add to
.vscode/mcp.json. VS Code usesservers, notmcpServers:{ "servers": { "encore-local": { "command": "encore", "args": ["mcp", "run", "--app=<app-id>"] } } }Other tools: a stdio server with the command
encore mcp run --app=<app-id>, or an SSE server athttp://localhost:9900/sse?app=<app-id>.
If
encoreisn't on the tool's PATH, which is common for editors started from the dock or start menu, use the full path fromwhich encoreas the command. Write it out in full, such as/Users/<user>/.encore/bin/encore: config files don't expand~.Check it:
claude mcp listin Claude Code, or the tool's MCP settings, should showencore-localas connected. Then call itsget_servicestool.
The app doesn't need to be running. call_endpoint starts it, and the database tools start the local databases, which needs Docker. Traces exist only for requests the local app has served.
Encore Cloud server
The server is at https://api.encore.dev/mcp, over HTTP. It isn't tied to one app: with OAuth, it sees every app the user can access.
Add the server to the user's tool:
Claude Code:
claude mcp add --transport http --scope user encore-cloud https://api.encore.dev/mcp--scope usermakes it available in every project. Leave it out to add it to this project only.Cursor: add to
~/.cursor/mcp.jsonfor every project, or.cursor/mcp.jsonfor one:{ "mcpServers": { "encore-cloud": { "url": "https://api.encore.dev/mcp" } } }VS Code: add to
.vscode/mcp.json:{ "servers": { "encore-cloud": { "type": "http", "url": "https://api.encore.dev/mcp" } } }Other tools: an HTTP (streamable HTTP) server at
https://api.encore.dev/mcp.
Ask the user to authenticate. The agent can't do this step, because a person approves access in a browser:
- Claude Code: the user runs
/mcp, selectsencore-cloud, and chooses Authenticate. - Cursor, VS Code, and other tools: the user starts the sign-in for
encore-cloudfrom the tool's MCP settings, or from the prompt the tool shows.
- Claude Code: the user runs
Check it: call the
app_listtool. It lists the user's apps.
Encore Cloud without a person: API key
For CI or when nobody can approve access in a browser, use an API key.
Ask the user to create one in the Cloud Dashboard: the app's Settings > Access > API Keys. API keys start with
enpk_. They're different from the auth keys under Auth Keys, which log in the CLI (encore-login). A key belongs to one app, and the server only lists the tools its scopes allow, so pick scopes for the tools the agent needs.Have the user put it in an environment variable, such as
ENCORE_API_KEY, and add the server with anAuthorizationheader:claude mcp add --transport http encore-cloud https://api.encore.dev/mcp \ --header "Authorization: Bearer $ENCORE_API_KEY"In other tools, add
"headers": {"Authorization": "Bearer <api-key>"}to the server's entry, in a config file that isn't committed, such as a user-level one.Check it with a tool the key's scopes allow.
Troubleshooting
- The server doesn't appear: the tool hasn't reloaded its MCP config. Ask the user to restart it.
encore-localfails to start: runencore mcp run --app=<app-id>in a terminal to see the error. Usuallyencoreisn't on the tool's PATH (use the full path), or the app ID is wrong (runencore mcp startagain).encore-cloudsays authentication is required: the user hasn't finished OAuth (step 2), or the API key is wrong, expired, or deleted.encore-cloudlists few or no tools with an API key: the key's scopes don't cover them. Ask the user to add scopes or create a new key.
Guidelines
- Never ask the user to paste an API key into the chat, and never commit one. Keep it in an environment variable or a config file outside the repository.
- MCP tools can query databases and call endpoints. The user's tool asks before running them, depending on its approval settings.
encore llm-rules init --llm-rules=<tool>sets up the local server together with Encore's coding rules forcursor,claudecode,vscode, orzed, for apps that are on Encore Cloud. Use it when the user also wants the rules files.- Docs: https://encore.dev/docs/mcp and https://encore.dev/docs/platform/cloud-mcp