Access tokens

​

How access tokens work

• MCP only — the token works with the Juno MCP server and nothing else. The Juno REST API rejects it; to call the API, see API Overview.
• Acts as you — everything done with the token is done as the Admin who created it, with that Admin’s Juno permissions.
• Valid for 365 days — after that, create a new token.
• Revocable — revoke a token at any time and it stops working immediately.
• Tied to its creator — if the Admin who created it is deactivated, the token stops working.

​

Create a token

1

Open Developer Settings

Go to Admin → Security → Developer Settings and select Generate Personal Access Token.

2

Select MCP access

Select Connect AI assistants (MCP) on its own. An MCP access token can’t carry any of the other permissions in the list.

3

Name the token

Enter a Token name of up to 80 characters that says where the token is used — for example, GitHub Actions: weekly content report. The name is how you’ll find the token when it’s time to revoke it.

4

Generate and copy

Select Generate Token, copy the token, and store it somewhere secure right away. Juno shows it only once — if you lose it, revoke it and create a new one.

​

Connect with a token

https://mcp-prod.the-juno.com/mcp

Authorization: Bearer <your-token>

{
  "mcpServers": {
    "juno-journey": {
      "type": "http",
      "url": "https://mcp-prod.the-juno.com/mcp",
      "headers": {
        "Authorization": "Bearer ${JUNO_MCP_TOKEN}"
      }
    }
  }
}

​

Use a token in CI

- name: Run the Juno job
  env:
    JUNO_MCP_TOKEN: ${{ secrets.JUNO_MCP_TOKEN }}
  run: ./scripts/run-juno-job.sh

​

Keep tokens safe

• Treat a token like a password. Keep it in a secret store — never in code, in a file you commit, or in a URL.
• Create one token per job or system, named after it, so you can revoke one without breaking the others.
• Don’t share a token between people or add it to a shared assistant connector. Everyone using it would act as you, with your Admin permissions.
• Replace tokens before they expire: create a new token, update the secret, then revoke the old one.

​

Revoke a token

1

Find the token

Go to Admin → Security → Developer Settings. The MCP tokens list shows every MCP access token in your organization, with its name, who created it, when it was created, and when it expires.

2

Revoke it

Select Revoke on the token’s row, then confirm. The token stops working immediately, and anything still using it starts failing. Revoking can’t be undone.

​

If a token stops working

• It was revoked (the list shows Revoked), or it has expired — check its Expires date.
• The Admin who created it was deactivated or removed from your organization.
• It was sent to the Juno REST API instead of the MCP server.
• The header isn’t exactly Authorization: Bearer <token>, or the token was copied incompletely.