Kangram

Measured conclusion: Deep-tested. L2 outcome: tools_ok.

Task & board management for AI agents + humans. Kanban, comments, digests via MCP.

Add to your agent

Copy this into your MCP client config:

{
  "mcpServers": {
    "Kangram": {
      "url": "https://kangram.app/mcp",
      "transport": "streamable-http"
    }
  }
}

Measured tools (61)

• list_boards

  Use this command to discover boards before creating or filtering tasks.

  Parameters:

  • code — string — Filter boards by board code (3-character code, exact match, case-insensitive).
  • limit — integer — Optional max number of boards to return.
  • title — string — Filter boards by title (starts-with, case-insensitive).
  • only_archived — boolean — Return only archived boards.
  • include_archived — boolean — Include archived boards in result.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• create_board

  Use this command to initialize a board and its default status workflow.

  Parameters:

  • title — string — Optional board title.
  • timezone — string — Optional board timezone (e.g. Australia/Melbourne).
  • group_chat_id — integer — Optional target group chat id. Defaults to active context group chat.
  • namespace_slug — string — Optional target namespace slug (e.g. 'kangram', 'exemplarov'). Creates the board in that namespace instead of the personal one. Use list_namespaces to discover available slugs.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• update_board

  Use this to edit board metadata (title, code) and/or the board-level agent prompt. The prompt is the markdown instructions an agent reads when operating on this board (stored as the root file "AGENTS.md"). Pass only the fields you want to change; omitted fields are left untouched. Pass an empty string as prompt to clear the prompt.

  Parameters:

  • board_id (required) — integer — Board ID to update.
  • code — string — New board code (3 letters or digits A-Z/0-9, unique within the namespace). Omit to leave unchanged.
  • title — string — New board title. Omit to leave unchanged.
  • prompt — string — Markdown agent prompt for this board (stored as the root "AGENTS.md" file). Omit to leave unchanged; pass an empty string to clear. May include YAML frontmatter.
  • visibility — string — Set board visibility. 'private' (default) = members-only; 'public' = anyone with the link can view the board read-only (no account required). Owner/admin only. Omit to leave unchanged.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• get_board_by_namespace

  Canonical lookup for a board. Resolves the namespace by slug, then the board by its 3-character code within that namespace. Membership-gated: returns an error for unknown namespace, unknown board, or non-member (indistinguishable).

  Parameters:

  • namespace_slug (required) — string — Owner namespace slug (e.g. a username).
  • board_code (required) — string — 3-character board code (case-insensitive; legacy codes may contain Unicode letters or digits).

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• archive_board

  Use this to hide a board from active workflows without deleting it.

  Parameters:

  • board_id (required) — integer — Board ID to archive.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• restore_board

  Use this to recover a previously archived board.

  Parameters:

  • board_id (required) — integer — Board ID to restore.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• clone_board

  Clone a board into a new board, copying the workflow not the data: statuses + board files (the prompt / agent instructions) + board title. Excludes tasks, comments, and members. The caller becomes the owner of the fresh board. The new board is created in the caller's personal namespace with a fresh unique code. Authorize: caller needs read access to the source board — a board member OR any viewer when the board is public (public boards are forkable by anyone). Authorization is enforced imperatively in execute.

  Parameters:

  • source_board_id (required) — integer — Board ID to clone the workflow from.
  • code — string — Optional 3-character code (A-Z/0-9) for the new board; must be unique in your namespace. Auto-generated if omitted.
  • title — string — Optional title for the new board. Defaults to "<source title> (copy)".

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• create_task

  Use this to add a task. Provide boardId for deterministic routing; otherwise active board is used.

  Parameters:

  • title (required) — string — Short task title. Keep it clear and action-oriented.
  • tags — array — Optional list of tags.
  • status — string — Optional initial status name for the task.
  • assignee — string — Assignee username without @.
  • board_id — integer — Board ID where the task should be created.
  • priority — string — Optional task priority: critical, major, normal, or low.
  • description — string — Optional longer task details.
  • parent_board_id — integer — Board ID of the parent task. Defaults to board_id if omitted.
  • telegram_chat_id — integer — Optional Telegram chat id for message-task linking.
  • parent_task_number — integer — Optional parent task number to create a subtask. Use with parent_board_id or board_id.
  • telegram_message_id — integer — Optional Telegram message id for message-task linking.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• get_task

  Use this to read one task including its description, deadline, tags, status, and assignee.

  Parameters:

  • task_number (required) — integer — Task number in board scope.
  • board_id (required) — integer — Board ID where the task belongs.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• list_tasks

  Use this to inspect task backlog by board, assignee, status, priority, tags, title substring, creation date range, and deletion state.

  Parameters:

  • board_id (required) — integer — Board ID to list tasks from.
  • tags — Optional list of tags to filter by. Tasks matching ANY of the specified tags are returned.
  • limit — integer — Optional max number of tasks to return.
  • status — string — Optional status name filter.
  • assignee — string — Optional assignee username filter (without @).
  • priority — Optional priority filter: critical, major, normal, low (aliases: high→major, middle→normal).
  • created_to — string — Optional inclusive upper bound on createdAt as YYYY-MM-DD.
  • created_from — string — Optional inclusive lower bound on createdAt as YYYY-MM-DD.
  • only_deleted — boolean — Return only deleted tasks.
  • title_contains — string — Optional case-insensitive substring match on task title.
  • include_deleted — boolean — Include deleted tasks in the result.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• list_board_tags

  Use this to discover which tags already exist on a board before filtering with list_tasks. Returns unique tag strings (first-seen casing), sorted case-insensitively.

  Parameters:

  • board_id (required) — integer — Board ID to list tags from.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• update_task

  Use this to edit task title/description/deadline/tags/assignee/status.

  Parameters:

  • task_number (required) — integer — Task number in board scope.
  • board_id (required) — integer — Board ID where the task belongs.
  • tags — array — Replace task tags list.
  • title — string — New title.
  • status — string — Set status by name.
  • assignee — string — Assign by username (without @).
  • deadline — string — New deadline string.
  • priority — string — Set priority: critical, major, normal, or low.
  • description — string — New description.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• transition_task_status

  Use this for explicit status moves while keeping other fields unchanged.

  Parameters:

  • task_number (required) — integer — Task number in board scope.
  • board_id (required) — integer — Board ID where the task belongs.
  • status (required) — string — Target status name.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• delete_task

  Use this to mark a task as deleted without permanent removal.

  Parameters:

  • task_number (required) — integer — Task number in board scope.
  • board_id (required) — integer — Board ID where the task belongs.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• move_task

  Use this to transfer a task between boards. The task gets a new number in the target board. Status is reset to target board's default if the current status doesn't exist there.

  Parameters:

  • task_number (required) — integer — Task number in the source board.
  • source_board_id (required) — integer — Board ID where the task currently belongs.
  • target_board_id (required) — integer — Board ID to move the task to.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• restore_task

  Use this with list_tasks onlyDeleted/includeDeleted to recover deleted tasks.

  Parameters:

  • task_number (required) — integer — Deleted task number in board scope.
  • board_id (required) — integer — Board ID where the task belongs.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• list_task_activity

  Use this to read the history of actions performed on a task (create, update, status changes, comments). Returns a timeline of activity entries.

  Parameters:

  • task_number (required) — integer — Task number in board scope.
  • board_id (required) — integer — Board ID where the task belongs.
  • limit — integer — Optional max number of activity entries to return (default 20).
  • offset — integer — Optional offset for pagination (default 0).

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• search_tasks

  Use this to find tasks by text, assignee, status, priority, or attention category across all your accessible boards. All filters are optional — combine them to narrow results. Returns up to 50 tasks ordered by last updated.

  Parameters:

  • query — string — Search query text (matches task title and description).
  • status — string — Filter by completion status: 'open' (not done) or 'done'.
  • board_id — integer — Scope to a specific board ID.
  • priority — string — Filter by priority: critical, major, normal, or low.
  • attention — string — Filter by attention category: overdue, due_soon, blocked, stale, unassigned.
  • assignee_id — integer — Filter by assignee user ID.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• my_work

  Returns up to 100 tasks assigned to or created by the caller across all boards they can access, ordered by most recent update. Use this to answer 'what's on my plate?' or to surface overdue/stale work. Pass namespaceSlug to scope to a single namespace.

  Parameters:

  • namespace_slug — string — Namespace slug (e.g. 'acme'), as returned by list_namespaces. Scopes tasks to boards in that namespace.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• list_statuses

  Use this command to inspect the board status catalog and ordering.

  Parameters:

  • board_id — integer — Optional board ID. Defaults to user's active board.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• create_status

  Use this command to add new statuses to board workflow.

  Parameters:

  • name (required) — string — Status display name.
  • code — string — Optional machine code. If omitted, derived from name.
  • color — string — Optional hex color, e.g. #FF9800.
  • index — integer — Optional sort index; lower appears earlier.
  • board_id — integer — Optional board ID. Defaults to user's active board.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• update_status

  Update status by statusId or by boardId+code.

  Parameters:

  • code — string — Existing status code for board+code lookup.
  • name — string — New display name.
  • color — string — New hex color.
  • index — integer — New sort index.
  • board_id — integer — Board ID for board+code lookup.
  • new_code — string — New machine code value.
  • status_id — integer — Target status ID.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• reorder_statuses

  Provide orderedStatusIds to set deterministic status ordering for a board.

  Parameters:

  • ordered_status_ids (required) — array — Status IDs in desired order.
  • board_id — integer — Optional board ID. Defaults to user's active board.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• delete_status

  Delete by statusId or boardId+code. If tasks use it, provide replacementStatusId.

  Parameters:

  • code — string — Status code for board+code lookup.
  • board_id — integer — Board ID for board+code lookup.
  • status_id — integer — Target status ID.
  • replacement_status_id — integer — Replacement status ID when deleting an in-use status.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• add_comment

  Use this to add a comment to a specific task. Provide board_id + task_number to identify the task.

  Parameters:

  • task_number (required) — integer — Task number in board scope.
  • board_id (required) — integer — Board ID where the task belongs.
  • text (required) — string — Comment text.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• list_comments

  Use this to retrieve all comments for a specific task. Provide board_id + task_number.

  Parameters:

  • task_number (required) — integer — Task number in board scope.
  • board_id (required) — integer — Board ID where the task belongs.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• delete_comment

  Use this to delete a comment. Allowed for the comment author or a board admin (owner/admin). Provide board_id + task_number for context and comment_id.

  Parameters:

  • comment_id (required) — integer — ID of the comment to delete.
  • board_id (required) — integer — Board ID where the task belongs.
  • task_number (required) — integer — Task number in board scope.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• add_checklist_item

  Use this to add a new item to a task's checklist. Provide board_id + task_number to identify the task.

  Parameters:

  • task_number (required) — integer — Task number in board scope.
  • board_id (required) — integer — Board ID where the task belongs.
  • title (required) — string — Checklist item text.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• list_checklist

  Use this to retrieve all checklist items for a specific task. Provide board_id + task_number.

  Parameters:

  • task_number (required) — integer — Task number in board scope.
  • board_id (required) — integer — Board ID where the task belongs.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• update_checklist_item

  Use this to update a checklist item's title or done status. Provide item_id and fields to update.

  Parameters:

  • item_id (required) — integer — Checklist item ID.
  • done — boolean — Set done status (true/false).
  • title — string — New title for the item.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• delete_checklist_item

  Use this to remove a checklist item from a task. Provide item_id.

  Parameters:

  • item_id (required) — integer — Checklist item ID to delete.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• list_board_members

  Use this command to see all board members and their roles (owner/admin/user).

  Parameters:

  • board_id (required) — integer — Board ID to list members for.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• invite_board_member

  Use this command to invite a user to a board. The invited user will receive a notification and must accept. Owner/admin only.

  Parameters:

  • board_id (required) — integer — Board ID to invite the user to.
  • username (required) — string — Telegram username of the user to invite (without @).
  • role — string — Role to assign (admin or user). Default: user. Cannot assign owner role.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• add_board_member

  Use this command to add a user directly to a board — they become a member immediately, with no invitation to accept. This is the one-step grant (the bot /addmember command). Owner/admin only; cannot create or assign the owner role.

  Parameters:

  • board_id (required) — integer — Board ID to add the user to.
  • username (required) — string — Telegram username of the user to add (without @).
  • role — string — Role to assign (admin or user). Default: user. Cannot assign owner role.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• remove_board_member

  Use this command to remove a member from a board. On group-chat-linked boards, removing a member with an explicit board_member row reverts them to a regular Telegram member (they stay on the board via the linked group). Members without a board_member row (Telegram-only) cannot be removed. Owner can remove admin/user, admin can remove user. Cannot remove owner.

  Parameters:

  • board_id (required) — integer — Board ID to remove the user from.
  • user_id (required) — integer — User ID to remove from the board.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• update_member_role

  Use this command to change an existing board member's role. Owner/admin only. Cannot target the board owner or promote anyone to owner.

  Parameters:

  • board_id (required) — integer — Board ID where the member belongs.
  • user_id (required) — integer — User ID of the member whose role to change.
  • role (required) — string — New role to assign (admin or user). Cannot assign owner.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• list_pending_invitations

  Use this without board_id to see your pending invitations. With board_id, see pending invitations for that board (must be a member).

  Parameters:

  • board_id — integer — Optional board ID to filter invitations for. If omitted, shows your pending invitations.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• respond_to_invitation

  Use this command to accept or reject a pending board invitation by its ID.

  Parameters:

  • invitation_id (required) — integer — Invitation ID to respond to.
  • accept (required) — boolean — True to accept, false to reject.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• cancel_board_invitation

  Use this command to cancel a pending board invitation. Only the original inviter or a board admin can cancel.

  Parameters:

  • invitation_id (required) — integer — Invitation ID to cancel.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• create_organization

  Create a new organization. The organization gets its own namespace (slug derived from the name). The creator becomes the organization owner. Use this when a user asks to create a namespace, organization, or workspace.

  Parameters:

  • name (required) — string — Organization name (e.g. 'Kangram', 'Acme Inc'). A namespace slug is derived from this.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• list_namespaces

  List all namespaces the user can see: their personal namespace plus any organization namespaces they own or are a member of. Use this to discover where boards can be created or moved.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• move_board

  Move a board from its current namespace to a target namespace. The board's 3-character code must be unique in the target namespace. The board URL will change. Use this to consolidate boards into an organization namespace.

  Parameters:

  • board_id (required) — integer — Board ID to move.
  • namespace_slug (required) — string — Target namespace slug (e.g. 'kangram'). Use list_namespaces to discover available slugs.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• transfer_board_ownership

  Transfer ownership of a board from the current owner to an existing board member (admin or user role). The current owner is demoted to the specified role (admin by default). Only the current board owner can initiate a transfer. The target must already be a board member — invite them first if needed. This is an irreversible high-impact operation.

  Parameters:

  • board_id (required) — integer — Board ID to transfer ownership of.
  • to_user_id (required) — integer — User ID of the new owner. Must already be a board member (admin or user role).
  • demote_current_owner_to — string — Role to assign to the current owner after the transfer. Defaults to 'admin'.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• get_board_prompt

  Fetch the board-level agent prompt — the markdown instructions an agent should follow when operating on this board. Read this into your context before working a board. Returns the content of the board's root file ("AGENTS.md"); null when no prompt is set.

  Parameters:

  • board_id (required) — integer — Board ID to read the prompt for.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• update_board_file

  Upsert a named markdown file on a board. In v1 the conventional name is "AGENTS.md" (the root prompt). Omit content (or pass empty) to clear a file's body. Future versions will support multiple named files; this command is the low-level writer beneath update_board's prompt option.

  Parameters:

  • board_id (required) — integer — Board ID to write the file on.
  • name (required) — string — File name (path-like identifier). Use "AGENTS.md" for the root prompt.
  • format — string — File format. Defaults to "markdown".
  • content — string — Markdown content. Omit or pass empty to clear the file body.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• list_board_files

  List the board's named files (the multi-file-ready prompt store). v1 returns at least the root "AGENTS.md" once a prompt has been set; empty list means no prompt/files yet.

  Parameters:

  • board_id (required) — integer — Board ID to list files for.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• create_oauth_client

  Register a new OAuth2 client so a third-party app can authenticate users via 'Login with Kangram'. Returns the client_id and a client_secret shown ONCE — store it securely. Owner-only.

  Parameters:

  • name (required) — string — Human-readable client application name.
  • redirect_uris (required) — array — Allowed redirect URIs (exact match, https required; http only on localhost). No wildcards.
  • scopes — array — Scopes the client is allowed to request. Defaults to ['profile'].

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• list_oauth_clients

  List the OAuth2 clients you own (client_id, name, redirect URIs, scopes, revocation status).

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• revoke_oauth_client

  Revoke one of your OAuth2 clients by its numeric ID. Existing tokens are not deleted but no new authorizations will be allowed.

  Parameters:

  • client_id (required) — integer — Numeric ID of the OAuth2 client to revoke.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• get_digest

  Compute an on-demand digest of the calling user's tasks across all accessible boards: overdue, stale (needs attention), new assignments, open count, and recently completed. Use this to answer 'what needs my attention?' or 'what's my work summary?'.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• save_session_handoff

  Save a session handoff — a durable note on the board recording where the work stands: what was done, what is next, what is blocked, and key links (PRs, issues, branches). Call this at the END of a working session so the next session (possibly a brand-new chat) can pick up exactly where you left off. Use this when the user says 'remember where we left off', 'save our progress', 'save the session state', or 'don't lose this context'. `summary` must be YOUR OWN concise authored recap — never a transcript or list of raw messages.

  Parameters:

  • board_id (required) — integer — Board ID the handoff belongs to.
  • summary (required) — string — Your authored recap: done / next / blocked. One concise string (max 20000 chars) — not a transcript.
  • links — Optional references — PR/issue URLs, branch names, doc links (e.g. ['https://github.com/o/r/pull/12', 'feat/auth-refactor']). Max 25 single-line items.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• get_project_context

  Get the full project context for a board — everything needed to CONTINUE work without re-explaining: the latest session handoff (where we left off), an attention snapshot (blocked / overdue / due soon / unassigned / stale counts), the top open tasks, and recent board activity. Call this at the START of a session when the user says 'continue where we left off', 'what's the state of the project', 'resume our work', or 'remind me what we were doing' — especially in a NEW chat after a previous session saved a handoff.

  Parameters:

  • board_id (required) — integer — Board ID to load context for.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• get_board_settings

  Use this command to read a board's effective settings — the stored value, or the default when unset (lazy). Pass a key to read one setting; omit it to read all. Returns { key: value } object(s).

  Parameters:

  • board_id (required) — integer — Board ID to read settings for.
  • key — string — Optional setting key (e.g. "autoAddAssignees"). Omit to read all settings.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• set_board_setting

  Use this command to change a board setting. The value is a string coerced to the setting's type server-side (booleans accept on/off, true/false, 1/0, yes/no). Use get_board_settings_schema to discover available keys and types. Example: set autoAddAssignees to "off" to require explicit /addmember on task assignment.

  Parameters:

  • board_id (required) — integer — Board ID to configure.
  • key (required) — string — Setting key (e.g. "autoAddAssignees").
  • value (required) — string — New value as a string (coerced to the setting's type). Booleans: on/off, true/false, 1/0.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• get_board_settings_schema

  Use this command to discover which board settings exist and their types/defaults (json-schema-like). Pass a key to inspect one setting; omit for all. Board-independent metadata — call this before set_board_setting to learn valid keys and types.

  Parameters:

  • key — string — Optional setting key to inspect. Omit for all available settings.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• bind_board_to_group

  Bind (link) a board to a Telegram group chat. The board becomes the group's primary board — bot commands in the group will act on this board. Unbinds any previous binding first. The actor must be an owner/admin of the target board. Use this when a user asks to set, link, bind, or assign a board to a chat/group. boardRef accepts: 'ns/code' (e.g. 'kangram/DEV'), a code alone (uses the active namespace), or a full URL like 'https://kangram.app/#/kangram/DEV'.

  Parameters:

  • board_ref (required) — string — Board reference: 'ns/code' (e.g. 'kangram/DEV'), 'code' alone, or a kangram.app URL.
  • group_chat_id — integer — Telegram group chat ID. Omit in a Telegram group context — the current group is auto-detected.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• create_agent

  Create a non-human agent account (User type='agent') inside the organization identified by its namespace slug. The agent becomes an org member immediately (board access via role inheritance), gets no personal namespace and cannot log in. A first API key is auto-issued and returned in plainKey — show/store it now, it is never shown again. Requires organization owner/admin.

  Parameters:

  • namespace_slug (required) — string — Namespace slug of the organization (e.g. 'kangram' for kangram.app/kangram).
  • username (required) — string — Unique username for the agent (letters, digits, dot, dash, underscore). Used for invites and search.
  • role — string — Organization role. 'member' (default) maps to board user; 'admin' maps to board admin. Agents never own orgs.
  • display_name — string — Human-readable display name. Defaults to the username.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• list_agents

  List the members of the organization identified by its namespace slug, including agent accounts (type='agent') with their active API-key counts and last key use. Requires organization owner/admin.

  Parameters:

  • namespace_slug (required) — string — Namespace slug of the organization.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• delete_agent

  Delete an agent account: revokes all its API keys, removes memberships, unassigns its tasks, then hard-deletes the user. When history rows (messages/activity) block the hard delete, the agent is deactivated instead (zero access, row kept) and status='deactivated' is returned. Requires organization owner/admin.

  Parameters:

  • namespace_slug (required) — string — Namespace slug of the organization.
  • agent_username (required) — string — Username of the agent to delete.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• issue_agent_key

  Mint a new API key for an agent member of the organization. Use for rotation or additional keys. The plaintext key is returned once — store it immediately. Requires organization owner/admin.

  Parameters:

  • namespace_slug (required) — string — Namespace slug of the organization.
  • agent_username (required) — string — Username of the agent.
  • name — string — Key label. Defaults to '<username> — <date>'.
  • scope — string — Key scope label (enforcement is planned; stored today).

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• revoke_agent_key

  Revoke an agent's API key by id. Only keys owned by agent accounts are revocable this way (humans revoke their own). Requires organization owner/admin of an org the agent belongs to.

  Parameters:

  • key_id (required) — integer — API key id (from list output or the web UI).

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

Measured by MCPYP probing. Untested fields are omitted, never estimated. Listing is always free; MCPYP never proxies calls or stores user tokens.