Add Kesk to your AI client

Kesk MCP servers use remote HTTP transport, so most clients need nothing more than a URL. Sign-in happens in the client — you approve access with your Kesk account when it first connects. No API keys to copy, nothing to paste into a config file.

Server URLs

Consumer — your own Kesk account: order food, book a ride, track a parcel.

Per-category servers are also available if you want to connect just one:

for food, groceries, pharmacies, shops, services, taxis, parcels, dining, sports, rentals, accommodations.

Vendor — run your business: orders, catalogue, locations.

for the same eleven categories above. Use the one your business is registered under.

Claude

Claude web and desktop

  1. Settings → Connectors
  2. Add custom connector
  3. Name it Kesk, paste https://mcp.kesk.app/v1/users
  4. Add, then Connect and sign in with Kesk

The connector appears in the attachments menu in any chat.

Claude Code

Then /mcp inside Claude Code to authenticate. Add --scope user to make it available across all your projects rather than just the current one.

For a vendor server:

Codex

Add to ~/.codex/config.toml:

Or from the CLI:

Restart Codex, then /mcp to check the connection and sign in.

ChatGPT

  1. Settings → Connectors → Advanced → Developer mode
  2. Create a new connector
  3. Name it Kesk, paste https://mcp.kesk.app/v1/users
  4. Choose OAuth authentication and connect

Requires a plan with Developer mode available.

Cursor

Settings → MCP → Add new global MCP server, then:

Or drop the same JSON in .cursor/mcp.json in a project to scope it there.

VS Code

Or add to .vscode/mcp.json:

Gemini CLI

Add to ~/.gemini/settings.json:

Windsurf

Add to ~/.codeium/windsurf/mcp_config.json:

Zed

Add to your settings.json:

Anything else

Kesk works with any MCP client supporting remote HTTP transport — Siri, Perplexity, DeepSeek, Kimi, Hermes and Copilot among them. Look for "custom connector", "remote MCP server", or an mcpServers config block, and give it the URL.

If your client only supports stdio, bridge it:

What you are approving

When you connect, the client asks Kesk for access and you approve it. Personal and vendor access are kept separate — a consumer connector cannot reach vendor operations.

You grant only what you choose and can disconnect at any time. Actions involving money are surfaced for confirmation before they commit, rather than being executed silently.

Two things are deliberately never included in a normal approval, and must be granted explicitly:

  • Payment history and profile changes on a consumer account
  • Autonomous unit access on a vendor account — this covers issuing machine credentials for drones and robots, so connecting an assistant to a merchant account never hands it the keys to the fleet

Troubleshooting

The client connects but lists no tools. You are connected but not signed in. Run /mcp (Claude Code, Codex) or reopen the connector settings and complete sign-in.

406 Not Acceptable — only relevant if you are writing your own client. The Accept header must include both application/json and text/event-stream.

Building your own client

See Vendor tools for the tool surface, and MCP overview for the raw JSON-RPC transport details.

Built with