> ## Documentation Index
> Fetch the complete documentation index at: https://docs.palagus.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# 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.

```text theme={"system"}
https://app.palagus.ai/api/mcp
```

## ChatGPT

<video autoPlay loop muted playsInline controls aria-label={"Connecting Palagus in ChatGPT"} poster={"https://media.palagus.ai/mcp/recordings/chatgpt-connect.poster.d51c875d3d34.webp"}>
  <source src={"https://media.palagus.ai/mcp/recordings/chatgpt-connect.c4e32209ed6b.webm"} type={"video/webm"} />

  <source src={"https://media.palagus.ai/mcp/recordings/chatgpt-connect.c4e32209ed6b.mp4"} type={"video/mp4"} />
</video>

<Steps>
  <Step>
    You need ChatGPT Plus (checked by us), or Pro or a business plan per OpenAI.
  </Step>

  <Step>
    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.
  </Step>

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

  <Step>
    Choose Continue to Palagus, sign in and approve the three permissions. In a conversation, select Palagus with + in the message box.
  </Step>
</Steps>

<Warning>
  **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 — Palagus is such an app. Add only apps whose maker you trust.
</Warning>

<Warning>
  **To reconnect, delete and add again.** ChatGPT keeps the permissions it was given the first time and cannot ask for more later. Uninstalling is not enough — remove the app, then add it once more.
</Warning>

## Claude.ai

<video autoPlay loop muted playsInline controls aria-label={"Connecting Palagus in Claude.ai"} poster={"https://media.palagus.ai/mcp/recordings/claude-connect.poster.608c8fb708c8.webp"}>
  <source src={"https://media.palagus.ai/mcp/recordings/claude-connect.b99659cf47af.webm"} type={"video/webm"} />

  <source src={"https://media.palagus.ai/mcp/recordings/claude-connect.b99659cf47af.mp4"} type={"video/mp4"} />
</video>

<Steps>
  <Step>
    In Claude.ai open Customize → Connectors, choose Add, then Add custom connector.
  </Step>

  <Step>
    Enter a name and the server URL, then choose Continue.
  </Step>

  <Step>
    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.
  </Step>

  <Step>
    Sign in to Palagus and approve the permissions. The tools then appear in the conversation, grouped into reading and writing ones.
  </Step>
</Steps>

<Tip>
  **Allow the reading tools once.** If Claude asks before every tool call, set the reading tools to Always allow in the connector's tool permissions — a weekly pulse otherwise asks dozens of times (42 in our test). Leave the writing tools on approval: they use run budget.
</Tip>

## Claude Code

*For developers — this client runs in a terminal.*

<video autoPlay loop muted playsInline controls aria-label={"Connecting Palagus in Claude Code"} poster={"https://media.palagus.ai/mcp/recordings/claude-code-connect.poster.c10dea5aa665.webp"}>
  <source src={"https://media.palagus.ai/mcp/recordings/claude-code-connect.d45c3cbc4d45.webm"} type={"video/webm"} />

  <source src={"https://media.palagus.ai/mcp/recordings/claude-code-connect.d45c3cbc4d45.mp4"} type={"video/mp4"} />
</video>

<Steps>
  <Step>
    Add the server and sign in.

    ```text theme={"system"}
    claude mcp add --transport http palagus https://app.palagus.ai/api/mcp
    claude mcp login palagus
    ```
  </Step>

  <Step>
    Approve the three permissions in the browser window that opens, then return to the terminal.
  </Step>

  <Step>
    Ask it something: “List my projects with palagus.” Run `claude mcp list` to see the connection, `claude mcp remove palagus` to drop it.
  </Step>

  <Step>
    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.
  </Step>
</Steps>

<Tip>
  **Connected in Claude.ai too?** Claude Code also lists your Claude.ai connectors, so Palagus may appear twice — once as claude.ai Palagus. The one you added here is the one `claude mcp login` signs in.
</Tip>

<Warning>
  **Be quick in the browser.** Claude Code stops waiting for the sign-in after a few minutes and then reports a timeout. Start it again and approve without a long pause.
</Warning>

## Codex CLI

*For developers — this client runs in a terminal.*

<video autoPlay loop muted playsInline controls aria-label={"Connecting Palagus in Codex CLI"} poster={"https://media.palagus.ai/mcp/recordings/codex-connect.poster.c1e32afdef70.webp"}>
  <source src={"https://media.palagus.ai/mcp/recordings/codex-connect.adf23db4e000.webm"} type={"video/webm"} />

  <source src={"https://media.palagus.ai/mcp/recordings/codex-connect.adf23db4e000.mp4"} type={"video/mp4"} />
</video>

<Steps>
  <Step>
    Codex 0.154 or newer is required; older versions fail before they reach any tool.

    ```text theme={"system"}
    codex mcp add palagus --url https://app.palagus.ai/api/mcp
    codex mcp login palagus
    ```
  </Step>

  <Step>
    Approve the permissions in the browser. Codex asks for none in particular, so it receives all three.
  </Step>

  <Step>
    Ask in plain words. Codex offers no reports; the tools are called all the same.
  </Step>
</Steps>

## 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](https://www.perplexity.ai/help-center/en/articles/13915507-adding-custom-remote-connectors)
* **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](https://support.google.com/gemini/answer/17209137)
* **Microsoft Copilot:** The personal Copilot cannot add servers like Palagus; Microsoft 365 Copilot can, set up by your company's admin. [Microsoft's guide](https://learn.microsoft.com/en-us/microsoft-copilot-studio/mcp-add-existing-server-to-agent)

## 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](/usecases) or one of the [six reports](/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.

<Info>
  **Still stuck?** Write to [support@palagus.com](mailto:support@palagus.com) and tell us which assistant you use and what it said.
</Info>

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


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.