# Kangram

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

- name: app.kangram/kangram
- version: 1.0.0
- connection class: R1 (autonomous)
- trust: 76/100 flags: no-repository
- quality: 65/100 (needs work)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/app.kangram%2Fkangram
- tools: https://api.protogrid.dev/v1/servers/app.kangram%2Fkangram/tools

**An agent can connect on its own if it already holds `KANGRAM_TOKEN`.** Remote endpoint behind a static API key or header. The registry never sees the value; the agent fills the placeholder.

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "kangram": {
      "type": "http",
      "url": "https://kangram.app/mcp",
      "headers": {
        "Authorization": "Bearer ${KANGRAM_TOKEN}"
      }
    }
  }
}
```

Placeholders to fill: `${KANGRAM_TOKEN}`.

## Trust

- hygiene: 80
- liveness: 98
- freshness: 85
- provenance: 45
- drivers: +dns-namespace +reachable +uptime-95% ~updated-62d-ago -no-repository
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 65/100 (needs work)

### protocol: 75 (weight 25)

- warn `protocol.modern`: newest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
- n/a `protocol.stateless`: only applies to 2026-07-28 servers
- pass `protocol.transport`: streamable HTTP
- n/a `protocol.list_ttl`: only applies to 2026-07-28 servers

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 57 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- fail `tools.annotations`: no tool declares readOnlyHint or destructiveHint, so clients cannot tell safe calls from risky ones
- fail `tools.directory_hints`: no tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: clone_board (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); delete_task (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); move_task (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); …
- warn `tools.token_cost`: about 10,016 tokens to load every tool
- warn `tools.api_dump`: 61 tools, 69% named like REST operations: looks like an API mapped one endpoint per tool

### stability: n/a (weight 15)

- n/a `stability.changes`, `stability.rug_pull`: tool history recorded for 5 of the 7 days needed

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 61, about 10,016 tokens to load them all
- tool set hash: 9fb5f64f4df88244e449a1abd13bb1be
- badge: [![protogrid quality](https://protogrid.dev/badge/app.kangram/kangram.svg)](https://protogrid.dev/servers/app.kangram/kangram)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

_No tool definition changes recorded._

## Remotes

- https://kangram.app/mcp (streamable-http, auth api_key ${KANGRAM_TOKEN}, reachable true, uptime30d 0.9464286)

## Packages

_none_

## Tools (61)

- `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.
- `add_checklist_item`: Use this to add a new item to a task's checklist. Provide board_id + task_number to identify the task.
- `add_comment`: Use this to add a comment to a specific task. Provide board_id + task_number to identify the task.
- `archive_board`: Use this to hide a board from active workflows without deleting it.
- `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'.
- `cancel_board_invitation`: Use this command to cancel a pending board invitation. Only the original inviter or a board admin can cancel.
- `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.
- `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.
- `create_board`: Use this command to initialize a board and its default status workflow.
- `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.
- `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.
- `create_status`: Use this command to add new statuses to board workflow.
- `create_task`: Use this to add a task. Provide boardId for deterministic routing; otherwise active board is used.
- `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.
- `delete_checklist_item`: Use this to remove a checklist item from a task. Provide item_id.
- `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.
- `delete_status`: Delete by statusId or boardId+code. If tasks use it, provide replacementStatusId.
- `delete_task`: Use this to mark a task as deleted without permanent removal.
- `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).
- `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.
- `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).
- `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.
- `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?'.
- `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.
- `get_task`: Use this to read one task including its description, deadline, tags, status, and assignee.
- `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.
- `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.
- `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.
- `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.
- `list_board_members`: Use this command to see all board members and their roles (owner/admin/user).
- `list_boards`: Use this command to discover boards before creating or filtering tasks.
- `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.
- `list_checklist`: Use this to retrieve all checklist items for a specific task. Provide board_id + task_number.
- `list_comments`: Use this to retrieve all comments for a specific task. Provide board_id + task_number.
- `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.
- `list_oauth_clients`: List the OAuth2 clients you own (client_id, name, redirect URIs, scopes, revocation status).
- `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).
- `list_statuses`: Use this command to inspect the board status catalog and ordering.
- `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.
- `list_tasks`: Use this to inspect task backlog by board, assignee, status, priority, tags, title substring, creation date range, and deletion state.
- `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.
- `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.
- `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.
- `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.
- `reorder_statuses`: Provide orderedStatusIds to set deterministic status ordering for a board.
- `respond_to_invitation`: Use this command to accept or reject a pending board invitation by its ID.
- `restore_board`: Use this to recover a previously archived board.
- `restore_task`: Use this with list_tasks onlyDeleted/includeDeleted to recover deleted tasks.
- `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.
- `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.
- `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.
- `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.
- `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.
- `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.
- `transition_task_status`: Use this for explicit status moves while keeping other fields unchanged.
- `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.
- `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.
- `update_checklist_item`: Use this to update a checklist item's title or done status. Provide item_id and fields to update.
- `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.
- `update_status`: Update status by statusId or by boardId+code.
- `update_task`: Use this to edit task title/description/deadline/tags/assignee/status.