> ## 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 Grok

> Add levios as a custom MCP connector in Grok.

<Note>
  Available tools and activation support depend on your current connection. After
  connecting, ask the agent to check the available operations before creating an
  automation.
</Note>

## Add the connector

1. Open `https://grok.com/connectors`.
2. Select **New Connector**, then **Custom**.
3. Enter `https://levios.app/api/mcp` as the MCP server URL.
4. Complete the authentication step.
5. Sign in to levios, review the permissions and Instagram accounts, then
   approve the request.

Grok then discovers the tools that levios exposes for your grant.

The levios endpoint is served on the public internet, so it satisfies xAI's
requirement that a custom MCP server be publicly reachable. You do not need a
tunneling service.

## Authentication

xAI documents OAuth for its own built-in connectors. Its custom connector
documentation does not state which authentication methods a custom MCP server
may use, so levios cannot confirm from that source that the browser
authorization flow completes here.

levios accepts only that flow. If Grok's custom connector step asks for an API
key or a static header instead of opening a browser sign-in, the connection
cannot complete, and the connector will list no tools.

See [xAI's connector guide](https://docs.x.ai/grok/connectors) for the current
custom connector behavior.

## Verify access

Ask Grok 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 Grok. The browser authorization flow
supplies the credential.


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