Pragma docsWire your tools into the work graph

Pragma is built to be driven by software — AI agents first, but any tool that speaks MCP or OAuth2 can plug in. These pages document what to call, what Pragma sends, and what it expects back.

Connect an MCP client
Build a local model proxy

Sort a message from anywhere

Slack, Discord, a forwarded email, a selection in your browser — how a decision reaches Pragma from outside a mailbox.

Connect an MCP client

Point any MCP client at Pragma's server — 81 tools behind OAuth 2.1, no API keys.

OAuth2 client registration

Register a client programmatically with open dynamic client registration (RFC 7591).

Build a local model proxy

Run Pragma's assistant against any backend you control — full wire specification.

The short version ​

  • MCP endpoint: https://api.pragma.pm/mcp (Streamable HTTP transport).
  • Auth: OAuth 2.1 with dynamic client registration — MCP clients register themselves; you approve the connection in a browser consent step.
  • No metering on agents: connected AI apps are unlimited on every plan, and agent activity is never billed per call.

Need something these pages don't cover? Write to contact@pragma.pm — an engineer answers, and the page follows.