Skip to content
Patricia
Use casesIntegrationsSecurityPricingStart free

Developers

Connect your software to Patricia

Patricia is an AI coworker who lives in Slack, with Microsoft Teams rolling out next. This page is the machine-facing side of her: the Model Context Protocol server your agent dials, the credentials it accepts, and the REST API behind the dashboard.

MCP serverAPI reference

MCP server

Patricia speaks the Model Context Protocol over the Streamable HTTP transport. Point any MCP client at this address:

https://api.patricia.app/v1/mcp

Authentication is a bearer token on the Authorization header. An unauthenticated request answers 401 with WWW-Authenticate: Bearer realm="patricia-mcp", which is the expected reply and a quick way to confirm the endpoint is up.

Client configuration

Most clients take a JSON block that looks like this:

{
  "mcpServers": {
    "patricia": {
      "type": "http",
      "url": "https://api.patricia.app/v1/mcp",
      "headers": { "Authorization": "Bearer pat_mcp_..." }
    }
  }
}

Credentials

Two kinds of token exist, and which one you hold decides what the server will answer. A person mints either at Settings, Developer in the Patricia dashboard. There is no self-serve signup, so an agent cannot mint one on a user's behalf.

  • pat_mcp_

    Personal token

    Names the person who minted it. Required for anything that reads or writes that person's own work: files, memory, skills, connected tools, and asking Patricia to do a job.

  • pat_live_

    Workspace API key

    Names the workspace and no person. It can read workspace-level context such as the company profile and the team roster. Anything that depends on who is asking is refused.

What the server exposes

Call tools/list for the authoritative set. In outline:

  • Know the workspace. Confirm which workspace and which person the credential names, read the company profile, and list the team.
  • Read and write the workspace memory. Search what Patricia already knows about the company, store a new fact, or forget one.
  • Work with files. List, search, read, and create files in the workspace, and open or close a dated public link for one.
  • See what Patricia can already do. List the skills and the connected tools this workspace holds, then search or inspect a capability before calling it.
  • Hand Patricia a job. Ask Patricia to do the work as the person the token names. The run is asynchronous, so poll it for status. Patricia's ordinary approval rules still apply, so anything that publishes, sends, or spends waits for a human yes.

Registry descriptor

There is no standard well-known location for advertising an MCP server yet, so this site publishes a descriptor in the MCP registry's own server.json format at /mcp/server.json. Anything else claiming to be a Patricia MCP manifest is not ours.

When to call Patricia

Patricia is worth a call when the request needs this company's own context, tools, or approval chain:

  • Produce a finished marketing deliverable that needs the company's own voice, brand, and history: a campaign report, an ad set, a social calendar, a customer update, a proposal.
  • Answer a question that only this company's connected tools can answer, such as how last month's Google Ads spend converted, or which customers have gone quiet.
  • Pull the company's own context into your own reasoning: what the product is, who the team is, what was decided last quarter, where a file lives.
  • Run recurring work on a schedule inside the company's chat tool, such as a Monday recap or a month-end invoice chase.
  • Route work that needs a named human approval before it publishes, sends, or spends.

When not to

  • Creating an account. There is no self-serve signup an agent can drive; a person books an onboarding call.
  • General world knowledge or reasoning with no tie to this company's data. Your own model is faster and cheaper.
  • Anything that must publish, send, or spend with no human in the loop. Patricia will hold it for approval instead.
  • Reading a workspace the credential does not name. Every answer is scoped to the one workspace behind the token.

REST API

The same API the Patricia dashboard runs on, versioned under /v1. The dashboard itself uses a signed-in session; a programmatic caller sends a pat_live_ workspace API key as a bearer token instead.

Agent discovery files

Some pages answer in markdown when you send Accept: text/markdown, and each of those also answers at its .md address. Not every page has one, so read /404.md for the list rather than guessing. These files are the indexes:

Getting help

Write to hello@patricia.app with what you are building, or see every contact route.