Connect an assistant

Scope keeps one approved freelance record for ChatGPT, Claude, Gemini, Grok, Cursor, and any other MCP client that speaks Streamable HTTP and OAuth. It is not a ChatGPT-only plugin. Scope tools need Pro or an active trial. A new subscription includes a 14-day trial.

Shared connection

MCP address:

https://scope-continuity2.vercel.app/mcp

Transport: Streamable HTTP. Sign in with your Scope account when the assistant opens OAuth. Dynamic client registration is supported, so leave the client id and secret empty. Do not paste an API key, access token, or password into a header or into the chat.

An unauthenticated tool call returns 401 with a WWW-Authenticate challenge pointing at https://scope-continuity2.vercel.app/.well-known/oauth-protected-resource/mcp. That document names the OAuth issuer. The issuer registers clients. Ask for the email scope, and offline_access when the client can refresh tokens.

  1. Sign in and start a trial if you have not already.
  2. Add the MCP address using the steps below.
  3. Approve Scope, then ask the assistant to read the approved record before it answers.

ChatGPT

  1. Enable custom MCP connectors if your workspace requires it.
  2. Create a custom app and enter the MCP address.
  3. Choose OAuth, leave client credentials empty, and approve Scope.

Claude

  1. Add a custom connector and paste the MCP address.
  2. Choose OAuth and register the client automatically. Do not put a token in request headers.
  3. Approve Scope, then enable the connector in the chat.

Claude Code:

claude mcp add --transport http scope https://scope-continuity2.vercel.app/mcp

Do not pass an Authorization header. In a JSON config, set "type": "http" next to url.

Gemini

  1. In the Gemini web app, open Settings, then Connected apps.
  2. Add a custom app and paste the MCP address.
  3. Leave advanced credentials empty. Scope's authorization server registers the client.

Gemini CLI:

gemini mcp add --transport http --scope user scope https://scope-continuity2.vercel.app/mcp

Do not set an Authorization header.

Grok

  1. Open grok.com/connectors.
  2. Choose a custom connector and paste the MCP address.
  3. Finish the sign-in Grok presents.
grok mcp add --transport http scope https://scope-continuity2.vercel.app/mcp

Do not set an Authorization header. The xAI API's static bearer field is not a Scope API key. Use a client that performs OAuth.

Cursor and other MCP clients

In ~/.cursor/mcp.json or a project .cursor/mcp.json:

{
  "mcpServers": {
    "scope": {
      "url": "https://scope-continuity2.vercel.app/mcp"
    }
  }
}

Do not add headers or a static client id. Cursor registers a client and opens sign-in. Any other client can use the same address when it supports Streamable HTTP, OAuth with PKCE, and dynamic client registration. Clients that call from their own servers should omit a browser Origin. Browser calls are accepted only from Scope and the assistant sites on the server allowlist.

After it connects

Ask the assistant to call get_approved_record before it talks about scope, rates, or deadlines. A lower rate and any new deliverable need an approved change order. If a tool refuses, the assistant must stop rather than invent a workaround.

When you run this server yourself, the address above is the configured base URL. This repository does not publish a separate production domain.