Skip to main content
Use the generic preset when your client supports remote HTTP MCP servers but Fortress does not have a dedicated preset for it yet.

​
Connection details

Fortress gives each agent:
FieldValue
Server namefortress-<agent>
URLhttps://api.fortressproductivity.com/mcp?agent_id=<agent-id>
HeaderAuthorization: Bearer ft_<token>
TransportStreamable HTTP

​
Common config shape

Many clients accept this shape: 
{
  "mcpServers": {
    "fortress-agent": {
      "url": "https://api.fortressproductivity.com/mcp?agent_id=<agent-id>",
      "headers": {
        "Authorization": "Bearer ft_<token>"
      }
    }
  }
}
Some clients require type: "http" or use a top-level servers key instead of mcpServers. Use the dedicated provider pages when they match your client.

​
Verify

Ask the client to list MCP tools or read fortress://workspace/overview. If the client reports authentication failure, confirm the header is exactly: 
Authorization: Bearer ft_<token>