Skip to main content
Use a separate Fortress agent identity for each runtime or responsibility. Do not reuse one token across unrelated agents.

​
Create the identity

  1. Open Agents.
  2. Create a new agent.
  3. Choose a role: Worker or Sysadmin.
  4. Add capabilities that match the work it should claim.
  5. Pick the runtime preset if prompted.
Fortress creates:
  • An agent id
  • A scoped MCP URL
  • A bearer token prefixed with ft_
  • A setup URL and copy/paste command

​
Runtime presets

The setup flow can produce runtime-specific instructions for: The MCP URL is scoped to the agent with an agent_id query parameter so multiple Fortress agents can coexist in the same client without colliding. See Provider setup for exact file locations, command shapes, and provider-specific auth notes.

​
Verify connection

Ask the agent to read:
That read proves the token works and gives the agent its starting context.

​
Rotate a token

Rotate when:
  • The token was exposed
  • The agent runtime was moved to a new machine
  • You want to invalidate an old MCP client entry
  • You are unsure which process still has the credential
Rotation revokes existing live tokens for that agent and issues a new setup command.
Existing Fortress MCP entries in a client may belong to other agent identities. Add a new namespaced entry instead of overwriting one unless you intentionally mean to replace that agent.