# Connecting your assistant

Every connection starts the same way: copy your MCP endpoint from the
[AI assistants (MCP)](/360/integrations/mcp) page, paste it into your
assistant, and sign in. The page walks you through the same three steps —
**copy your endpoint**, **add it to your assistant**, **authorize & verify** —
with ready-to-copy snippets for each client.

<Screenshot
  src="/help/screenshots/ai-assistants/mcp-page.png"
  alt="The AI assistants (MCP) page in the 42min dashboard, showing the endpoint URL with a copy button, setup tabs for Claude, ChatGPT, Claude Code and other clients, and the connected-assistants list"
  caption="AI assistants (MCP) under Integrations — Step 1 is your endpoint with a copy button, Step 2 has per-client setup tabs, Step 3 lists every assistant you've authorized."
/>

## Your endpoint

The endpoint URL is shown in **Step 1** on the
[AI assistants (MCP)](/360/integrations/mcp) page, with a copy button. On
42min.us it is:

```
https://api.42min.us/mcp
```

## Two ways to sign in

- **OAuth (recommended).** Paste the endpoint, and the assistant sends you to
  a 42min consent screen where you sign in and approve access. No keys to
  copy, and you can revoke access from 42min at any time. OAuth grants always
  include both read and write access — the consent screen shows exactly what
  that covers.
- **Personal access token (PAT).** For clients where you'd rather use a key —
  or when you want **read-only** access, which OAuth doesn't offer. Mint one
  under [Admin Center → API → API keys](/360/api?tab=apiKeys) (Owner or Admin
  role required) with the scopes you want, and pass it as a bearer token. See
  [Permissions and security](/help/ai-assistants/permissions-and-security)
  for which scopes map to which tools.

## Claude (web and desktop)

1. In Claude, go to **Settings → Connectors → Add custom connector**.
2. Paste the endpoint URL and save.
3. Claude opens the 42min consent screen — sign in and approve. That's it; no
   app registration is needed.

## ChatGPT

1. In ChatGPT on the web or in the desktop app, open **Settings → Apps &
   Connectors** (named "Connectors" in older versions) → **Advanced
   settings**, and turn on **Developer mode**.
2. Go back to **Apps & Connectors**, click **Create**, and paste the endpoint
   URL into the **MCP Server URL** field.
3. Choose **OAuth** authentication and save, then sign in and approve on the
   42min consent screen.

<Callout type="note">
Custom connectors in ChatGPT require a paid plan (Plus, Pro, Business,
Enterprise, or Edu) and are not available in the ChatGPT mobile apps.
</Callout>

## Claude Code

Run one command in your terminal:

```bash
claude mcp add --transport http 42min https://api.42min.us/mcp
```

Claude Code prompts you to authenticate with OAuth on first use. To use a
[personal access token](/360/api?tab=apiKeys) instead:

```bash
claude mcp add --transport http 42min https://api.42min.us/mcp \
  --header "Authorization: Bearer <YOUR_PAT>"
```

## Other MCP clients

Any MCP-compatible client (Cursor, Windsurf, custom agents, …) can connect
with a generic HTTP configuration:

```json
{
  "mcpServers": {
    "42min": {
      "type": "http",
      "url": "https://api.42min.us/mcp",
      "headers": { "Authorization": "Bearer <YOUR_PAT_OR_OMIT_FOR_OAUTH>" }
    }
  }
}
```

Omit the `headers` block to sign in with OAuth, or keep it and paste a PAT.

## Verify the connection

Back on the [AI assistants (MCP)](/360/integrations/mcp) page, **Step 3**
lists every assistant connected via OAuth — the application name, what it can
access, when it connected, and when it was last used. Ask your assistant
something simple ("what's my 42min username?") to confirm it's working, then
check that **Last used** updates.

PAT-based connections don't appear in that list — manage those keys under
[Admin Center → API → API keys](/360/api?tab=apiKeys), where each key shows
its own last-used time.

## Common pitfalls

- **The consent screen never appears.** If your organization's admin has
  turned AI assistant access off, authorization is refused with a message
  saying so — the connection can't be approved until it's re-enabled.
- **The assistant connected but tools are missing.** With a PAT, the
  assistant only sees tools covered by the scopes on the key. Mint a key with
  broader scopes if you need more.
- **A colleague's setup works but yours doesn't.** Connections are personal —
  each person connects their own assistant to their own account; there is no
  org-wide connection to share.