Skip to main content
The Judt MCP server exposes the Judt API as native tools, so your agent can discover and call operations directly without parsing the OpenAPI specification. Use MCP whenever your agent or editor supports the Model Context Protocol.

Get an API key

Create an API key in the Judt dashboard to authenticate your MCP client:
1

Open the API keys page

In the Judt dashboard, go to API keys and click Create key.
2

Set the name and expiration

Set the following fields:
  • Name: the client or agent name, such as Cursor or Claude Code.
  • Expires: select a short expiration window such as 1 day or 7 days (recommended), or a longer window if needed.
Click Create key and copy the key (judt_...). The dashboard shows the key only once.
3

Store the key in an environment variable

If your client reads credentials from your shell environment, export the key without saving it to your shell history:
A key from the dashboard reaches all Apps in the organization. Unless your agent needs to create new Apps, use this key to create an App token with POST /api/tokens, and give the App token to the agent:
  • The agent can read and modify only that App (GET /api/apps returns only that App, and requests to any other App return 404 not_found).
  • The agent cannot create new Apps (403 app_scoped_token).
  • The token expires after the time you set, up to 24 hours. For more details, see Give an agent access to a single App.
If you’re using MCP in an agent your users/customers use, it’s recommended to use the create token API dynamically to generate a token you embed into the MCP config for the agent. This way the agent does not have access to all Apps — only the one the user should have access to.

Configure your MCP client

The Judt MCP server uses the Streamable HTTP transport at:
Pass your API key in the Authorization header as a bearer token (Authorization: Bearer JUDT_API_KEY). Select your client below for the exact configuration:
Add the judt server to ~/.cursor/mcp.json (or your client’s mcpServers JSON configuration):
mcp.json
Replace JUDT_API_KEY with your judt_... key. Keep this file in your home directory so you do not commit the key to a repository.

How your agent edits Apps

Your agent writes the code itself. It reads and changes files (list_files, read_file, edit_file, write_file, delete_file), runs shell commands (run_command), tests on the dev server (create_preview), commits (create_commit), and publishes (deploy). For how the code in an App works, see Build Apps. The MCP server has no tools for the in-product Judt agent. To give work to the Judt agent, use the dashboard or the API.

Available MCP tools

The server has tools for your account, Apps, files, the sandbox, deployments, Secrets, and logs. For each tool, the API operation that it sends, its annotations, and how authentication and errors work, see the MCP server reference.
No MCP tool takes a Secret value, so a value never goes through your model provider’s context window. request_secrets gives the user a link to the App’s Secrets page in the Judt dashboard, where the user types the values. See Secrets.