Create an API token for MCP or the REST API

Settings, Integrations, API tokens. Read-only, shown once, Network plan. Tick the REST box to use the REST API as well as MCP.

Using the dashboardUpdated 1 min read

API tokens are part of Network.

  1. Open Settings, then Integrations (the page is titled AI & MCP), and find API tokens.
  2. Give the token a label, choose an expiry (30 days, 90 days, 1 year or never) and click Create token. Tick Also allow the read-only REST API if you want to call REST routes; leave it off for MCP only.
  3. Copy the token (ssk_ followed by characters). It is shown once; ServerStats stores only a hash.

A token belongs to you and one organisation and acts as you, with your current role. It is read-only. It stops working immediately when you revoke it, when it expires, when you leave the organisation or when the organisation leaves Network. You can have up to 10 active tokens per person in an organisation, and owners and admins can see and revoke every member's tokens.

What to do with it: authentication, MCP for Claude and Cursor, REST reference.

Still stuck? Email [email protected] with the server name and what you see. For a rejected claim code or no data, include the output of the agent’s status command.