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

# Connect from Claude

> Add NextLevel MCA as a custom connector in Claude and sign in with your work email.

Claude connects to the MCP server as a custom connector. You need a NextLevel MCA user account (the email you sign in to the app with) and a Claude plan that supports custom connectors; on Team and Enterprise plans an admin may need to enable them first.

## Add the connector

<Steps>
  <Step title="Open Claude settings → Connectors">
    In Claude on the web or desktop, open **Settings**, then **Connectors**, and choose **Add custom connector**.
  </Step>

  <Step title="Enter the server URL">
    Name it `NextLevel MCA` and set the URL to:

    ```text theme={null}
    https://api.nextlevelmca.com/mcp
    ```

    Leave the advanced OAuth fields empty. Claude registers itself with the authorization server automatically.
  </Step>

  <Step title="Connect and sign in with your work email">
    Click **Connect**. A NextLevel MCA sign-in page opens. Enter the email you use for the app. You always see "check your email", whether or not the address is known.
  </Step>

  <Step title="Open the magic link">
    The email contains a sign-in link that works once and expires in 10 minutes. Opening it returns you to the authorization flow.
  </Step>

  <Step title="Pick a location">
    If your email belongs to more than one location, choose the one this connection should work in. A connection is bound to exactly one location; add the connector again for another.
  </Step>

  <Step title="Approve the scopes">
    The consent screen shows what Claude will be able to do. Approve to finish; Claude shows the connector as connected.
  </Step>
</Steps>

## What the consent screen shows

* The client requesting access (Claude) and the location you picked.
* The signed-in email.
* Each scope in plain language, for example "Read deals, submissions and the pipeline" or "Submit deals to lenders and withdraw submissions".
* **Approve** and **Deny**. Deny sends you back to Claude with no access granted.

The scopes listed are the ones the client asked for. Claude asks for none, so the consent screen offers every scope, each ticked by default; untick anything the connection should not be able to do (for example the write scopes, if it should only answer questions and summarise). If you already approved the same client for the same location with the same scopes, the consent step is skipped on reconnect.

## Use it

In a conversation, open the tools menu and make sure the NextLevel MCA connector is enabled, then ask in plain language. See [example prompts](/mcp/overview#example-prompts). Claude asks before running tools that send anything.

If a tool answers with a message like "This connection wasn't granted the submissions:write scope", that scope was unticked on the consent screen. Remove the connector, add it again, and leave the scope ticked when you approve.

## Revoke access

* In the app: **Settings → Developers → Connected apps** lists every connection for the location with the user, client, scopes and last use. **Revoke** ends it immediately: the refresh token family is revoked and the next request from Claude fails until the user reconnects.
* In Claude: Settings → Connectors → remove the connector. This deletes Claude's tokens but does not by itself revoke the consent on our side; do both if you are offboarding someone.

Deactivating a user in the app also invalidates every token issued to them.


## Related topics

- [MCP server](/mcp/overview.md)
- [Connect from ChatGPT](/mcp/connect-from-chatgpt.md)
- [Overview](/getting-started/overview.md)