Vlozi MCP lets your AI agent do real work in your workspace — publish blog posts, search your knowledge base, draft and schedule content — authenticated however suits your client: an API key you already have, or a native "Sign in" flow for clients that support one.
Point any AI client (Claude Desktop, Cursor, Windsurf, n8n, a custom script) at mcp.vlozi.app and it gains typed tools to drive your Vlozi account.
30-second setup
Native MCP clients connect with a single command. For Claude Code:
claude mcp add --transport http vlozi https://mcp.vlozi.app/mcp \
--header "Authorization: Bearer YOUR_VLOZI_KEY"Have a client with its own built-in "Connect" or "Sign in" button instead (Claude.ai's remote-MCP connector)? Skip the key entirely — point it at https://mcp.vlozi.app/mcp and click Connect. See MCP clients for both paths, and every other client's config block.
What an agent can do
| Namespace | Capabilities |
|---|---|
blog.* |
List, create, edit, publish, schedule, delete, restore posts; manage tags and categories; view analytics |
brain.* |
Ask natural-language questions of your knowledge base; ingest new docs; manage memories; return cited context |
contacts.* |
CRM: profiles, timelines, channels, memory; schedule and draft outreach; churn/mood analytics |
newsletter.* |
Manage subscribers, segments, and templates; create, send, or cancel campaigns |
content.* |
Social content calendar: schedule posts, recurring schedules, approve/reject slots, generate captions and hashtags |
chat.* |
Configure chatbots and channels (including WhatsApp); manage live sessions, custom tools, and analytics |
comms.* |
Send transactional email; manage sender identities, vanity aliases, and suppression lists |
collections.* |
Custom structured content types and their entries |
forms.* |
Forms, submissions, and webhook deliveries |
flow.* |
Build and manage Vlozi Flows automations |
billing.* |
Read credit balance, usage, costs, and transaction history |
Every namespace is filtered by your credential's permission scopes — an agent only ever sees the tools it's actually allowed to call.
How it works
You don't run anything. Vlozi hosts the gateway at mcp.vlozi.app. Your agent sends an HTTP request with a credential — an API key or an OAuth access token; the gateway resolves your workspace, filters tools to your permission scopes, and routes the call to the right Vlozi service.
your agent → mcp.vlozi.app → product service → your data
↑
ls_xxx key, or an OAuth token, resolves your workspaceThe same ls_xxx API key you use for the REST API works here — no new auth to learn if you're already using one. Clients with a native sign-in flow use OAuth instead; see Authentication for both.
Two endpoints, same backend
| Endpoint | Protocol | Use for |
|---|---|---|
POST /mcp |
JSON-RPC 2.0 | Native MCP clients (auto-handled) |
POST /tools/<name> |
Plain JSON | curl, n8n, custom HTTP agents |
Pick whichever your caller speaks. Auth, tools, permissions, and rate limits are identical.