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

# Connecting

> Add the GC AI MCP server to ChatGPT, Claude, Cursor, or any MCP client, and sign in with your GC AI account.

The GC AI MCP server lives at one endpoint:

```
https://app.gc.ai/api/mcp
```

You do not need an API key. The server authenticates with your GC AI login through a standard OAuth flow: when you add it, your host opens a GC AI sign-in page, you approve access, and the host stores the connection. Every request then runs as you.

## Before you connect

Two things need to be true for the connection to work:

1. **You have a GC AI account.** The assistant acts as you, so you sign in with your own credentials.
2. **Your organization has the MCP server enabled.** It is off by default. If sign-in succeeds but tools do not appear, ask your GC AI admin to turn it on, or reach out to support.

## Add the server to your host

The steps differ slightly by host, but the shape is the same everywhere: point the host at the endpoint above, then complete the GC AI sign-in when prompted.

<Tabs>
  <Tab title="ChatGPT">
    In a ChatGPT plan that supports connectors, add a new connector using the URL `https://app.gc.ai/api/mcp`. ChatGPT walks you through the GC AI sign-in, then lists the GC AI tools. Enable the ones you want the assistant to use.
  </Tab>

  <Tab title="Claude">
    In Claude, add a custom connector pointing at `https://app.gc.ai/api/mcp`. Approve the GC AI sign-in when Claude opens it, and the GC AI tools become available in your conversations.
  </Tab>

  <Tab title="Cursor">
    Add the server to your MCP configuration with the same URL. Cursor opens the GC AI sign-in on first use, then the tools are available to the agent.

    ```json theme={null}
    {
      "mcpServers": {
        "gc-ai": {
          "url": "https://app.gc.ai/api/mcp"
        }
      }
    }
    ```
  </Tab>

  <Tab title="Other clients">
    Any MCP client that supports remote servers over HTTP with OAuth can connect. Use the endpoint `https://app.gc.ai/api/mcp`; the client discovers the sign-in flow automatically from the server's OAuth metadata.
  </Tab>
</Tabs>

<Note>
  The exact menu labels vary by host and change over time. If you do not see a place to add a remote MCP server or connector, check that your plan supports custom connectors.
</Note>

## Verify the connection

Once connected, ask the assistant to run a quick read, for example: "List my GC AI projects." That calls `get_projects` and confirms the tools are wired up and scoped to your account. From there the assistant can upload files, run playbooks, and ask questions grounded in your knowledge base.

## Related

* [MCP server overview](/api-reference/mcp/overview): what the server does and how requests are scoped.
* [REST API introduction](/api-reference/introduction): for backend integrations and scripts rather than assistants.