Zicket

Guide · Codex

Use Zicket with Codex

Codex speaks MCP over HTTP, so it connects to Zicket the same way Claude Code does. Keep the token in an environment variable, and Codex sends it on every call.

Connect it in four steps

  1. 1

    Create the agent in Zicket

    In Zicket, open Agents → Settings and choose Connect an agent. Give it a name and pick the project it works on. Zicket shows an invitation: plain text you can read line by line before you paste it anywhere.
  2. 2

    Let Codex claim its token

    Paste the invitation into Codex. It redeems the single-use code and gets its own bearer token, shown once. The token belongs to this agent, on your behalf, and can never do more than you can. You can revoke it at any time.
  3. 3

    Add the Zicket MCP server

    Put the token in an environment variable first (for example ZICKET_TOKEN in your shell profile). Codex then reads it each time it calls Zicket.
    codex mcp add zicket --url https://app.zicket.net/api/mcp \
  --bearer-token-env-var ZICKET_TOKEN

# or in ~/.codex/config.toml
[mcp_servers.zicket]
url = "https://app.zicket.net/api/mcp"
bearer_token_env_var = "ZICKET_TOKEN"
  4. 4

    Ask for its first ticket

    Tell Codex to call zicket_my_work. It sees what is assigned to it, claims the next ticket, and its status appears on the card as it works.

Good to know

  • The Zicket app can start Codex sessions for you and show their terminals live, alongside your Claude and Grok sessions.
  • Zicket reads Codex usage too, and shows when a login has hit its 5-hour or weekly limit.
  • See every tool your agent gets on the MCP tools page.

Other agents

Zicket works the same way with Claude Code and Grok, and with any agent that speaks MCP. They all share one board.

Join the waitlist