Connect your agent
Connect Claude, ChatGPT, Cursor or Claude Code to Omnipresence over MCP, how the account-scoped connection works, and how to rotate a credential.
Updated October 20, 2026
Omnipresence is built to be read by an agent as well as by a person. One connection, scoped to your account, covers every project you have.
The endpoint
https://api.getomnipresence.com/mcpThe same URL for everyone. There is nothing project-specific in it, because the connection is account-scoped and the project is chosen inside the session.
Connect it
1. Add the server in your client
Claude Code, one line:
claude mcp add --transport http omnipresence https://api.getomnipresence.com/mcpClaude.ai, ChatGPT and Cursor each have their own add-a-connector screen. The project's MCP tab walks through the exact steps per client and holds the values to paste.
2. Sign in
Your client opens an authorisation window. Sign in with the account that owns the projects. The token that results belongs to your account and is gated on the subscription being healthy: no healthy subscription, no token.
3. Pick a project
Ask the agent to list your projects, then to use the one you want. It will say which project it is working in and keep saying so.
If the account has several projects and none is selected, project-scoped calls are refused rather than guessed. That is deliberate: a wrong guess writes memory and optimization logs into another client's site. The choice persists for the connection, so you do this once.
4. Check it reads
Ask for the presence overview:
How did we do last week? Visibility Score with the band, and the
per-platform split.A rate with a confidence band coming back means the connection is live and everything else in this section works. If you would rather start by having it do the setup for you, say this instead:
Run the Omnipresence MCP onboardingWhat to ask your agent has nine jobs written out, with the tools each one calls.
Connected apps
The MCP tab lists every connected client and when it was last active. Expect one entry per machine rather than per person: a laptop and a desktop running the same client are two connections.
Revoke anything you do not recognise. Revoking takes effect immediately and the client will ask to sign in again.
The project credential
A project also holds a credential you can copy, with a Rotate control beside it. Rotate it when it may have been exposed, or when someone with access to it leaves. Rotating invalidates the old value at once, so anything using it has to be updated.
Headless clients
An agent with no browser cannot complete the sign-in window. For those, create an API key under Account and send it as a bearer token. It carries the same tools and the same account boundary as an OAuth sign-in. See API keys.
What else the connection serves
Besides your data, it serves the methodology: the processes and skills for a given job, fetched on demand. That is the difference between an agent that can read a dashboard and one that knows what to do about what it reads. See the methodology.
Rate limits apply per project as well as per account, so a runaway loop on one site cannot consume the allowance your other sites need. A limited call says so and asks you to wait a minute or switch project.
Questions about connect your agent
- Do I need a separate connection per project?
- No. One connection covers every project on the account, and the agent switches between them.
- My client has no browser. How does it sign in?
- With an API key as a bearer token instead of the OAuth flow. Same tools, same account boundary.
- The agent says it does not know which project to use. What now?
- Tell it which one. It refuses to guess when the account has several and none is selected, because guessing writes work into the wrong site.