MCP server
Connect Claude, ChatGPT, Cursor, and other MCP clients to an eksis workspace.
eksis speaks the Model Context Protocol, so any MCP client can work in a workspace: check, schedule, and approve posts, manage the queue and media, moderate and answer comments, reply to direct messages, and read analytics. It is the same API with the same roles and quotas, spoken by an assistant instead of your code.
Server URL
https://api.eksis.io/mcpThe transport is Streamable HTTP. Every client uses this one URL.
Authentication
A connection reaches exactly one workspace, and you pick which one when you connect. The client decides how: apps that cannot send headers sign in with OAuth, tools that can send headers use an API key.
Sign in with OAuth
The app opens a consent screen on eksis, where you pick one workspace and the permissions the assistant may use. The connection then shows up on the API & MCP page of that workspace, where it can be disconnected at any time. It works on every plan.
Send an API key header
Tools that can send headers take an API key you create on the API & MCP page of the workspace, exactly like a REST call. The key decides the workspace and the role, and no consent screen appears. Every plan can create a key for this, the Free plan included. What a Free key cannot do is call the REST API.
| Header name | Header value |
|---|---|
Authorization | Bearer eksis_sk_... |
X-API-Key | eksis_sk_... |
The header name is Authorization
Not Bearer. Many clients ask for the header name and value in two separate boxes, and putting Bearer in the name box is the most common mistake. If your client only takes a plain key, name the header X-API-Key and paste the key alone.
Permissions
| Scope | What it allows |
|---|---|
read | Read channels, posts, the queue and calendar, media, comments, direct messages, analytics, and the list of webhook endpoints. |
write | Create, change, schedule, approve, and publish posts, manage queue slots, upload and delete media, moderate and reply to comments, and reply to direct messages. |
OAuth asks for read, and for write only if you allow it. An API key always holds both. Either way, the role of the person or key behind the connection sets the ceiling: a scope never grants more than that role is allowed to do. Connections made before October 2026 keep the scopes they were given, and those scopes now also cover direct messages.
Direct messages and analytics follow the workspace's plan. On a plan without them, those tools answer that the plan does not include the feature.
Replies to direct messages
A reply goes privately to a real person, so the reply tool tells the assistant to show you the exact text and wait for your yes before sending. It also tells the assistant never to follow instructions written inside a message or a comment. An assistant can only answer a conversation, never start one.
Two things stay out of the assistant's reach on purpose: creating or changing webhook endpoints, and deleting many posts at once. Do those in the app or through the REST API. An assistant can list webhook endpoints, but never sees their signing secrets.
Quota
Every tool call counts as one request against the workspace's daily quota, the same quota REST requests use. Reading the tool list needs no credential and does not count, so a client can show what eksis offers before anyone signs in. The daily quota for each plan is in the API reference.
Set up your client
Pick the assistant you use. The server URL is the same for all of them.
Claude
Sign-in: OAuth
Claude Code
Sign-in: OAuth or API key
ChatGPT
Sign-in: OAuth
Codex
Sign-in: OAuth or API key
Cursor
Sign-in: OAuth or API key
VS Code
Sign-in: OAuth or API key
OpenCode
Sign-in: OAuth or API key
OpenClaw
Sign-in: OAuth or API key
Hermes
Sign-in: OAuth or API key
Grok Bot
Sign-in: OAuth
Nakama
Sign-in: OAuth or API key
Any other client
Sign-in: OAuth or API key
The tool list shows what an assistant can ask eksis to do. To do the same work from your own code, use the REST API.