Vlozi MCP lets your AI agent do real work in your workspace — publish blog posts, search your knowledge base, draft and schedule content — using the same API key you already have.
Point any AI client (Claude Desktop, Cursor, Windsurf, n8n, a custom script) at mcp.vlozi.app and it gains 14 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"The one-config patterns for every other client live on the MCP clients page.
What an agent can do
| Namespace | Capabilities |
|---|---|
blog.* |
List, create, edit, publish, schedule, delete, search posts; manage tags and categories |
brain.* |
Ask natural-language questions of your knowledge base; ingest new docs; return cited context |
More products (contacts, newsletter, content engine, media, chat) ship in the next release.
How it works
You don't run anything. Vlozi hosts the gateway at mcp.vlozi.app. Your agent sends an HTTP request with your API key; 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 API key resolves your workspaceThe same ls_xxx API key you use for the REST API works here. No new auth.
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.