Ir para o conteúdo
Logo de KanbanMCP

Servidor MCP de KanbanMCP

Quais servidores MCP são de KanbanMCP, do registro oficial e encontrados perguntando ao próprio domínio, se respondem e o que oferecem. Um programa verificou cada item; nada foi copiado da página do produto.

lido em 2026-10-28

← Voltar para KanbanMCP

De quem é o servidor
  • Endereçohttps://kanbanmcp.com/mcpfora do registro oficial: respondeu quando perguntado

Nenhuma entrada do registro oficial de MCP nomeia este servidor. Ele respondeu em kanbanmcp.com quando o Atlas perguntou no endereço onde servidores costumam ficar, então é do próprio fornecedor. Clientes e catálogos que listam servidores a partir do registro não o mostram.

Quando perguntamosverificado em 2026-10-28
  • Estadorespondeverificado em 2026-10-28
  • Ferramentas31
  • O servidor se chamakanbanmcp
  • Versão do servidor0.1.1
  • Versão do protocolo2025-06-18

Em 2026-10-28 o servidor respondeu a initialize e tools/list sem login. Primeira resposta em 54 ms.

Um agente deve conectá-loAinda não está claro
  • As ferramentas fazem todos os casos de uso verificados: hand a card from one coding agent to another; review agent work on a shared kanban board; resume a stalled task from the previous agent's notes.
  • Verificado em 6 dos 7 dias necessários para julgar a confiabilidade.

Depois de conectar

  • Para "hand a card from one coding agent to another", a primeira chamada provável é complete.
  • Para "resume a stalled task from the previous agent's notes", a primeira chamada provável é show.
  • create_card, update_card, create_board, edit_column, delete_column alteram dados sem login: qualquer pessoa com o endereço pode chamá-las.

Dito por regras a partir das medições acima. A primeira chamada provável é a escolha de um modelo na lista de ferramentas; leia a descrição antes de confiar nela.

Medido todo diaverificações diárias: 6, a primeira em 2026-10-28
  • Nota INITE MCPdepois de uma semanaa nota precisa de 7 verificações diárias: 6 até agora
  • O que um agente consegue fazer com ele3 de 3 casos de uso
  • Respondeumedindo6 das 7 verificações diárias necessárias para mostrar a porcentagem
  • Mediana da primeira resposta372 ms
  • Espaço no contexto do agente≈ 8.729 tokensas definições de todas as ferramentas (31), que o agente carrega a cada turno
  • Definições das ferramentasA · 98 de 100
  • Resultados tipados0 de 31 ferramentasdeclaram outputSchema: o resultado chega tipado e é lido de uma vez
  • Parâmetros sem descrição: em 3 de 31

O que um agente consegue fazer com ele

  • consegue · hand a card from one coding agent to another
  • consegue · review agent work on a shared kanban board
  • consegue · resume a stalled task from the previous agent's notes

Cada caso de uso do produto foi perguntado ao Jev junto com a lista de ferramentas deste servidor: um agente consegue fazer isso com essas ferramentas?

Vale conferir

  • Ferramentas que alteram dados, em um servidor que responde sem login: create_card, update_card, create_board, edit_column, delete_column

Um programa verifica o servidor uma vez por dia: initialize e tools/list, sem modelo. Os tokens são o tamanho das definições, a cerca de quatro caracteres por token. A nota é a média de seis verificações do nome, da descrição, do esquema e das anotações de cada ferramenta; diz se as ferramentas estão bem descritas, não se funcionam. A nota pesa só o que foi medido: se responde (25%), se faz o trabalho do produto (25%), definições (20%), contexto (10%), uso (10%) e a facilidade de conectar (10%). Uma parte não medida fica de fora, e uma instrução oculta limita a nota a 40. O estado dos servidores MCP dos fornecedores: método e números →

Ferramentas que oferece31 ferramentas · lido em 2026-10-28
  • claim_next

    Claims the next Ready card for you, starts a run and moves the card to Running. Pass cardId to work one exact card. Add peek to check first, with no claim, and reading true to hold a card while you read it. With no filter, a call takes…

  • show

    Reads one card with its comments, questions and answers, prior runs and capacity. Read-only; it needs no claim or persona.

  • heartbeat

    Keeps your claim alive, a reading claim too. Call it about every 5 minutes. A comment with your runId counts too. A master agent sends heartbeat for each sub-agent's card, with that cardId and runtimeHandle. Pass busyFor before a long…

  • comment

    Adds a comment to a card's thread, or several with comments; to read a card first, claim it with claim_next, cardId and reading true. To ask a teammate, write @ and the persona's name; a plain name notifies nobody. At three agent comments…

  • complete

    Ends your run with a handoff. The card moves to Done. It goes to Review when a question on it still waits for a person. It also goes to Review when the board needs a person's sign-off and your persona may not mark work done. Your claim…

  • request_review

    Ends your run and sends the card to Review for a person to check, whatever the board's Done rules are. Takes the same handoff as complete. It clears the assignee. Pass reviewer to name who reviews.

  • block

    Ends your run because you cannot continue, with a typed reason. The card leaves Running and your claim ends. Use it only for something outside your control. A card that does not suit you is for release. For a failed verify command, use…

  • release

    Ends a reading claim, or hands back a card you hold when it does not suit you, or not now. It goes back where it was and counts for nothing. You do not get it again, unless you pass until. In a batch it hands back that card only.

  • raise

    Files a signal: assumption (the default), question, concern, rule proposal, deferred or observation. Only blocking parks your card: keep it for a choice you cannot undo. Offer options only with type question, and mark your advice. If you…

  • inbox

    Reads what waits for you: answers to your questions, and comments that @mention you or your personas. Marks both as seen. Call it when an attention note says so, or to search what was already decided.

  • resolve

    Closes a question. With answer, it answers a teammate's question when you know the answer. Without answer, it closes a question you raised, with a note, when you no longer need it answered. Only a person may close a question that has…

  • events_since

    Reads board activity after a cursor. Call it between steps to see what changed.

  • toggle_task

    Flips a checklist item on a card between done and not done, or sets it to a given state. Pick the item by position or by text.

  • find_cards

    Finds cards on one board. Leave out boardId to search every board you reach. It gives one short row per card, with no description or comments.

  • list_boards

    Lists the boards this connection reaches, with each board's id, slug, columns and card counts. Read-only.

  • get_setup

    Your first call on a new connection. It says what this connection can do and what exists: the boards you reach, who you act as, and which briefs are missing. It gives the steps to set yourself up and the questions to ask. Part "rules"…

  • get_context

    Sends everything you work from again: the protocol, the workspace brief, this board's brief, your persona's brief and a digest of the rules. Call it after a context reset or compaction, in a new session, or when a heartbeat says…

  • rules

    Keeps your installed rules in step. With ruleId, it records where you installed a rule and its hash. Call it once per file after you install a rule from get_setup (part "rules"). Without ruleId, it tells you which rules you hold are…

  • create_card

    Creates a card with all its fields in one call. Pass copyFrom to copy another card. Pass cards to create several at once. It lands in Triage unless you pass state or column. Each card counts toward the plan's limit.

  • update_card

    Changes any of a card's fields in one call, and archives or restores it (archived). Fields you leave out stay as they are. Pass updates to change several cards at once. Pass checklist as {add, remove} to change items in place. To move a…

  • move_card

    Moves a card to a state or to an exact column. Pass summary with a move to Ready to send the card back for changes. Pass clearWait to let agents claim the card again now.

  • link

    Makes one card the blocking parent of another. The child waits until the parent reaches Done. Pass remove true to take the link away again.

  • undo

    Reverts the card's latest recorded change. Calling it again redoes the change.

  • stop_run

    Ends the active run on a card now. The claim ends and the card goes back to Ready. Use it when an agent is stuck, wrong, or must be cut off. In a batch it stops that card only; batch true stops all.

  • promote

    Turns a raised signal into a Triage card and marks the signal resolved.

  • create_board

    Create a new board in the workspace. The board gets the default columns and is private.

  • edit_column

    Adds a column, or changes one. Without columnId it adds one at the end: pass state, which tells agents what its cards mean. With columnId it renames the column, moves it, or both. A column's state never changes.

  • delete_column

    Remove a column. If it holds cards, name another column to receive them.

  • set_brief

    Replaces a brief: this board's brief, or with scope workspace the workspace brief that every board's agents read. Use it only after the person sees the draft and says yes. How to write it: call get_setup with part "briefs".

  • update_persona

    Changes one persona's name, title, description or brief. Use it only while you act as the person (leave persona out), who must be an owner or admin. A connection that acts as a persona cannot use it. Use it after the person sees the text…

  • label

    Changes a label on every card that carries it: delete, rename, merge into another label, or archive. Call it without confirm first. The answer says how many cards carry the label, and nothing changes. Change a label only when a person or…

Como conectar

Adicione o servidor à configuração do seu cliente MCP. Claude Desktop, Cursor e a maioria dos outros clientes leem este formato:

{
  "mcpServers": {
    "kanbanmcp": {
      "type": "http",
      "url": "https://kanbanmcp.com/mcp"
    }
  }
}

Adicionar

Claude Code, no terminal

claude mcp add --transport http kanbanmcp https://kanbanmcp.com/mcp

Adicionar ao CursorAdicionar ao VS Code

claude.ai, ChatGPT e outros clientes: adicione https://kanbanmcp.com/mcp como conector personalizado nas configurações.

Outros servidores atribuídos a KanbanMCP
  • com.kanbanmcp/kanbanmcpendereço próprio de cada instalaçãoverificado no registro MCP

Cada linha é algo que um programa encontrou ao procurar: o registro, a resposta do próprio servidor, uma especificação que se lê. Linha ausente quer dizer que não encontramos, não que não exista.