---
title: "Connect an AI client"
description: "Add the Lookio MCP server to Claude, Cursor, ChatGPT or another client, approve the connection with OAuth, or use an API key for an unattended agent."
canonical: "https://lookio.app/docs/developers/mcp/connect"
updated: "2026-11-08"
---

# Connect an AI client

The server URL is the same everywhere:

```text
https://mcp.lookio.app/mcp
```

Client menus change often, so the steps name the setting, not the button. See each client's own documentation for its menus.

## Claude

**Claude.ai and Claude Desktop**

In Claude's connector settings, add a custom connector and paste the URL. Claude opens Lookio in your browser. Approve the connection. The Lookio tools then show in the conversation.

**Claude Code**

```bash
claude mcp add --transport http lookio https://mcp.lookio.app/mcp
```

Then run `/mcp` in Claude Code and choose **Authenticate** to approve the connection.

## Cursor

Add the server to `.cursor/mcp.json`, in your project or in your home directory:

```json title=".cursor/mcp.json"
{
  "mcpServers": {
    "lookio": {
      "url": "https://mcp.lookio.app/mcp"
    }
  }
}
```

Cursor shows a **Connect** button for the server. Click it, then approve in your browser.

## ChatGPT

In ChatGPT's connector settings, add a custom connector (an MCP server) and paste the URL. Some ChatGPT plans need developer mode for this. Approve the connection when ChatGPT opens Lookio.

## Any other client

Any client that supports remote MCP servers with OAuth works with the same URL. It finds the sign-in steps at `https://mcp.lookio.app/.well-known/oauth-protected-resource` and `/.well-known/oauth-authorization-server`, registers, and sends you to approve. See [OAuth](/docs/developers/authentication#oauth).

## What you approve

When a client asks to connect, Lookio shows the consent screen:

1. Choose the workspace, if you belong to several.
2. Untick what you do not want to grant. You can grant only what your role allows.
3. Approve.

The client then acts for you, with those permissions. On the Pro and Custom plans, you need the `mcp` permission. If your workspace lets members grant none of the requested permissions, Lookio tells you.

## Review and revoke

Open **Developer tools** in the app, then the connections section. Each connection shows who approved it, what it may do and its last use. A revoked connection stops at once.

## Use an API key instead

For an agent that runs without a person, create a workspace [API key](/docs/guides/api-keys). Put it in the client's header setting:

```text
Authorization: Bearer sk_live_...
```

Give the key only the scopes the agent needs. For an agent that only asks questions, use the **Ask questions** preset. A key never manages members or tags. A key with `assistants:write` can read the conversation [logs](/docs/guides/logs).

## Clients that need a local process

Some clients can only start a local command that uses standard input and output. For them, use the CLI bridge:

```bash
lookio mcp
```

It sends each message to the MCP server with your stored credential. First sign in with `lookio auth login`. See [CLI authentication](/docs/developers/cli/authentication).

## Test the connection

Ask your agent: "List my Lookio assistants." If the connection works, it calls `list_assistants` and shows them. If the client shows no Lookio tools, check the scopes you approved.