[ docs ]MCP
Connect the AI you use every day
Zomler is an MCP server. Any assistant, editor, CLI, automation platform or agent framework that speaks MCP over HTTP connects with one URL and gets every platform tool with its schema attached.
https://api.zomler.com/mcpPick your client
Each guide has the exact config for that client and, where it exists, a one-click install.
Assistant
Editor
Automation
Two ways to prove who you are
The server is the same for every client; what differs is how the client authenticates.
- Sign in with a browser. Claude, ChatGPT, Cursor, Claude Code, VS Code and Windsurf open a tab, you approve, done. Nothing to copy but the URL. The connection shows under Connections in your dashboard and can be disconnected there.
- An API key. Clients that run from a config file or a server — CLIs, automation platforms, agent frameworks, anything headless — send
Authorization: Bearer zk_live_…instead. Create it under API keys. The same key works on the REST API, and revoking it closes both.
Whichever way a client connects, it gets the same tools: one per platform, plus capabilities and check_balance. Every answer carries the same envelope the REST API returns, and every fetch costs the same credits.
After connecting
Ask in plain language. The tools describe their own ops, so a client knows that Instagram has profiles, posts and hashtagwithout being told. Anything already held is served free; a fresh fetch is measured, stored and billed once. Say "estimate first" and the client quotes before spending.
A connected client can spend the account's balance. Disconnect it under Connections, or revoke its key under API keys, and the next call is refused.