Skip to main content
When you give an external coding agent access to Judt, you can scope its credential to one specific App. An App token lets the agent edit files, run commands, preview, commit, and deploy that App without seeing or modifying any other App in your organization.

Choose how to connect the agent

Step 1: Create an App token

1

Make sure the App exists

In the Judt dashboard, select the App that the agent will work on, or click New App to create it first.
2

Get an organization-wide API key

Go to API keys and click Create key. Set a name and an expiration time, click Create key, and copy the key (judt_...). Keep this key for yourself. It reaches all Apps in the organization.Store the key in an environment variable so it does not appear in your shell history or source code:
3

Create the App token

Call POST /api/tokens with the ID of the App. expires_in is in seconds, from 60 to 86400 (24 hours). The default is 3600.
The token value in the response is the App token (judt_...). The response is the only place that shows it.
4

Give the token to the agent

Store the token in the environment of the agent:

What an App token can and cannot do

An App token acts with your organization role (owner, admin, or member) on the selected App only:
  • Allowed: Read the App (GET /api/apps returns only that App), read and write files, run commands, inspect Git status, create and restore commits, create preview links, and (if your role is owner or admin) manage Secrets and publish deployments for that App.
  • Blocked:
    • POST /api/apps and POST /api/tokens return 403 app_scoped_token.
    • Any request to /api/apps/{other_id} or /api/apps/{other_id}/* returns 404 not_found.
If you want an agent to edit and test code in the sandbox without being able to deploy to production, delete the App, or change Secrets, create the App token with an API key from an account that has the member role.

Step 2: Connect the agent

You can connect the agent through the MCP server or through the REST API.
Add the Judt MCP server (https://api.judt.ai/mcp) to your client with the App token in the Authorization header.For Claude Code:
For Codex, Cursor, and VS Code configuration files, see Configure your MCP client.Then give the agent its task:

Revoke access when finished

An App token stops working when it expires. To stop it earlier, go to API keys, open the menu of the token, and click Revoke. Any future request with that token immediately returns 401 unauthenticated.

Next steps