Available tools and activation support depend on your current connection. After
connecting, ask the agent to check the available operations before creating an
automation.
Add the server
Run MCP: Add Server from the Command Palette, or edit the configuration
file directly. Choose one location:
- Use
.vscode/mcp.json inside a workspace to make levios available only in
that workspace.
- Use MCP: Open User Configuration to make levios available in every
workspace.
Add this remote server entry:
VS Code uses servers as the top-level key, not mcpServers. If the file
already has other servers, add the levios entry inside the existing servers
object instead of replacing the file.
See the VS Code MCP guide
for the current configuration locations and server format.
Authorize the connection
levios requires browser authorization. Start the server in VS Code and complete
the levios sign-in when prompted, then review the permissions and Instagram
accounts and approve the request.
The VS Code MCP guide linked above documents the server format but not the
authorization flow, so the exact prompt wording may differ from the description
here. If VS Code never opens a browser window, the connection cannot complete
and the server will list no tools.
Verify access
Ask Copilot Chat in agent mode 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 add headers, an API key, or a bearer token to this entry. levios uses the
server’s OAuth flow.
