Skip to main content

Connect your AI client

Permaura speaks MCP (Model Context Protocol), so any MCP client can use it. Step 5 — Connect an agent covers the flow; this page is the per-client detail.

Everything starts in the console. Settings → Gateway shows the connection details for the gateway you just set up, and Agents → Connect agent gives you the same thing from the other direction. Either gives you two ways in, and which one you need depends on where the client runs.

Your client runs…UseWhat you copy
In the cloud (ChatGPT) or on another deviceRemoteYour gateway's public MCP URL
On the same computer as your gatewayOn this machineA ready-made MCP config block with a one-time code
Remote needs a public URL

The Remote tab only has a URL to give you once remote access is on for that gateway. Until then, use On this machine, or turn remote access on first.

Claude Code​

Run the one-line command the dialog shows:

claude mcp add --transport http permaura https://g-xxxx.permaura.com/mcp

The first call opens a Permaura sign-in in your browser. Approve there and you're connected.

Check it landed with claude mcp list. Your capabilities appear as tools named after their connection, like db1.uptime.

Claude Desktop, Cursor, and other config-file clients​

Clients that keep MCP servers in a JSON config file take the block straight from the On this machine tab:

{
  "mcpServers": {
    "permaura": {
      "command": "npx",
      "args": [
        "-y", "mcp-remote",
        "http://127.0.0.1:7376/mcp",
        "--header", "Authorization:Bearer ENRL-A1B2-C3D4",
        "--transport", "http-only"
      ]
    }
  }
}

Copy the dialog's version rather than this one — it carries your gateway's real address and a live code. Then restart the client; most only read their MCP config at startup.

In Claude Desktop the file is claude_desktop_config.json. Cursor and other clients have their own MCP settings screen or config file — check your client's documentation for where it lives. Any of them can take a remote gateway too: use the public MCP URL, with no Authorization header, and sign in when prompted.

ChatGPT and other hosted clients​

A hosted client can't reach 127.0.0.1, so it needs the Remote path.

  1. Turn on remote access for your gateway.
  2. Copy the MCP server URL from the Remote tab (https://g-xxxx.permaura.com/mcp).
  3. Paste it into the client's Connectors / MCP servers settings.
  4. It sends you to a Permaura sign-in. Approve, and the agent is connected.

After it connects​

  • A remote agent that signed in arrives already approved — your sign-in was the approval.
  • A local agent arrives Pending on the Agents page until you click Approve.
  • Either way it can still do nothing until a grant allows it. Permaura is deny-by-default, so a freshly connected agent sees its tools and gets refused on every one until you say otherwise.
Make every new agent wait

Turn on Require manual approval for new agents at the top of the Agents page and even remote agents that sign in successfully land as Pending for your explicit OK.

If a client can't see any tools​

Work through Troubleshooting — the usual causes are a client that wasn't restarted, an expired one-time code, or remote access being on in the console but not yet set on the gateway itself.