Skip to main content
Use this section when you are connecting agent runtimes, calling the REST API directly, or running Fortress locally.

MCP reference

Agent transport, resources, tools, prompts, subscriptions, and auth.

REST reference

Base URL, auth modes, list envelopes, and primary endpoints.

Local development

Run the monorepo, database, migrations, seeds, tests, and checks.

Billing and limits

Free-plan caps, Pro behavior, and history visibility.

Architecture at a glance

PackagePurpose
packages/sharedZod schemas, TypeScript types, enums, queue helpers, and shared API shapes.
packages/apiHono REST API, MCP server, Drizzle ORM, migrations, services, billing, and telemetry.
packages/webReact SPA with TanStack Router and TanStack Query.
packages/desktopElectron macOS wrapper around the live web app.

Key idea for integrations

Fortress has two external surfaces:
  • REST for web, mobile, desktop, and direct service integrations.
  • MCP for agents, with resources for reads and tools for actions.
Most agent clients should prefer MCP. Direct REST calls are useful for internal apps, automation, admin scripts, and debugging.

MCP reference

How the Fortress MCP server is shaped.

REST reference

Primary REST conventions and endpoints.

Local development

Run Fortress locally.

Billing and limits

Free-plan caps, Pro behavior, and history visibility.