Run usepresence from the agent you already use.
Connect Claude or Cursor over MCP and let it set everything up — a team, a source, a live contact form, a look at your inbox. You sign in with OAuth in the browser: no API keys to copy, no SDK to install.
One line to connect.
Add usepresence to Claude Code from your terminal:
claude mcp add --transport http usepresence https://usepresence.com/mcp
On Claude Desktop or Cursor, add a one-line entry to your
mcpServers
config pointing at the same URL —
the guide has the exact JSON.
What a conversation looks like.
From "I need support on my site" to a live form and a first test message — in one chat.
Add a contact form to my site and hook it up to a support inbox.
On it. I'll connect to usepresence — a browser window will pop up so you can sign in.
I built a contact form from that contract and dropped it into your site. It posts to the usepresence API with your publishable key.
Nice. I just sent a test message — did it come through?
Yes — one open conversation just landed: "Testing the new form 👋". Open your inbox to read the thread and reply when you're ready.
Ask in plain language.
A few things you can just say to your assistant.
"Set up support for my new app."
Your agent spins up a team, then hands you a ready-made form to drop in.
"Any new messages since yesterday?"
It scans the inbox and reads back the threads that need you — you reply in the app.
"Create a separate source for the marketing site."
A fresh publishable key, so you can see where each conversation came from.
The whole toolbox.
Seven tools and one prompt — enough to set usepresence up end to end and keep an eye on the inbox, and nothing that could do damage.
-
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.
-
integrate-usepresenceprompt - A reusable prompt your client can pull in, so a fresh assistant knows exactly how to wire your site up.
Where we drew the line.
The MCP server helps you get set up and stay aware — but it's a read-only view of your inbox. Your assistant can create teams and sources, fetch your keys, and read conversations. It can't reply to a customer, revoke a key, or delete anything.
That's deliberate, and it matches how we think about AI everywhere in usepresence: it drafts, you approve. Replying is a human moment, so it stays in the app where you can read the whole thread. Anything destructive lives in Settings, behind a real click — never a tool call.
-
Set up and read
Create teams and sources, fetch keys, read the inbox.
-
Replying stays human
Answers go out from the app, reviewed by a person.
-
Nothing destructive
Revoking keys or removing sources lives in Settings.
Questions, answered.
What is MCP?
The Model Context Protocol is an open standard that lets AI assistants like Claude and Cursor connect to external tools. usepresence runs a remote MCP server, so your agent can create teams and sources, fetch keys, and read your inbox on your behalf.
Do I need a usepresence account before I connect?
No. The server uses OAuth — the first time your assistant connects, you sign in or register right there in the browser flow, and usepresence provisions a personal team and a Default source with a publishable key automatically.
What can the agent access?
A small, focused set of tools: it can list and create teams and sources, fetch your publishable keys, get a paste-ready setup prompt, and read conversations in your inbox. That is the whole surface.
Is it safe — can the agent delete things or reply to customers?
No. The MCP server is for setup and a read-only view of your inbox. It can create teams and sources and read conversations, but it cannot reply to a customer, revoke a key, or delete anything. Those stay behind a real click in the web app, on purpose.
Which clients work?
Any MCP client that speaks Streamable HTTP with OAuth — Claude Code, Claude Desktop, and Cursor are all supported. Point the client at https://usepresence.com/mcp and approve the sign-in.
Does it cost anything?
usepresence is free to start — you can connect, set up a contact form, and read your inbox without a card. Connecting over MCP does not cost extra.
Let your agent do the setup. You stay present.
Connect Claude or Cursor, sign in in the browser, and your contact form is live in one conversation.