Connecting via MCP

usepresence ships a remote MCP server at https://usepresence.com/mcp. Point an MCP-aware assistant — Claude, Cursor, or anything that speaks the Model Context Protocol — at it, and the assistant can create your team, mint a publishable key, and read your inbox on your behalf. No API keys to copy, no config files to hand-edit.

You don't even need an account first. The server uses OAuth: the first time your assistant connects, you sign in — or register right there in the flow — and usepresence sets up a personal team and a Default source with a publishable key automatically. By the time the connection is live, you're fully provisioned.

Connect Claude Code

One line in your terminal:

claude mcp add --transport http usepresence https://usepresence.com/mcp

The next time you talk to Claude, it'll walk you through signing in, then have the usepresence tools ready.

Connect Claude Desktop or Cursor

Add usepresence to the mcpServers block in your client's config:

{
    "mcpServers": {
        "usepresence": {
            "url": "https://usepresence.com/mcp"
        }
    }
}

Restart the client, approve the sign-in when it opens your browser, and you're connected. Any other MCP client works the same way — it's a standard Streamable HTTP server with OAuth, so point it at the same URL.

What your assistant can do

The server exposes a small, focused set of tools — enough to set usepresence up end to end and keep an eye on the inbox, and nothing that could do damage on your behalf.

Tool	What it does
list-teams	Lists the teams you belong to, with your role in each.
create-team	Creates a new team (one team per app) — a Default source and key come with it.
list-sources	Lists a team's sources with their live publishable keys and usage.
create-source	Adds a new source and publishable key for a team.
get-setup-instructions	Returns a paste-ready integration prompt — contact-form or embed flavor — with your live key already in it.
list-conversations	Lists conversations in a team's inbox, filterable by status or source.
get-conversation	Reads a single conversation: the customer, their attributes, and the full message thread.

There's also an integrate-usepresence prompt your client can pull in, so a fresh assistant knows exactly how to wire your site up without any prompting from you.

What it can and can't do

The MCP server is for setup and a read-only view of your inbox. Your assistant can create teams and sources, fetch your keys, and read conversations — but it can't reply to a customer, revoke a key, or delete anything.

Those are deliberate. Replying is a human moment, so it stays in the web app where you can read the whole thread and approve what goes out. And anything destructive — revoking a key, removing a source — lives in Settings too, behind a real click, not a tool call. The assistant helps you get set up and stay aware; you stay present for the parts that matter.

Once you have a key, integrating your site is one small API call — and your assistant already knows the contract via get-setup-instructions.