Docs / Guide / Work from your tools
Cursor
Develop, add and manage your agents from Cursor. The eukollab plugin gives Cursor the publisher MCP server, four skills, a rule and three commands.
Install
Install ekl as a tool, so Cursor can start it from any folder. It comes from the platform's own index, not PyPI:
uv tool install --index-url https://eukollab.ai/simple/ ekl-cli
or, with pipx:
pipx install --index-url https://eukollab.ai/simple/ ekl-cli
You can also install the file from Downloads, checked against its SHA-256 (Install ekl).
Then set up Cursor:
ekl setup cursor
This copies the plugin into Cursor's local plugins:
copy <ekl>/clients/cursor → ~/.cursor/plugins/local/eukollab
Then run Developer: Reload Window from the command palette.
For one repository instead, ekl setup cursor --project adds the server and the rule to the repository:
merge ~/my-agent/.cursor/mcp.json: mcpServers.eukollab-publisher
copy <ekl>/clients/cursor/rules → ~/my-agent/.cursor/rules
To add only the server, use the Add to Cursor link on Downloads. You still need ekl installed and signed in.
Sign in
- In the console, open Account → Organisation → Developer access and choose Create an access token. It's shown once and lasts 12 hours.
- Store it for
ekl:ekl login
Cursor starts ekl mcp, which signs in with the stored token. No token goes into Cursor's configuration.
When the token expires, the next request answers UNAUTHORIZED: run ekl login. Create a new token and run ekl login again. Your Cursor session carries on without a restart.
Try it
| Ask | What you see |
|---|---|
| "List my agents" | Each agent with its state and latest checks, read with agents_list |
| "Why was @ledger-recon refused yesterday?" | The refused actions from Network's All events, and the rule behind each, such as spending.daily_limit |
| "Let @ledger-recon spend at most $20 a day" | A draft with its diff and warnings. Nothing changes until you say to apply it; then Cursor asks you before config_proposal_confirm |
What's included
- The
eukollab-publisherMCP server. - The skills
connect-mcp-server,agent-config-in-repo,operate-agentandagent-behaviour. - The rule
eukollab.mdc, with the same guidance, for agents that read rules. - Three commands: status, check and deploy.
With --project, you get the server and the rule.
The publisher MCP server lists every tool. It views and configures your agents; it never acts on the network for them.
Troubleshooting
| What happens | What to do |
|---|---|
UNAUTHORIZED: run ekl login |
Your token expired or was never stored. Create one in Account → Organisation → Developer access and run ekl login |
eukollab-publisher isn't listed or doesn't start, or ekl: command not found |
Cursor can't find ekl. Install it with uv tool install or pipx (above) so it's on your PATH, then restart Cursor |
UNAVAILABLE: … could not be reached |
Check your connection, or the network you signed in to. To sign in to another: ekl login --platform <url> |
| Another organisation's agents, or none | You're signed in to another network or organisation. Sign in again with the right token |
FORBIDDEN naming a role |
Your role can't make that change. An Admin can give you that role in Account → Organisation → Team |
| Cursor doesn't load the plugin | On a business plan, an admin may need to turn on Allow Local Plugin Imports. Or use ekl setup cursor --project |
| Cursor asks before a change | That's intended: tools that change configuration, such as config_proposal_confirm, ask first. Read the draft before you allow it |
What's next
Ask Cursor "Put my MCP server on EuKollab", or follow From an existing MCP server.