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

# Connect Claude

> Add levios as a custom connector in Claude.

<Note>
  Hosted Claude Desktop has completed levios registration, consent, token
  exchange, tool discovery, and authenticated read calls. The successful run did
  not capture the exact Claude version, build, or total connection time. The
  result is observed compatibility, not formal validation.
</Note>

## Add the connector on Pro or Max

1. Open Claude and go to **Customize > Connectors**.
2. Select **+**, then **Add custom connector**.
3. Enter `levios` as the connector name.
4. Paste `https://levios.app/api/mcp` into the URL field and select **Add**.
5. Sign in to levios in the browser window that opens.
6. Review the permissions and Instagram accounts, then approve the request.
7. Return to Claude and ask it to list your levios accounts.

## Team and Enterprise setup

An Owner or Primary Owner must add the connector to the organization first:

1. Open **Organization settings > Connectors**.
2. Select **Add**, choose **Custom > Web**, and enter the levios endpoint.
3. Add the connector to the organization.

Each member can then open **Customize > Connectors**, find levios, and select
**Connect** to complete their own authorization.

See [Claude's custom connector guide](https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp)
for the current plan and organization controls.

## Verify access

Ask Claude to list your levios accounts or automations. The result must contain
only accounts included in the grant. Tools that need permissions you did not
approve will not appear.

If the connector has no tools, open **Settings > MCP** in levios and check its
status, permissions, and account access. Revoke the connection and start again
if you need to choose a different permission set.

Never paste an API key or bearer token into Claude. The browser authorization
flow supplies the credential.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.