Skip to main content
Each Fortress agent connects to the MCP server with its own scoped URL. Most local clients use a bearer token; OAuth-capable remote clients can use Fortress’s OAuth flow. 
https://api.fortressproductivity.com/mcp?agent_id=<agent-id>
Authorization: Bearer ft_...
Local development uses the API origin running on port 3000: 
http://localhost:3000/mcp?agent_id=<agent-id>
Authorization: Bearer ft_...

​
Server identity

FieldValue
Namefortress
TitleFortress
DescriptionMission control for a human and their bring-your-own agents.
TransportHTTP MCP endpoint
AuthBearer token or OAuth access token scoped to one agent

​
Resources before tools

Agents should use resources for reads when they know the URI. Tools are for writes, search, or reads that need parameters such as a limit.

Read full context

Use fortress://action/<id>, fortress://project/<id>, and fortress://document/<id>.

Mutate state

Use tools such as heartbeat, complete_action, drop_action, ask_question, and update_document.

​
Required startup reads

At the start of a session, an agent should read:
  1. fortress://workspace/overview
  2. fortress://orders
  3. fortress://order/<id> for any active order it will execute
  4. fortress://action/<id> before doing a task

​
Error handling

MCP tool errors return structured content under structuredContent.error. Agents should branch on stable error codes, not natural-language messages. Examples include:
CodeMeaning
already_terminalAnother actor already completed or dropped the action. Refetch and stop retrying.
not_agent_actionableThe action is no longer ready work for this agent.
wrong_actorThe token does not match the actor allowed for the operation.
template_not_completableTemplate actions cannot be completed as live work.

​
Subscriptions

The MCP server supports resource subscriptions. Subscribable resources include actions, questions, projects, orders, and the authenticated agent’s own queue. Use subscriptions when an agent runtime stays alive and should react to queue changes or question answers.

​
OAuth clients

Fortress also exposes OAuth 2.1 flows for MCP clients that discover and register dynamically. The consent page can use the agent_id hint in the MCP resource URL to preselect the intended agent.