MCP server
Revoke, troubleshoot and develop locally
Revoke a connected app in Settings, understand token lifetimes, fix common MCP errors, and connect to a self-hosted or local Yomenie.
Updated
Revoke
Open Settings → Connected apps (the gear at the bottom of the left rail, or yomenie.us/app/<workspace>/settings/apps). Each connection shows the app’s name, the workspace, what it may do (“See boards and tickets”, “Change tickets”, “Read your chat”, “Send messages as you”), when it was connected and when it was last used.
Revoke stops it at once: its access and refresh tokens stop working on the next request. Only you see your connected apps.
Connections also stop when:
- you’re removed from the workspace, or you leave it, or
- the connection isn’t used for 30 days.
Connecting and revoking are listed in your security log.
How long it stays connected
Your tool gets an access token that lasts an hour and refreshes itself. Each refresh starts a new 30-day window, so a tool you use regularly stays connected. After 30 days without use, it asks you to sign in again.
Tokens are stored only as hashes. They start with ym_at_ (access) and ym_rt_ (refresh), so secret scanners can spot one that leaks; a leaked refresh token that’s used twice revokes the whole connection.
Troubleshooting
The tool says it needs to authenticate, or gets “401”. The connection was revoked, expired, or you were removed from the workspace. Sign in again: in Claude Code, /mcp, pick yomenie, Authenticate. If your workspace started requiring a passkey, connections not approved with one were disconnected: connect again and use your passkey.
“That request has expired.” The browser page waited more than 10 minutes, or was already used. Start again from the tool.
“This app can’t connect.” The app sent something Yomenie doesn’t accept, usually a return address it didn’t register. Yomenie accepts https addresses, and http only on 127.0.0.1, localhost or [::1]. Custom schemes such as cursor:// aren’t accepted yet. Try connecting again from the app; if it keeps happening, the app’s MCP setup may be off.
“App wasn’t given “Change tickets”” or “You can’t change tickets in this workspace.” The connection is read-only, or your role can’t change tickets. To allow changes, revoke it and connect again with “Change tickets” ticked.
“App wasn’t given “Manage workspace settings”“. The connection can’t change metrics or screens. If you’re an owner or admin, connect again and tick “Manage workspace settings”, then revoke the old connection here.
“App wasn’t given permission to read your chat” (or “to send messages as you”). The connection was made without that scope, for example before chat tools existed. Connect again (in Claude Code: /mcp, pick yomenie, Authenticate) and tick “Read your chat” and “Send messages as you”, then revoke the old connection here. A connection never gains scopes by itself.
“You are not in this conversation” or “No channel #… that you can see.” The tool asked for a private channel you aren’t in or someone else’s DM. It can only read and post where you can.
“You’ve sent 20 messages through connected apps in the last minute.” The limit for messages sent by tools for you. Wait a minute; messages you type in Yomenie aren’t limited.
“No board …” or “No ticket … in this workspace.” The tool used an id from another workspace. A connection sees only the workspace you picked; connect again to use another.
The wrong workspace. Revoke the connection and connect again, picking the right one. You can have a connection per workspace.
Self-hosted servers
On your own server, use your domain: https://<your-domain>/mcp. The sign-in works the same way, through your server’s Worker (self-hosting).
Local development
Plain pnpm dev has no sign-in. The API answers MCP directly at http://localhost:8787/mcp, acting as the member in the x-yomenie-member header:
claude mcp add --transport http yomenie-dev http://localhost:8787/mcp --header "x-yomenie-member: priya"
Optional headers:
| Header | Does |
|---|---|
x-yomenie-dev-scopes: tickets:read,chat:read |
Only these scopes, comma-separated (default: all scopes) |
x-yomenie-dev-client: <name> |
The name in the audit log and on sent messages (default “Local dev”) |
The production setup ignores these headers. To try the full sign-in flow locally, run the whole stack under wrangler dev and connect to http://localhost:<port>/mcp.