Skip to main content
Connect Pagent to Claude, Claude Code, Codex, Cursor, VS Code, Windsurf, Zed, or another MCP-compatible client. You can review website test performance, turn hypotheses into tests, and manage targeting and goals without leaving your existing workflow.

Pagent MCP server

https://app.pagent.ai/api/mcpTransport: Streamable HTTP
Authentication: OAuth 2.0 or personal token
Pagent connections start with read access. During OAuth, you choose which organisations the client can access and whether to grant any write permissions.

Before you connect

You need:
  • A Pagent account with owner or administrator access to the organisation you want to connect
  • MCP enabled for that organisation
  • An MCP-compatible AI client
  • An onboarded website with the Pagent SDK installed if you expect visitor data or test results

Connect your AI client

OAuth is the recommended setup. Pagent asks you to choose organisations and permissions before the client can access anything.
1

Open connector settings

In Claude, open Settings, then Connectors.
2

Add Pagent

Choose Add custom connector, name it Pagent, and enter:
3

Approve access

Sign in to Pagent, choose the organisations and permissions, then approve the connection.

Other MCP clients

Add a Streamable HTTP server using https://app.pagent.ai/api/mcp and choose OAuth authentication. If your client cannot use OAuth, create a personal token in AI client access. Store personal tokens in a secret manager and never commit them to source control.

What you can do

The tools your client sees depend on the permissions you approved. Pagent keeps reads and writes separate.

Example workflows

Replace the bracketed details with your own website, test, or hypothesis.

Review live tests without changing anything

Compare what was tested

Turn a hypothesis into a test

Check before starting a live test

Access and safety

Pagent connections start with read access. During OAuth, you choose the organisations the client can access and whether to add write permissions. Pagent checks your current role, the organisation allowlist, and the organisation’s MCP policy on every request. A connection does not remember a website between requests. Ask the client to list available websites, then name the intended website or domain before website-specific work.
A write runs when your AI client calls the tool. Pagent does not add a second confirmation screen. Keep write confirmation enabled in your client and ask it to show planned changes before acting. Starting, pausing, stopping, or rolling back a test can affect a live website.
Marking a test as shipped records that its winning changes were implemented. It does not change the website. Write requests are audited and use idempotency keys so the same retry cannot repeat a change.
Content returned through connected tools can contain misleading instructions. Review proposed writes and data sharing before you approve them in your client.

Manage access

Open AI client access to:
  • Review active connections
  • Change their organisation access
  • See when they were last used
  • Revoke connections or personal tokens
Reconnect a client if you need to change its permission groups. Organisation owners can also disable MCP for the entire organisation.

Troubleshooting

Confirm that your client uses the exact Pagent endpoint. Close the browser tab, return to the client, and start the connection again while signed in to the intended Pagent account.
The connection can only see organisations selected during approval. Reconnect or update its organisation access in Pagent. The organisation must also have MCP enabled.
Pagent only exposes tools allowed by the connection’s permissions. Reconnect with the required write permission if you intentionally need broader access.
Ask it to list the available websites, then refer to the website by name or domain. Connections do not keep a selected website between requests.
Pagent checks your current organisation role and policy on every request. Your role may have changed, MCP may have been disabled, or the test may not allow that action in its current state.
Confirm that the Pagent SDK is installed and receiving visitor traffic. A test can also remain inconclusive until it has enough evidence.
Disconnect Pagent in your client, reconnect it, and complete the browser approval flow again.
The connection reached a rate limit. Wait for the Retry-After period returned by Pagent, then retry.
Per-website MCP credentials are no longer supported. Reconnect through OAuth or create a new personal token in AI client access.

FAQ

Does connecting change my live website?

No. Read tools only inspect Pagent data. A live website changes only when a permitted write tool performs an action that affects a running test.

Can I keep the connection read-only?

Yes. Leave the optional write permissions unchecked during OAuth.

Can one connection access multiple organisations?

Yes. Select each organisation during approval. Organisations you join later are not added automatically.

Is a connection limited to one website?

No. It acts through your Pagent profile across the organisations you select. Name the intended website or domain for website-specific work.

Can I use Pagent from CI or a headless client?

Yes. Create a personal token with the minimum required organisations and permissions, then store it in a secret manager.
Need help? Email support@pagent.ai with the client name, authentication method, approximate error time, and exact message. Never send your personal token. Updated August 11, 2026.