Skip to main content
Claude Code has completed levios authorization and authenticated read calls. The recorded run did not capture the exact Claude Code version, build, or negotiated MCP revision. The result is observed compatibility, not formal validation.

​
Add the server

Run this from your terminal:
Claude Code stores the server in local scope by default, which keeps it private to you in the current project. Choose a different scope when you need one:
Use --scope user to reach levios from every project on your machine. Use --scope project only if you intend to commit the server entry to .mcp.json and share it with everyone who clones the repository. The endpoint is public, so sharing it exposes no secret, but each person still completes their own authorization. A project-scoped entry looks like this:

​
Authorize the connection

Run the /mcp command inside Claude Code and follow the browser prompt:
Sign in to levios, review the permissions and Instagram accounts, then approve the request. Claude Code stores the resulting credential for you. To clear it later:
See Claude Code’s MCP guide for the current transport flags and scope precedence.

​
Verify access

Ask Claude Code 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 server 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. Do not pass --header with an API key or bearer token. levios authenticates through the browser authorization flow.