For developers
Work Mendaro tickets with Codex.
The same MCP server that powers the Claude Code integration registers in Codex with a few lines of config — same tools, same permissions, your agent of choice.
Point Codex at Mendaro once, then ask it to work a ticket: it loads the full context — the conversation, screenshots, recent commits — plans a fix, and can comment, set status, and link the pull request when it ships.
- More than 20 RBAC-scoped tools that mirror the web permissions
- Read and write: comment, set status, assign, snooze, link a PR
- Server-side GitHub reads, so no local clone is needed
> Work on Mendaro ticket 4821 via the mendaro MCP tools. Pulling ticket 4821 with full context...
Implement: Solve this ticket
No skill installed yet?
Copy a complete markdown brief instead — ticket, conversation, screenshots, recent commits, all inline.
Set up in a few lines of config
# ~/.codex/config.toml
[mcp_servers.mendaro]
url = "https://<your-mendaro-api>/mcp"
bearer_token_env_var = "MENDARO_TOKEN"- 1
Create an API token
Generate a token under Profile → API tokens in Mendaro. It is shown once and stored server-side only as a hash.
- 2
Register the MCP server
Add the mcp_servers.mendaro block to ~/.codex/config.toml — the in-app setup dialog generates the exact block for your workspace, with your API endpoint filled in.
- 3
Hand Codex a ticket
Export MENDARO_TOKEN in your shell, then ask Codex to work on a ticket by id: it loads the report with full context through the MCP tools and gets to work.
Using Claude Code?
The Claude Code integration goes further: a plugin, skills like /mendaro-work-on, and a one-command install.
Learn moreQuestions, answered.
Is this the same MCP server as the Claude Code integration?
Yes — one server, every MCP-compatible agent. Codex, Claude Code, and anything else that speaks the Model Context Protocol get the same 20-plus RBAC-scoped tools with the same permissions.
What can Codex do with a ticket?
Read the full ticket with its conversation, screenshots, and linked commits; search and list tickets; comment; set status; assign; snooze; and link a pull request or commit — everything your account may do in the web app.
How is the API token handled?
The token lives in an environment variable (MENDARO_TOKEN), never in the config file in plaintext. Server-side, Mendaro stores only its SHA-256 hash, and you can revoke it at any time from Profile → API tokens.