Connect Claude, Codex and Cursor

What it is

Proa works inside the AI tools you already use. Once connected, Claude, Claude Code, Codex or Cursor can list your websites, read the results of your experiments, draft experiments and customizations with a preview link, and check whether a publish would go through, all on the websites you can see in Proa.

The connection is yours: the tool signs in with your Proa account and works within the access and websites you allow. Your current permissions in Proa still apply. You choose how much it may do when you connect, and you can disconnect it at any time.

Before you start

You need a Proa account and at least one website in it. Open the user menu in the dashboard and choose MCP & API keys. The dialog opens on the Connect tab with one guide per tool, each ending with Proa listed in the tool. The URL every tool asks for is:

https://api.tryproa.com/api/mcp

Use Copy URL in the guide rather than typing it.

Connect Claude

For Claude on the web and Claude Desktop:

1. On a Free, Pro or Max plan, open Customize, then Connectors, and choose Add custom connector. Free accounts can add one custom connector.
2. Paste the URL above as the connector URL and save.
3. Click Connect. Claude opens Proa: sign in, choose the access and the website, and allow. Claude returns on its own.

On Team or Enterprise, an Owner first adds Proa in Organization settings → Connectors → Add → Custom, using the URL above. If asked for the connector type, choose Web. Enterprise members with permission to manage organization libraries can also add it. Each member then opens Customize → Connectors, finds Proa and clicks Connect.

If Claude asks for authentication settings, choose Sign in now and Register automatically. Proa registers the connection for you; leave any optional client ID and secret fields empty.

Connect Claude Code

Run this in your terminal:

claude mcp add --scope user --transport http proa https://api.tryproa.com/api/mcp

Then, in Claude Code, run /mcp, choose proa and sign in. The browser opens Proa for you to allow the access.

Connect Codex

Run these in your terminal. The second one opens the browser for you to sign in to Proa and allow the access:

codex mcp add proa --url https://api.tryproa.com/api/mcp
codex mcp login proa

In the Codex app or the IDE extension instead: open Settings, then MCP servers, choose Add server and Streamable HTTP, paste the URL, then Authenticate. In Codex, /mcp lists proa once it is connected.

Connect Cursor

One click: Add to Cursor opens Cursor with Proa ready to authenticate.

Or add Proa to the Cursor configuration by hand, with only the URL. Save it as .cursor/mcp.json in your project, or as ~/.cursor/mcp.json for every project, keeping any other servers the file already has:

{
  "mcpServers": {
    "proa": {
      "url": "https://api.tryproa.com/api/mcp"
    }
  }
}

In Cursor, open Customize in the sidebar, find proa and click Authenticate. The browser opens Proa: sign in, choose the access and allow. Back in Customize, proa lists the Proa tools. If it does not, open Output and choose MCP Logs.

Allowing access

When a tool asks for access, Proa opens a page that names the app asking. On it you choose:

• Access: Read by default, or Read and write. Read and write is offered only where your role in Proa may change things.
• Website: one of your websites, or All websites, which means every website you can see, now and later.

Then click Allow. The connection keeps only what you allowed, for 90 days at most, after which the tool asks again. Reconnecting the same app with the same requested access can reuse an active connection without asking again. Expired or disconnected apps need your permission again. If you do not recognise the app, click Cancel and nothing is granted.

The page shows where the tool returns to after you allow. Claude Code and Codex normally return to an address on your own computer. Cursor can return through its own website or an address on your computer. Allow access only when you just started connecting Proa in that tool.

What the tools can do

With Read access, the tool reads websites, brand guidelines, theme profiles, playbooks, experiments and their results, customizations and their HTML and CSS, and shareable preview links. It changes nothing.

With Read and write access, it also creates and edits experiments, customizations and preview links, and launches tests or publishes where your permissions allow. Saving theme profiles and running design reviews are reserved for the Vasta team that operates Proa; a design review spends the website's AI budget.

Launching, ending and publishing always go through a plan the tool shows you first. It acts only after you say yes. Results come with the same verdict the dashboard shows: the tool repeats it and does not compute statistics of its own.

Your role on each website sets the ceiling. Website owners and members of its agency can create, publish and apply winners. Website staff can create, launch, pause and conclude tests. Viewers can only read.

Managing connections

The Connected apps tab of MCP & API keys lists every app you connected by signing in, with its access, website and when it was last used. Disconnect stops it right away, and the tool has to ask again to come back.

Your current permissions are checked on every call. Losing access to a website stops the tool from using that website. If you no longer have any edit access covered by a Read and write connection, the connection stops altogether. Reconnect with Read access to keep using it.

Keys for servers and scripts

An API key remains the way to connect a server, a scheduled job or a script that cannot sign in through a browser. The Keys tab creates one with a name, an access level, an optional website and an expiry of up to a year. Proa shows the key once, with the configuration to paste for Claude Code, Cursor or Codex.

A key acts as you: it sees and changes what you can. Prefer a Read key for an agent that only analyses, keep the key in your home folder or in an environment variable rather than in a file you commit, and Revoke it when you change computers, stop using a tool or suspect a leak.

Prompts to try

Once a tool is connected, paste one of these, replacing the name in brackets:

• "List my Proa websites."
• "Show the results of my running experiments on [website] and say which ones are ready for a decision."
• "On [website], create a draft experiment that tests [hypothesis], with a customization for the variant and a preview link for it."
• "On [website], check whether a publish would succeed now and explain anything it would refuse."

Privacy and data

A connected AI tool reaches only what Proa exposes through the actions listed above, within your current permissions and the access and websites you allowed when connecting. Proa does not request the tool's conversation history. Proa records tool calls for auditing. Connected apps shows each connection and when it was last used. The AI tool handles the data it receives under its own terms. How Proa handles data is in the privacy policy.

Support

Use the Support entry in the dashboard sidebar, which arrives with your website context attached, or the contact page.