Skip to main content
The levios MCP server lets compatible AI clients call levios tools after you approve access to specific permissions and Instagram accounts. Use this remote MCP endpoint:

​
Plan an outcome

Start with Create your first automation in chat. Compare objectives, use a follow gate when growth is the priority, or find strategic contacts. Read Instagram limits before promising a sequence. When tools/list exposes get_automation_guide, your agent can retrieve the guidance and the connection’s draft permission and activation route directly. It does not verify account or plan eligibility. If your server release does not expose it yet, share these pages.

​
Connect a client

  1. Copy the endpoint above.
  2. In your AI client, add a custom app, connector, or remote MCP server.
  3. Paste the endpoint and confirm the connection.
  4. Sign in to levios in the browser window that opens.
  5. Review the requested permissions and accounts, then approve the request.
  6. Return to the client and ask it to list your levios accounts.
OAuth handles the connection. Do not paste an API key, access token, or other secret into the client setup form.

​
Setup guides

Each guide carries the evidence levios has for that client. Read the callout at the top before you rely on it.

Claude

Claude Code

Cursor

ChatGPT

ChatGPT Work

Codex

VS Code

Gemini CLI

Antigravity

Perplexity

Grok

Grok Bot

Devin

Hermes Agent

OpenClaw

A client missing from this list may still work. The endpoint is a standard remote MCP server, so any client that supports remote MCP over OAuth can connect to it.

​
Available surface

levios publishes MCP tools. It does not publish MCP resources or prompts. The tools visible to a client depend on the permissions you approved. The client can discover permitted tools for accounts, Instagram media, automations, contacts, metrics, configuration, and activation changes. A tool outside the grant does not appear in the client’s tool list. Every tool call is restricted to accounts in the grant. Your client receives the authoritative JSON input and output schemas through tools/list. Those schemas include required fields, enum values, and the complete typed automation configuration. They are not free-form payloads. Account-scoped tools accept account_id as a UUID or an @username. Omit it only when the OAuth grant reaches exactly one account. When the grant reaches several accounts, use list_accounts or the account_cursor and account_limit fields exposed by the tool schema.

​
Available tools

For activation changes, and for creating an automation that starts live, the tool first returns a preview and asks whether to apply it. A positive response authorizes that specific short-lived transition. A later configuration change invalidates it. Read operations and changes use separate permissions. Pausing an OAuth grant keeps permitted reads available and blocks changes. You can pause or revoke a connection from Settings > MCP in levios.

​
Protocol support

The modern server path implements MCP 2026-07-28. levios also keeps a stateless compatibility path for the 2025-era wire used by some clients. Both paths use the same OAuth authorization, account boundaries, permission checks, and tool registry. Use Create a carousel with an agent to plan and validate image cards, link buttons, and the following action.

​
Authoring guides