Vlozi MCP speaks the standard Streamable HTTP transport at https://mcp.vlozi.app/mcp. Every modern MCP client connects with one command, one config block, or — for clients with a native "Sign in" button — no manual setup at all.
TIP
For Claude Code, Claude Desktop, or Cursor, npx @vlozi/cli auth login does all of this for you — see Quick connect. If your client has a built-in "Connect" / "Sign in" flow (Claude.ai), see the "Claude.ai (and other OAuth clients)" section below instead — it needs no key at all. Use the manual header-pasting steps for any other client, CI pipelines, or headless agents.
IMPORTANT
Replace YOUR_VLOZI_KEY with your secret key from Settings → API Keys at vlozi.app. It starts with ls_.
Claude.ai (and other OAuth clients)
Some MCP clients — Claude.ai's remote-MCP connector, and any client built against the MCP authorization spec — connect with a real "Sign in with Vlozi" flow instead of a pasted key. There's no config to write: give the client the server URL, click Connect, and approve the request in your browser when it appears.
Server URL: https://mcp.vlozi.app/mcp
That's the only field a client like this asks for. Everything else — registration, the authorization redirect, token exchange — happens automatically:
- The client discovers Vlozi's OAuth endpoints on its own (
/.well-known/oauth-authorization-server) and registers itself. - It opens your browser to a Vlozi consent screen showing the client's name and exactly what it's asking to access.
- You approve (choosing a role or hand-picking permissions, same picker as Settings → API Keys) or deny.
- The client receives its own access token — no
ls_key ever touches its config.
The token is short-lived and refreshes itself automatically behind the scenes. To disconnect a client you've approved this way, go to Settings → API Keys → Connected apps and click Disconnect — this stops it from refreshing again (its current access token, valid for up to an hour, simply expires on its own shortly after), rather than making you wait out its full 90-day connection.
TIP
Approving one of these is exactly as consequential as creating an API key — the client can do whatever permissions you grant it. Check the client name and requested permissions before clicking Approve, the same way you'd review before minting a key manually.
Claude Code
claude mcp add --transport http vlozi https://mcp.vlozi.app/mcp \
--header "Authorization: Bearer YOUR_VLOZI_KEY"claude mcp list # vlozi https://mcp.vlozi.app/mcp ✓ connectedClaude Desktop
Settings → Developer → Edit Config:
{
"mcpServers": {
"vlozi": {
"url": "https://mcp.vlozi.app/mcp",
"headers": { "Authorization": "Bearer YOUR_VLOZI_KEY" }
}
}
}Restart Claude Desktop.
Cursor
Settings → Cursor Settings → MCP:
{
"mcpServers": {
"vlozi": {
"type": "http",
"url": "https://mcp.vlozi.app/mcp",
"headers": { "Authorization": "Bearer YOUR_VLOZI_KEY" }
}
}
}Windsurf
Windsurf Settings → MCP servers → Add server:
{
"mcpServers": {
"vlozi": {
"serverUrl": "https://mcp.vlozi.app/mcp",
"headers": { "Authorization": "Bearer YOUR_VLOZI_KEY" }
}
}
}Antigravity
Add a .mcp.json to your project root:
{
"mcpServers": {
"vlozi": {
"type": "http",
"url": "https://mcp.vlozi.app/mcp",
"headers": { "Authorization": "Bearer YOUR_VLOZI_KEY" }
}
}
}Codex CLI
Edit ~/.codex/mcp.json:
{
"servers": {
"vlozi": {
"transport": "http",
"url": "https://mcp.vlozi.app/mcp",
"headers": { "Authorization": "Bearer YOUR_VLOZI_KEY" }
}
}
}codex --reloadContinue.dev
Edit ~/.continue/config.yaml:
mcpServers:
- name: vlozi
url: https://mcp.vlozi.app/mcp
headers:
Authorization: Bearer YOUR_VLOZI_KEYOther MCP clients
Any client that supports MCP Streamable HTTP (spec rev 2024-11-05+):
| Field | Value |
|---|---|
| URL | https://mcp.vlozi.app/mcp |
| Method | POST (JSON-RPC) |
| Header | Authorization: Bearer YOUR_VLOZI_KEY |
First test
In any of the clients above:
Use the vlozi tools to list my blog categories and any drafts I have.
A working setup calls blog.list_categories then blog.list_posts and reports back.
Troubleshooting
| Symptom | Fix |
|---|---|
All calls return -32001 |
Key missing/wrong — test with curl first (see Quickstart) |
| Some tools missing | Key or OAuth grant missing scopes — see Authentication |
-32601 Method not found |
Client speaks legacy SSE — use mcp-remote as a bridge |
| Connection timeout | Corporate proxy — whitelist mcp.vlozi.app |
| OAuth client never shows a consent screen | Client didn't hit /.well-known/oauth-authorization-server — confirm it supports the MCP authorization spec, not just Streamable HTTP |
| OAuth-connected client stopped working | Its connection may have been disconnected from Settings → API Keys → Connected apps, or its access token simply expired mid-session — it should refresh automatically on the next call |