Cursor

Authentication: OAuth sign-in, API key

Server URLCopy Anchor Link

https://api.eksis.io/mcp

Set it upCopy Anchor Link

The install link below is the quickest way: Cursor opens, asks you to confirm the server, and adds the OAuth version of the configuration. To set it up by hand, add the server to ~/.cursor/mcp.json to use it in every project, or to .cursor/mcp.json to use it in one. Leave the headers out and Cursor starts the OAuth flow the first time a tool is called.

Add eksis to Cursor

ConfigurationCopy Anchor Link

{
  "mcpServers": {
    "eksis": {
      "url": "https://api.eksis.io/mcp"
    }
  }
}

Set it up with an AI agentCopy Anchor Link

Paste this prompt into Cursor, or into any other AI agent that can run commands and edit files on the same computer. It stops and hands back to you when eksis asks you to sign in.

Connect the eksis MCP server to Cursor on this computer.

Server URL: https://api.eksis.io/mcp
Setup guide: https://docs.eksis.io/en/mcp/clients/cursor

Use OAuth sign-in. Follow the API key steps only if I give you a key that starts with eksis_sk_. Then use my key wherever the steps show eksis_sk_..., or set it as EKSIS_API_KEY where they read that variable.

OAuth:
Write this to `~/.cursor/mcp.json`. If the file already exists, merge it in and keep the other servers.
```json
{
  "mcpServers": {
    "eksis": {
      "url": "https://api.eksis.io/mcp"
    }
  }
}
```

API key:
Write this to `~/.cursor/mcp.json`. If the file already exists, merge it in and keep the other servers.
```json
{
  "mcpServers": {
    "eksis": {
      "url": "https://api.eksis.io/mcp",
      "headers": {
        "Authorization": "Bearer ${env:EKSIS_API_KEY}"
      }
    }
  }
}
```

From the setup guide:
The install link below is the quickest way: Cursor opens, asks you to confirm the server, and adds the OAuth version of the configuration. To set it up by hand, add the server to `~/.cursor/mcp.json` to use it in every project, or to `.cursor/mcp.json` to use it in one. Leave the headers out and Cursor starts the OAuth flow the first time a tool is called.

Rules:
- If Cursor already has a server named eksis, show me its entry and ask before you change it.
- Never put an API key in a file that is committed to git. Keep it in an environment variable or the client's own secret store, as the steps show.
- If a command asks a question interactively, show me the question and wait for my answer.
- When eksis opens a sign-in page in the browser, stop and ask me to pick the workspace and approve it. Do not approve it for me.

When you are done, check the connection and list the eksis tools Cursor can see. If it fails, show me the error.

Which file to useCopy Anchor Link

~/.cursor/mcp.json connects eksis in every project, and it is the only place an API key belongs. .cursor/mcp.json lives inside the repository, so commit it only in the OAuth version: the whole team gets the same server, and each person still signs in and picks their own workspace.

Keep the API key out of the fileCopy Anchor Link

Cursor fills in ${env:NAME} inside url and headers from the environment it was started in, which is why the API key version above reads EKSIS_API_KEY instead of holding the key. Set that variable, then restart Cursor so it picks up the new value.

Approving tool callsCopy Anchor Link

Cursor asks before it runs an MCP tool, and shows the arguments when you expand the call. Keep that for the eksis write tools: publishing a post or answering a message acts on a real social network, and some of it cannot be undone. If you use the Auto-review run mode, allowlist only read tools, because anything on the allowlist runs without asking. The tool list shows which tools only read.

If it does not connectCopy Anchor Link

Open the Output panel and choose MCP Logs to see why a connection or a call failed. A 401 on the API key version means the header did not arrive as Authorization: Bearer eksis_sk_..., most often because EKSIS_API_KEY was empty when Cursor started. If the server reached the wrong workspace, disconnect it on the API & MCP page of that workspace, then sign in again from Cursor and pick the right one.

How the two ways of signing in differ, and what each permission allows, is on the MCP overview. The tool list shows what the assistant can ask eksis to do.