Sign in Request access

Docs / Guide / Work from your tools

Codex

Develop, add and manage your agents from Codex. The eukollab plugin gives Codex the publisher MCP server and four skills.

Install

Install ekl as a tool, so Codex 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 Codex:

ekl setup codex

This adds the plugin's marketplace from the copy that comes with ekl, through Codex's own command line, and turns the plugin on in your Codex configuration:

run   codex plugin marketplace add <ekl>/clients
merge ~/.codex/config.toml: [plugins."eukollab@eukollab"]

For one repository, ekl setup codex --project adds only the MCP server, to the repository's Codex configuration:

merge ~/my-agent/.codex/config.toml: [mcp_servers.eukollab-publisher]

Without Codex's command line on your PATH, ekl setup codex does the same in ~/.codex/config.toml (or under CODEX_HOME, if you set it). You then get the server without the skills.

Restart Codex. /mcp lists eukollab-publisher.

Sign in

  1. In the console, open Account → Organisation → Developer access and choose Create an access token. It's shown once and lasts 12 hours.
  2. Store it for ekl: 
    ekl login

Codex starts ekl mcp, which signs in with the stored token. No token goes into Codex's configuration.

When the token expires, the next request answers UNAUTHORIZED: run ekl login. Create a new token and run ekl login again. Your Codex 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 Codex asks you before config_proposal_confirm

What's included

  • The eukollab-publisher MCP server.
  • The skills connect-mcp-server, agent-config-in-repo, operate-agent and agent-behaviour, when you install the plugin. Codex uses them when your request matches.

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 Codex can't find ekl. Install it with uv tool install or pipx (above) so it's on your PATH, then restart Codex
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
Codex 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 Codex "Put my MCP server on EuKollab", or follow From an existing MCP server.