Setup

Connect your assistant

Four assistants, set up and tested by us. Each one needs the same address and one sign-in with your Palagus account: no client ID, no secret, nothing to install on our side.

Server URL

Every assistant uses the same address.

https://staging.palagus.ai/api/mcp
ChatGPT logo

ChatGPT

Connecting Palagus in ChatGPT

  1. You need ChatGPT Plus (checked by us), or Pro or a business plan per OpenAI.

  2. Open Plugins, choose Add, then Create MCP App. If ChatGPT asks for Developer mode first, switch it on under Settings → Security and login. On our Plus account the form opened without it.

  3. Enter a name and the server URL and keep Authentication on OAuth. Tick I understand and want to continue, then choose Create.

  4. Choose Continue to Palagus, sign in and approve the three permissions. In a conversation, select Palagus with + in the message box.

What ChatGPT will warn you about

  • Custom MCP servers introduce risk … An untrusted server may access or steal information shared through app use … The app you add receives what the model sends it and can act with the permissions you approve. Check that the address is exactly the server URL above: a look-alike address is how this attack works. Palagus then acts only as you, with those three permissions, and you can end the connection at any time.
  • Connect Palagus … Connectors may introduce risk … The same caution once more, before ChatGPT sends you to the Palagus sign-in. Continue only if the address is ours.
  • Developer mode — ELEVATED RISK Only if your account asks for Developer mode. It lets you add apps that OpenAI has not reviewed, and Palagus is such an app. Add only apps whose maker you trust.
Claude.ai logo

Claude.ai

Connecting Palagus in Claude.ai

  1. In Claude.ai open Customize → Connectors, choose Add, then Add custom connector.

  2. Enter a name and the server URL, then choose Continue.

  3. Claude.ai detects the sign-in and registers itself: Sign in now and Register automatically are both marked Detected. Keep them and choose Add, then Connect on the connector's page.

  4. Sign in to Palagus and approve the permissions. The tools then appear in the conversation, grouped into reading and writing ones.

Claude Code logo

Claude Code

For developers: this client runs in a terminal.

Connecting Palagus in Claude Code

  1. Add the server and sign in.

    claude mcp add --transport http palagus https://staging.palagus.ai/api/mcp
claude mcp login palagus

  2. Approve the three permissions in the browser window that opens, then return to the terminal.

  3. Ask it something: “List my projects with palagus.” Run claude mcp list to see the connection, claude mcp remove palagus to drop it.

  4. To start a report, type /palagus and press Tab to take the suggestion (it becomes /mcp__palagus__weekly_pulse), then add the project. Typed out as /palagus:weekly_pulse it answers Unknown command.

Codex CLI logo

Codex CLI

For developers: this client runs in a terminal.

Connecting Palagus in Codex CLI

  1. Codex 0.154 or newer is required; older versions fail before they reach any tool.

    codex mcp add palagus --url https://staging.palagus.ai/api/mcp
codex mcp login palagus

  2. Approve the permissions in the browser. Codex asks for none in particular, so it receives all three.

  3. Ask in plain words. Codex offers no reports; the tools are called all the same.

Other assistants, not yet checked by us

  • Perplexity: Pro, Max and Enterprise plans can add a custom remote connector. We have not set Palagus up there yet. Perplexity's guide
  • Gemini: Google offers custom connectors to personal accounts only in the US and in English; in Gemini Enterprise a team admin can add an MCP server. Google's guide
  • Microsoft Copilot: The personal Copilot cannot add servers like Palagus; Microsoft 365 Copilot can, set up by your company's admin. Microsoft's guide

Check that it works

Ask your assistant:

“List my Palagus projects.”

It should answer with the projects your account can see. From there, try a question from the use cases or one of the six reports.

See and end connections

Every assistant you approved is listed in Palagus under Account → Connected AI clients, with when it was connected and what it may do. Disconnecting stops it from renewing its access; what it already holds ends by itself within an hour at most. Removing Palagus inside the assistant only stops it from that side. Nothing is revoked on ours until you disconnect it in Palagus.

Troubleshooting

“This sign-in has expired”

The sign-in waits ten minutes for you. Start the connection again from your assistant and approve without a long pause.

“This browser did not start the sign-in”

Finish the sign-in in the browser window your assistant opened. A link copied into another browser cannot complete it.

Signed in with the wrong account

On the approval page, choose “Not you? Sign in with another account”. The assistant then finishes with the account you pick.

A tool or a report is missing

After a Palagus update, a client may not see newly added tools until it reconnects. In ChatGPT, delete the app and add it again; in the other clients, disconnect and connect again first.

“Too many requests”

More than 120 requests in a minute, usually an assistant stuck in a loop. Wait a minute and ask again.

No projects show up

The assistant sees exactly what your account sees. Check that your account has at least one project in Palagus, or ask your workspace admin for access.

Sources or sentiment come back empty

Cited sources need the citations feature in your plan, sentiment the sentiment feature.

Recordings show each assistant’s menus as they were when we recorded them. Assistants rename their menus now and then.