Skip to content
Docs · Tools and scopes

MCP server

What a connected tool can do

MCP tools for tickets, chat and workspace settings: the next ticket, briefs, your chat, messages as you, teams, boards, channels, rooms. Scopes and limits.

Updated

On this page

A connected tool acts as you, in the one workspace you picked, with the scopes you approved, and never more than your role allows.

You don’t call these tools yourself: you ask your tool in plain words, and it picks the tools.

Tickets

Tool What it does
whoami You, the workspace, your role, what the connection may do, and how many unread notifications you have
list_boards The workspace’s boards, with their ids, teams, columns, sprints and backlog line. Archived boards only when asked (includeArchived)
get_board One board: its columns left to right (ids, names, review columns, how many cards), whether the backlog list is on (with its line and the cards above it), and the running sprint with its points
search_tickets Find tickets by board, column (id or name, or backlog), sprint (current, backlog or a number), assignee (me for yours, none for unassigned), words (q: a ticket id like YOM-12 matches exactly, old ids too; other words the title, label or description) or doneSince. In board order, Done newest first. One page at a time: nextCursor gets the next, and total counts every match, so your tool can go through thousands of tickets
next_ticket What to work on next: the top unblocked ticket that’s yours or nobody’s: started work first, then the first column (To do), then the backlog, each in board order. Review columns and Done are left out. Optionally per board. It doesn’t claim
get_ticket One ticket, like YOM-142 (any id it had before works too: an old TKT-142, or its id on a board it left): its description (the brief and its “Done when” checklist), links, what blocks it and what it blocks, and recent activity and comments (20 at a time, with a cursor for older ones)
create_ticket Add a ticket at the bottom of the first column (the backlog list when the board has it on), or of a column you name: title, board (needed unless the workspace has exactly one active board), and optionally description, column, points (0 to 100 in steps of 0.1, like 0.5; default 1), label and assignee (me assigns it to you)
update_ticket Change a ticket’s title, description, column (id or name; backlog for the backlog list), place in its column (after another ticket, or top / bottom), points, label, board or assignee. Fields you leave out stay as they are
set_backlog_line Move the backlog line: after the first N cards (count), after the cards whose points add up closest to a number (points), or right after a ticket (after)
move_above_line Move every card above the backlog line to the board’s first column, in order (into the sprint, with sprints on). Needs the backlog list on
start_sprint Start the next sprint (none running), for the board’s length or lengthDays: the cards above the backlog line join it, with any carried over. It can start empty
end_sprint End the running sprint, without starting the next: cards that aren’t done stay on the board for the next sprint, or go back to the backlog
move_to_sprint, move_to_backlog Put tickets (by key, in order) into the running sprint, or back in the backlog just below the line
claim_ticket Assign a ticket to you and move it to the board’s working column (In progress). A blocked ticket is still claimed, with a warning naming its open blockers
comment_on_ticket Add a comment (markdown) to a ticket’s activity, as you, marked “via” the tool
get_agent_activity What a person’s AI did: live sessions, their latest past sessions, AI teammates they manage, merge and pull requests to review, and their ticket work
review_ticket Approve a ticket an agent worked on, or request changes with a note (sends a ticket in review back to work)
set_blocked_by Say a ticket waits on another (add) or no longer does (remove). No loops, and not on itself
add_link Attach a link: kind pr (a merge or pull request, GitLab or GitHub), branch, release, doc or other, an https:// address and an optional title
remove_link Remove a link by its id or address
delete_ticket Delete a ticket for good, with its comments and activity. Tickets that waited on it stop waiting. It can’t be undone, so ask your tool only when you mean it

Each board has its own columns (a new board: backlog, in_progress, review, done); get_board lists them, and tools take a column by id or name. The last column is Done. A board with the backlog list on has no Backlog column: backlog is then the ranked list at its left, where new tickets wait. Lists come back in board order: the backlog, then column by column, the top first (Done newest first). A board is named by its id or its name, in any case ("Sprint 16", "sprint 16" or platform-sprint), and every ticket says which board it’s on. A new ticket needs a board unless the workspace has exactly one active board; otherwise the tool is told which boards to pick from (“Pick a board: …”). New tickets and moves can’t go onto an archived board; tickets already on one can still be edited.

  • “Put a ticket on the ScreenApp board for the login screen.” → create_ticket with board: "ScreenApp".

  • “Move YOM-141 to Sprint 16.” → update_ticket with board: "Sprint 16".

  • “What should I work on next?” → next_ticket, then get_ticket to read the brief.

  • “What’s on my plate?” → search_tickets with assignee: "me".

  • “Pick up YOM-142.” → claim_ticket with id: "YOM-142".

  • “Make a ticket for the flaky login test, with a short brief and a done-when list, and give it to me.” → create_ticket with title, description, assignee: "me".

  • “Note on YOM-142 that the fix is in refundAmount().” → comment_on_ticket.

  • “Attach the MR and move it to review.” → add_link with kind: "pr", then update_ticket with column: "review".

  • “YOM-139 can’t start until YOM-133 is done.” → set_blocked_by with id: "YOM-139", blocker: "YOM-133".

  • “Groom the Platform backlog: most urgent first, about 20 points above the line.” → search_tickets with sprint: "backlog", update_ticket with after for each, then set_backlog_line with points: 20 (the reply: “Up next: 4 cards, 19 pts (…)”).

  • “Turn on the backlog list for Sprint 16.” → update_board with backlog: true (the Backlog column’s cards become the list).

  • “Move what’s above the line onto the board.” → move_above_line.

  • “End the sprint; unfinished goes back to the backlog.” → end_sprint with unfinished: "backlog" (the reply: “Sprint 16 ended: 7 cards done (18 pts). 2 cards went back to the backlog. No sprint is running: start_sprint starts Sprint 17 with what’s above the backlog line.”).

  • “Start the next sprint, one week this time.” → start_sprint with lengthDays: 7 (the reply: “Sprint 17 started: 5 cards (18.5 pts; 3 from above the line, 2 carried over). It ends …”).

  • “Put YOM-12 and YOM-14 in the sprint.” → move_to_sprint with ids: ["YOM-12", "YOM-14"].

Descriptions and comments can refer to other tickets by key (YOM-12), channels as #eng and people as @Priya: they’re stored as links, so they keep working after renames, and a mentioned ticket gets a “Mentioned in” line. get_ticket writes them back as typed and lists them in refs, so text your tool reads and sends back keeps its links.

claim_ticket is refused while an agent holds a live lease on the ticket (leases). Moving a ticket into a review column tells a person it’s ready: the manager of the agent it’s assigned to, or you when your tool moved your own ticket (review).

Chat

Tool What it does
list_people Everyone in the workspace, people and AI teammates, with ids, status, who each agent reports to, and when people were last seen (unless either of you turned that off)
list_conversations Your channels, DMs and group DMs, most recent first, with unread counts and what each notifies you about (all messages, mentions only or muted). Can add public channels you aren’t in
read_messages Recent messages in a channel or DM, oldest first, 30 at a time (up to 100), with a cursor for older ones. Shared files are listed by name, type and size, never their contents. Mentions read as @Priya or @platform, channels as #eng (“private channel” for one you aren’t in) and tickets by key; each message lists who it mentions and everything it refers to (refs: people, teams, channels and tickets, with titles and links). Reading the newest page marks the conversation read for you (never for anyone else), and your own messages show their receipt: sent, delivered or read, and who read them
read_thread A thread’s first message and its replies
search_messages Messages containing all your words, in the conversations you can read
send_message Post as you to a channel, or to a person or a few people (the DM is opened if it doesn’t exist yet). Write @Priya or @platform to mention someone or a team, #eng and ticket keys like YOM-12 to link them
reply_in_thread Reply in a thread as you
edit_message Change the text of one of your own messages; people see it marked “(edited)”. Newly mentioned people are told
delete_message Delete one of your own messages. It stays in place as “Message deleted” for everyone; its text, files and reactions are gone for good
set_conversation_notifications Change what a conversation you’re in notifies you about: all messages, mentions only, mute (for some minutes, or until you unmute) or back to the default. Only for you
list_notifications Your notifications, like the bell: missed rings, people who stopped by your desk, mentions, DMs, thread replies, approvals and tickets ready for review, newest first, for 30 days. Only unread, some kinds or since a time if you like. Each one names who, the conversation (#design, or people for a DM), the message or thread, the ticket key or approval, and the tool to answer with. Message text follows your “Show message text” setting. Reading them doesn’t mark them read
mark_notifications_read Mark notifications read: some, all, or everything up to a time. Yomenie updates the bell at once
add_reaction / remove_reaction React to a message with one emoji as you, or take your reaction back. Messages from read_messages and read_thread list their reactions: the emoji, who reacted and whether you did

Your tool can name a channel as #general and a person by name, Priya, or several, Priya, Marcus for a group DM. Names match whatever the case or accents; if two people share a name, the tool is told to use an id instead.

  • “Catch me up on chat.” → list_conversations with only unread, then read_messages for each.
  • “What did I miss?” → list_notifications with unread: true, then the tool each one names (send_message to answer a missed ring, read_thread, get_ticket), then mark_notifications_read.
  • “What did Marcus say about the release?” → search_messages with release, or read_messages with conversation: "Marcus".
  • “Tell #eng the deploy is green.” → send_message with to: "#eng".
  • “Ask Priya if she has five minutes.” → send_message with to: "Priya".
  • “Tell #eng that @platform should review the release notes.” → send_message with to: "#eng" and @platform in the text: everyone on the Platform team who can read #eng is notified.
  • “Reply in that thread that the fix is out.” → reply_in_thread.
  • “Tick Priya’s message in #eng so she knows it’s done.” → add_reaction with emoji: "✅".
  • “Mute #random for an hour.” → set_conversation_notifications with notify: "mute", minutes: 60.

Only what you can read. A connected tool reads exactly what you could read in Yomenie: your channels and DMs, and public channels. It can’t see private channels you aren’t in (it’s told no such channel exists) or anyone else’s DMs, whatever your role. Reading through a tool doesn’t mark messages read in Yomenie.

Sent as you, marked. Messages are posted under your name, with a quiet “via Claude Code” (or the tool’s name) next to it, so people can tell. They follow the same rules as a message you type: channels where only owners and admins post, archived channels and DMs you aren’t in refuse it, and posting in a public channel joins it. People get the same notifications as for a message you type (DMs, thread replies and mentions). Messages aren’t added to the audit log, just as yours aren’t.

Reactions need “Send messages as you” too, and follow the rule in Yomenie: anywhere you’re a member, also in channels where only owners and admins post; never in archived channels or channels you haven’t joined. They’re marked with the tool’s name where they’re stored, don’t notify anyone and aren’t audited.

At most 20 messages a minute go out through connected apps for you, all your tools together. After that the tool is told to wait a minute. Messages you type in Yomenie don’t count.

Scoreboards

Tool What it does
list_metrics The scoreboard’s metrics you may see: value, source, the board a counted metric counts from, which screens show it, and the key tools push to
list_scoreboards The screens on the floor: where each hangs, its team and its metrics in order
list_scoreboard_spots The wall spots where a screen can hang, free or taken
create_metric Add a metric: name, key, format, source (push, board, by hand), a board to count from, reset, timezone, target, who can see it, celebrations, a short label for the screen
update_metric Change any of those. Fields you leave out stay as they are
delete_metric Delete a metric and its history; it leaves every screen
set_metric_value Set a by-hand metric’s value, with an optional note. Pushed metrics take values from the push URL, counted ones count themselves
create_scoreboard Put a screen on a free spot, for a team or the whole workspace, with up to three metrics in order
update_scoreboard Rename a screen, move it to a free spot, change its team, or set its metrics in order
delete_scoreboard Take a screen down; its spot is plain wall again

Any connection reads the metrics and screens you may see. Changing them needs Manage workspace settings and the owner or admin role, exactly as in Settings → Scoreboard, with the same refusals (“Only metrics everyone can see can go on a screen”). Making or regenerating the push URL isn’t a tool: it asks you to confirm it’s you, so it stays in Settings.

  • “Put releases today and tickets in review on the Hall screen.” → list_metrics, then update_scoreboard with scoreboard: "Hall", metrics: ["releases_today", "in_review"].
  • “Add a screen over the Platform desks counting Sprint 16’s done tickets this week.” → create_metric with source: "board", boardMetric: "tickets_done_week", boardId: "platform-sprint", then create_scoreboard with spot: "platform".
  • “Set MRR to 48,200.” → set_metric_value with metric: "mrr".

Agent helpers

Your tool’s session and its sub-agents show on the floor as agent helpers. The session is automatic: any call makes it appear, one per window. Sub-agents are registered by the tool.

Tool What it does
start_helper Register a sub-agent: a role, a short task and the ticket if any. Returns its id, name and character
update_helper Change a sub-agent’s task or ticket, or (leaving out helper) the session’s own. waiting marks it waiting for you with the question it asked: you get a “Pip is waiting for you” notification, and it clears on the helper’s next call
end_helper The sub-agent is done: it leaves the floor with a puff. An optional outcome is kept in your session history, which only you see
list_helpers Everyone’s sessions and sub-agents right now, as the floor shows them
list_agent_sessions Someone’s past and running sessions (yours by default, or by name): the app, when, the ticket, each sub-agent with its role, task and how it ended, and the tools each called on which tickets and channels. Kept 90 days
set_floor_helpers Your switch “Show my agents on the floor”

Every other tool takes an optional helper id: the call counts as that sub-agent’s activity and is recorded as “Claude Code (Pip)” wherever the tool’s name is shown, such as a ticket’s timeline or a message’s “via”.

No extra scope: any connection manages its own session’s helpers, never anyone else’s. At most 8 sub-agents per session and 30 helper calls a minute for you. Everyone in the workspace sees name, role and task, so tasks are cut to 80 characters and tokens and emails are removed.

Problems with Yomenie

Found a bug in Yomenie itself, or something that didn’t work? Your tool can send it to the Yomenie team for you, like Report a problem in the app. Any connection, in any workspace, with no extra scope.

Tool What it does
report_problem Sends what went wrong in your words, the kind of problem (call, video, screen share, floor, chat or something else) and, if you name them, the conversation and ticket it’s about. Only their names and keys go with it, never messages: a public channel by name, a private one as “a private channel”, a DM as “a direct message”. Returns a reference like R-7KQ2MX. Up to 10 reports an hour, the same as the app
add_report_note Adds to a report you sent (from the app or your tool) within a day: steps, what changed, whether it happens again
  • “That board bug again: report it to Yomenie.” → report_problem with what happened, then it tells you the reference.

Privacy says who reads reports and what goes with them.

Workspace settings

What owners and admins change in Settings and in a channel’s details, a connected tool can change for them with Manage workspace settings. Same rules, same refusals, and each change is in the audit log as theirs, “via” the tool.

Tool What it does Needs
list_teams Teams, who is on each (people and agents), their boards and their channel any connection
create_team, rename_team, delete_team Make, rename or delete a team. A new team gets its channel, # and its name as a slug, unless channel: false; if that channel already exists the tool says so (link it instead, or pick another name). Renaming a team renames its channel. A deleted team’s boards become workspace-wide, with their tickets, and its channel is archived Manage workspace settings, owner or admin
link_team_channel, unlink_team_channel Give a team its channel: link an existing public channel (renamed to the team’s name only with rename: true), or create it when no channel is given; or unlink it (the channel stays) Manage workspace settings, owner or admin
add_to_team, remove_from_team Put people or agents on a team (by name or id), or take them off Manage workspace settings, owner or admin. Joining or leaving yourself ("me") is open to everyone, with Change tickets
create_board, update_board Make a board for a team or the whole workspace (with an optional key, like ISS; left out, it is suggested from the name and the reply says which); rename it, change its key (its tickets keep their numbers, old ids keep working), description or team; change its columns (the whole list left to right: keep one by id, add one by name, leave one out to remove it, its cards moving left unless moveTo says where; review: true makes a review column), turn the ranked backlog list on or off (backlog: true takes over a column named Backlog, false puts it back as a first column) or turn sprints on or off (sprints: { on, lengthDays }; on turns the backlog list on too) Manage workspace settings, owner or admin
archive_board, unarchive_board Archive a board (its tickets stay, readable) or bring it back Manage workspace settings, owner or admin
update_channel A channel’s name, topic, description, who can post, private or public. Changing visibility says what it means. Renaming a team’s channel renames the team, and a team’s channel stays public Topic and description: any member of the channel, with Send messages as you. The rest: Manage workspace settings, owner or admin
archive_channel, unarchive_channel Archive a channel or bring it back. #general stays Manage workspace settings, owner or admin
list_channel_members Who is in a channel Read your chat
add_channel_members, remove_channel_member Add people and agents, remove someone, or leave ("me") Private channel: any member adds, with Send messages as you. Public channel and removing: Manage workspace settings, owner or admin
list_rooms, update_room Room settings: name, video, lockable, capacity, agents, and purpose (restroom, phone booths, quiet room, storage, kitchenette; list_rooms says which each room can take, "original" puts its furniture back). A field set to null goes back to its default Reading: any connection. Changing: Manage workspace settings, owner or admin
list_room_people Who is on the floor right now, room by room: people and AI teammates, whose mic, camera and screen share are on, and raised hands in the order they go up (so “who is in Standup and whose hand is up?” is one call). Pass a room for just that one. It only reads: it never turns anyone’s mic or camera on Any connection
reset_floor Every room back to its original furniture; with all, every room setting too Manage workspace settings, owner or admin
list_webhooks, revoke_webhook A channel’s incoming webhooks (never their addresses), and revoking one Reading: Read your chat. Revoking: Manage workspace settings, owner or admin
list_git_hooks, revoke_git_hook The workspace’s git webhooks (never their addresses), and revoking one Reading: any connection. Revoking: Manage workspace settings, owner or admin
list_approvals, decide_approval Agents’ pending requests you may decide, and approving or denying one Manage workspace settings, owner or admin
read_audit The audit log, newest first, by action or agent Manage workspace settings, owner or admin
list_problem_reports, get_problem_report Problem reports people sent (by hand, or when a call went wrong), and one report with what they wrote and the full diagnostics. Screenshots are metadata only The people who read reports in Yomenie (the support team), connected to that workspace, with Manage workspace settings
list_sign_in_attempts Who asked for a sign-in, join or sign-up email, whether it was sent and whether they got in, with how each mail provider did over 7 and 30 days. No links or codes The same people as problem reports
get_call_stats, list_failed_calls How many calls work across every workspace (sound within 10 s both ways, no long silence, no problem report): counts, success %, time to first sound, grouped by day, version, size, browser, how it started or workspace, plus the workspace counts; and the failed calls with the pairs that failed and their reports The same people as problem reports

Teams, boards and rooms are named by id or name, in any case. A member’s own rights that come from more than their role, like renaming a channel they made or deciding their own agent’s approvals, need Manage workspace settings too, which members can’t give, so they do those in Yomenie.

  • “Rename the Sprint 16 board to Yomenie.” → update_board with board: "Sprint 16", name: "Yomenie".
  • “Make an Issues board with the key BUG.” → create_board with name: "Issues", key: "BUG".
  • “Add a QA column before Review on Sprint 16, as a review column.” → get_board, then update_board with the whole columns list ({ "name": "QA", "review": true } where it goes).
  • “Turn on two-week sprints for the Platform board.” → update_board with sprints: { on: true, lengthDays: 14 } (the reply: “Sprints are on: Sprint 1 runs until …”).
  • “Change the ScreenApp board’s key to SA.” → update_board with key: "SA" (SCR-4 becomes SA-4; SCR-4 still works).
  • “Make a ScreenApp team with Aiko and Iris, and a board for it.” → create_team, then create_board with team: "ScreenApp".
  • “Make Meeting room 1 a video meeting room for six.” → update_room with video: "meeting", capacity: 6.
  • “Turn Focus booth B into a restroom.” → update_room with room: "Focus booth B", purpose: "restroom".
  • “Put the office back the way it was.” → reset_floor.
  • “Archive #old-launch.” → archive_channel.

Scopes

Scope Shown as Allows
tickets:read See boards and tickets (always) List boards, search and read tickets, their activity and next_ticket
tickets:write Change tickets Create, edit, move, assign and claim tickets, comment, set blockers and links, as you
chat:read Read your chat List people and your conversations, read messages and threads, search, read your notifications (without it, only ticket notifications)
chat:write Send messages as you (unticked until you tick it) Post in channels, DMs and threads under your name, marked “via” the tool; mark your notifications read
workspace:admin Manage workspace settings (owners and admins only, unticked until you tick it) What your owner or admin role lets you manage in Yomenie. Teams, boards, channels, rooms, webhooks, approvals, the audit log and the scoreboards (above)

Every tool is listed for every connection. Without the scope, or if your role doesn’t allow it, a tool refuses with a plain reason your tool shows you (naming the scope to allow). Sending doesn’t need “Read your chat”, so a tool can post a message for you without reading anything.

“Manage workspace settings” is offered only when you’re an owner or admin of the workspace you connect, and starts unticked. If you tick it for a workspace where you’re a member, it isn’t granted. Even with it, a tool never gets more than your role.

Connected before chat or the workspace tools existed? A connection keeps the scopes you approved. To add chat or “Manage workspace settings”, connect again (in Claude Code: /mcp, pick yomenie, Authenticate, or remove and add the server) and tick what you want. Then revoke the old connection in Settings → Connected apps.

What it can never do

Whatever you approve and whatever your role, a connected app can never:

  • change who the owners are, or the workspace’s own settings,
  • change people, roles, join links or the invite policy,
  • do anything that asks you to confirm it’s you: connections, credentials, grants, deny rules, agent keys, making a webhook or a new webhook address, or the scoreboard’s push URL.

Those stay in Yomenie, where you do them yourself. People, roles and agents (creating them, their access) have no tools yet: they’re in Yomenie too.

Yours in the audit log

Every ticket and settings change made through a connected app is in the workspace’s audit log with you as the actor and the app’s name beside it: “priya via Claude Code” (ticket changes are on the ticket’s activity too, marked “via” the tool). Comments stay on the ticket, not in the audit log. Boards update for everyone as it happens, exactly as for any other change.

Setting your status from a connected tool isn’t built yet. Coming: More MCP tools: status and CI tokens, on the roadmap