Skip to content
Docs · Connect your tool

MCP server

MCP server: connect Claude Code, Codex and others

Yomenie's MCP server lets Claude Code, Codex, Cursor and other tools work with your tickets and chat as you. A browser sign-in, no tokens to copy.

Updated

On this page

Yomenie runs an MCP server at https://yomenie.us/mcp. MCP (Model Context Protocol) is how AI coding tools like Claude Code and Codex talk to other services. Connect one, and it can work as you: find work, create tickets, move them along and claim them, catch you up on chat and send messages for you.

You sign in with your browser, like signing in to Yomenie itself. Nobody copies a token.

Yomenie is built for AI-native teams: the idea is that most tasks are done from your tool, and the same tool updates the ticket and tells the team, so you don’t retype it afterwards. Work through your AI agent walks through that loop with things to ask.

Connect Claude Code

Install the Yomenie plugin for Claude Code: it connects Claude Code, shows its sub-agents on the floor beside you and brings a short skill. In Claude Code, type these one after the other:

/plugin marketplace add https://yomenie.us/claude-code/marketplace.json
/plugin install yo@yomenie

Then run /mcp, pick plugin:yo:yomenie and choose Authenticate. Your browser opens for the sign-in. Yomenie shows the same steps, with Copy buttons, under Settings → Connected apps.

Connected before with claude mcp add? Remove that one, so Claude Code doesn’t have two Yomenie connections:

claude mcp remove yomenie

Without the plugin

To add only the MCP server (no sub-agents on the floor, no skill), run this in your terminal:

claude mcp add --transport http yomenie https://yomenie.us/mcp

Then, in Claude Code, run /mcp, pick yomenie and choose Authenticate. By default claude mcp add saves the server for the current project only, for you; add --scope user to have it in every project. See Claude Code’s MCP docs for the options.

Connect Codex

Add the server to Codex’s ~/.codex/config.toml:

[mcp_servers.yomenie]
url = "https://yomenie.us/mcp"

Then sign in:

codex mcp login yomenie

Your browser opens for the sign-in. Codex’s MCP commands change from release to release, so check Codex’s MCP docs if this doesn’t match your version.

Cursor, VS Code, OpenClaw and others

Add a remote MCP server (Streamable HTTP) with the URL https://yomenie.us/mcp. In OpenClaw, that’s a server with transport: "streamable-http" and auth: "oauth", then openclaw mcp login yomenie (OpenClaw’s MCP docs). Clients that support MCP authorization, that is OAuth sign-in with dynamic client registration, can connect. Your client opens the browser when it needs you to sign in.

In the browser:

  1. Sign in with your email link or passkey, if you aren’t signed in already. You come straight back to the request.
  2. Check the app. The page says “Connect app to Yomenie?” and shows where it sends you back, for example “Sends you back to 127.0.0.1” for a tool on your computer. That address is the real check: an app’s name is whatever it calls itself.
  3. Pick one workspace. A connection works in one workspace only.
  4. Choose what it may do. “See boards and tickets” is always on. Untick “Change tickets” for a read-only connection. “Read your chat” lets it read what you can read; “Send messages as you” starts unticked, so tick it if you want the tool to post for you (its messages show “via” its name). Owners and admins also see “Manage workspace settings”, unticked: tick it to let the tool manage what your role manages, today the scoreboards.
  5. Press Approve (or Deny).

“It will act as you in one workspace, with only what you allow here and never more than your role. It can’t change owners or workspace settings, or anything that asks you to confirm it’s you, like keys and credentials.”

The request lasts 10 minutes and works once. Opening the page never approves anything by itself: only your Approve does.

A workspace that requires a passkey connects an app only when you signed in with a passkey, or press Confirm with your passkey on this page. Your tool never sees the passkey: it gets tokens. When an owner turns the setting on, apps that weren’t approved with a passkey are disconnected, so connect again and use your passkey. More in Require a passkey for everyone.

Next