MCP server

Kaiku Official

tech.kaiku/kaiku

Checked 26 Oct 2026, 08:29 UTC · It answered and asked for a sign-in

Issue tracker and wiki for teams and their agents: find, file and update issues, write pages.

Website

At a glance

Type

MCP server

Publisher

kaiku.tech (verified by the MCP Registry)

Status

Signs in with your account

Tools

179

Sets up in

Claude Code, Claude Desktop, Codex, Gemini CLI, Cursor, VS Code, Antigravity, ChatGPT, OpenAI API, Grok

Last checked

26 Oct 2026, 08:29 UTC

Connect it to your agent

Add to CursorAdd to VS CodeVS Code Insiders

Opens the app, which shows the server and asks you to confirm. For other apps, copy the setup below.

Claude Code

claude mcp add --transport http kaiku https://app.kaiku.tech/mcp

Claude Desktop

Settings → Connectors → Add custom connector, and paste the URL.

Codex (config.toml)

[mcp_servers.kaiku]
url = "https://app.kaiku.tech/mcp"

Gemini CLI

{"mcpServers":{"kaiku":{"httpUrl":"https://app.kaiku.tech/mcp"}}}

Cursor

{"mcpServers":{"kaiku":{"url":"https://app.kaiku.tech/mcp"}}}

VS Code

{"servers":{"kaiku":{"type":"http","url":"https://app.kaiku.tech/mcp"}}}

Antigravity

agy mcp add kaiku https://app.kaiku.tech/mcp

ChatGPT

Settings → Apps & Connectors → Advanced settings: turn on Developer mode, then Create a connector and paste the URL. Which plans can do this varies.

OpenAI API (Responses tools)

{"type":"mcp","server_label":"kaiku","server_url":"https://app.kaiku.tech/mcp","require_approval":"always"}

Grok (xAI API tools)

{"type":"mcp","server_label":"kaiku","server_url":"https://app.kaiku.tech/mcp"}

Signs in with your account: your agent app opens a sign-in page the first time you use it.

Tools

• add_attachment ~424 tokens
  Attach a file to an issue: pass its bytes as 'contentBase64', or its content as 'text' when the file is text. Attaching a filename the issue already has replaces that file rather than adding a second copy, so retrying this call cannot double it. A file on the person's own disk — a screenshot, a PDF
• add_comment ~477 tokens
  Add a comment to an issue, or reply to one of its comments ('replyTo' is a comment id from get_comments). A reply notifies the author of the comment it answers, whether or not they watch the issue — no mention needed — and they are told once even if also mentioned. Requires permission to comment in
• add_legal_reference ~418 tokens
  Put a reference to a legal act on an issue or a wiki page — as «Add» in the block «Legal acts» does: it is yours, accepted at once. 'url' is the act's address on one of the official sites acts are read from (a refusal lists them); an act not read yet is read in the background, so 'hasText' may be fa
• add_to_showcase ~533 tokens
  Show one issue, one wiki page or one claim of a PRIVATE project in a public project of the same company — by reference, not as a copy: anybody, signed in or not, can then read that issue (with its comments and files) or that page as it is now, and every later edit; the rest of its project stays clos
• add_wiki_attachment ~631 tokens
  Attach a file to a wiki page, identified by 'pageId' or by 'spaceKey' + 'title': pass its bytes as 'contentBase64', or its content as 'text' when the file is text. Re-attaching a filename the page already has replaces its bytes and bumps its version, as the wiki does everywhere else, so retrying thi
• add_wiki_comment ~443 tokens
  Comment on a wiki page, or reply to one of its comments ('replyTo' is a comment id from get_wiki_page). A reply notifies the author of the comment it answers, whether or not they watch the page — no mention needed — and they are told once even if also mentioned. Identify the page by 'pageId', or by
• admin_bank_transfer Moves money · ~198 tokens
  Administrators only: where a bank transfer is to be sent (PM-625) — beneficiary, account and its own currency, bank and SWIFT, the intermediary bank if there is one, the purpose line, how many days a wire is given, and who last changed all of it. 'offered' is the one flag that answers «may a custome
• admin_errors_week ~178 tokens
  Administrators only: the error collector's week — events and distinct errors per project against the week before, errors first seen that week with their release, the loudest by events and by people, and errors that came back after being resolved. The same numbers the weekly error report carries. A p
• admin_funnel ~612 tokens
  Administrators only: the installation as a business over a period — registrations, how many of them became working companies, purchases and conversion by cohort, churn, and money. Money comes in two halves that must not be added together: 'stock' is what recurs every month at today's prices, 'revenu
• admin_invoices ~278 tokens
  Administrators only: what companies were asked to pay and what answered it — each invoice with its amount, its coin, whether it is paid and what is short, and the payments against it. Amounts are never added across coins: each row carries its own currency and they stay apart. The list is the fleet's
• admin_landing_week ~142 tokens
  Administrators only: the landing site's week — visits, where they came from, clicks on sign-up, and the registrations that followed. The same numbers the weekly report carries into the monitoring chat. Ask for an earlier week with weeksAgo. The rendered message is not returned, only the figures.
• admin_load ~196 tokens
  Administrators only: how loaded this machine is and what the language models cost. Load is this machine's own — database, streams, memory, processor, traffic and stored bytes, each as used against allowed, where an allowance is known. Model spend covers the assistant, search-by-sentence and translat
• admin_overview ~180 tokens
  Administrators only: the whole installation by the numbers — accounts, workspaces, projects, issues, comments and sprints, plus issues broken down by status and by project. Counted across every workspace, which is what makes it the installation's rather than one company's. A total is null, never zer
• admin_set_bank_transfer Moves money · ~841 tokens
  Administrators only, and this one CHANGES things: state where bank transfers are to be sent. Send the WHOLE set every time — anything left out is cleared, not kept, because details half of one bank and half of another are money sent to a mixture of two. Read admin_bank_transfer first and repeat what
• admin_workspace_journal ~207 tokens
  Administrators only: what was done to one company and by whom — created, plan changed, period extended by hand, credited, suspended, resumed, erased — newest first, up to a hundred entries, each with the reason that was written down at the time. This is the answer to 'why is this company on a period
• admin_workspaces ~408 tokens
  Administrators only: every company on the installation — its plan, what state it is in (trial, active, over-limit, suspended…), when what it paid for runs out, how many days are left, what it is using against what it may use, and its balance. Ask with endingInDays to get only the ones running out th
• answer_issue_question ~315 tokens
  Answer a question that was put to you on an issue, by choosing one of its options. Only the person the question was addressed to may answer it; answering again with a different option changes the answer and says so in the thread. A question whose deadline already passed can still be answered — that
• answer_review_remark ~281 tokens
  Answer a remark of a page's review (see get_wiki_page_reviews). As the page's author — whoever may edit it — 'fixed': true says it is put right in the version the page is at now, false that it still stands (it is then compared with this version, so the next edit asks again); 'note' says how. As its
• approve_wiki_page ~330 tokens
  Approve a wiki page IN YOUR OWN NAME, in the edition you read: 'version' is the page's version as get_wiki_page gave it, and the call is refused if the page has been edited since — read it again first. The approval is a line in the page's journal: who, when, which edition, and an optional note. It i
• ask_issue_question ~634 tokens
  Ask one person a question with pre-written answer options, in an issue's thread — the way to get a decision that does not get lost in the comment stream. The question appears as an ordinary comment (so every Jira-speaking reader sees it) and is tracked separately: the person you ask sees it counted
• ask_wiki_page_approval ~274 tokens
  Name the people who may approve a wiki page, and tell each of them: they get a notification that opens the page. 'who' is usernames or e-mails as 'a,b' — each must be able to read the page. Somebody already named is asked again, about the edition the page is at now. With release: true the people in
• check_checklist_item ~244 tokens
  Tick or untick one checklist item by the 'id' get_checklist gave it. Written as a click on the item is: the same history line and the same notices to the issue's watchers, in your name — and only the item's box changes, so an edit somebody is saving to the description at the same moment is never los
• check_source ~413 tokens
  Check a source of a project's register against the open services now: its arXiv id against arXiv, its DOI against Crossref, its zbMATH number against zbMATH Open — whether the work is there and whether its authors (by surname), title and year are the record's. Every service agreeing makes it 'api' (
• cite ~292 tokens
  How to cite a work of a project's register in a text you write: give its key or any identifier in any shape ('arXiv:2301.01234', a DOI or its address, 'MR1234567', 'Zbl 1234.56789', an ISBN) and get 'cite' — '[@KEY]', what to put in a page, a comment or a description — the 'reference' line a bibliog
• code_calls ~303 tokens
  Who calls a class, method or function, or what it calls, to a depth of up to 3 — each use with its file and line. Uses linked only by the bare name are counted, not listed, because they are often a different symbol of the same name. When several symbols share the name, the answer lists them to choos
• code_symbols ~210 tokens
  Where a class, method or function is declared in the code of the repositories connected to a project: its file, line and signature. Ask by name, or Class.Method to say whose. Only repositories whose owners opened them to agents are asked.
• connect_repository ~383 tokens
  Connect one more GitHub or GitLab repository to a project, by its address — 'https://github.com/owner/repo', a gitlab.com project or a company's own GitLab. No token is taken here, ever: the host is asked as anybody would ask it, so a public repository connects at once and a private one is refused,
• create_credential ~601 tokens
  Attach a secret — a password, a key, a test login — to an issue or a wiki page, instead of writing it in a comment or a description, where everyone on the project reads it for ever. Pass issueKey or pageId, and a 'name' saying what it is. It can be read by the person whose token this is, by the peop
• create_issue ~751 tokens
  Create an issue in a project visible to this token. Returns the new issue key. Requires permission to create issues in that project. Answers with 'notified' (who this actually reaches: the people mentioned, and for an assignment the new assignee as 'assignee' and the one taken off as 'unassigned' in
• create_project ~719 tokens
  Administrators only: create a project — a new key, a starter board, and its own wiki space, led by you unless you name someone else. The key is yours to choose and is never invented for you: one already taken is refused, naming the project holding it, rather than quietly becoming KEY2 — the key show
• create_project_rule ~1531 tokens
  Add a rule to a project: when an issue enters 'status', append 'template' to its description. A rule appends its checklist to an issue's description when the issue ENTERS the rule's state — from the board, the Jira API or update_issue alike. The block starts with a hidden marker line '[//]: # (pm-ru
• create_version ~319 tokens
  Add a version to a project, at the end of its sequence. A version is what a project's work goes out in — '2.4.0', 'Autumn'. It is the project's own: an issue carries versions of its own project only, any number of them ('fixVersions' on create_issue, update_issue and get_issue; JQL 'fixVersion = "2.
• create_wiki_embed ~475 tokens
  Put one scene of a wiki page on other sites (PM-1076): a link anybody can open with no account, which plays the block's scene in our player and shows nothing else of the page — not its title, its words, its space or its author, only the 'caption' you give. Answers with the link and the ready <iframe
• create_wiki_page ~767 tokens
  Create a wiki page from Markdown in a space you can write to. Hangs off the space home page unless you name a parent (by 'parentId', or by 'parentTitle' within the same space). Returns the new page id and its URL. Mention someone as [@Their Name](user:username) — on a wiki page that is the form that
• decide_join_request ~237 tokens
  Approve or decline one request to take part in a public project (ids from list_join_requests). Approved, the person becomes a reporter there — files issues and comments; a broader role is given on the project's people screen, as for anybody on the board. Declined, they may ask again in 14 days. The
• decide_persons ~294 tokens
  Confirm or reject every PROPOSED person of one source at once — the persons the reading found on one page, issue or comment. 'source' as list_persons' 'sources' names it; 'expected' is how many proposed persons of it you were shown, and if the count has changed nothing is written. Ask the person fir
• decide_support_letter ~208 tokens
  Decide what a held or failed letter to the support address is. 'release' files it as if it had just arrived, past the spam filter and the limits: it joins the request it proves it answers, or opens a new one (and the sender gets the usual acknowledgement). 'dismiss' says it is not a request; its fil
• decide_terms ~355 tokens
  Confirm or reject every PROPOSED term of one source at once — a wiki page or an issue the terms were found on — as the terms screen's «Confirm all on this page» does. Read them first with list_terms and that 'source', and pass 'expected': how many proposed terms you read there. If the count is diffe
• define_term ~376 tokens
  What a word means IN THIS COMPANY'S PROJECTS — a code like 'PW06' or 'F24', a project's own name for something, a notion its pages define ('петля', 'размерная подгруппа'). Ask it before guessing at a word you do not know in an issue or a page: the answer is the project's own short definition, where
• delete_agent_usage Deletes data · ~148 tokens
  Remove one agent-usage record from an issue, by the id that get_agent_usage returns. For correcting a record's numbers, re-send it with report_agent_usage instead — the same source + externalId updates in place. Requires permission to edit the issue.
• delete_attachment Deletes data · ~164 tokens
  Remove a file from an issue, by 'filename' or by attachment 'id' — both come back from get_issue. Requires permission to edit issues in that project.
• delete_claim Deletes data · ~227 tokens
  Remove a claim from a project's register for good, with what it rests on — it cannot be undone, so do it only when the person asked for this very one to be deleted; confirm its label with them first. Its journal keeps its lines and one that it was deleted. A claim that turned out false is not delete
• delete_computation Deletes data · ~140 tokens
  Remove one computation from an issue, by the id list_computations gives — for a job reported against the wrong issue. To correct one, report it again under its own name instead. Requires permission to edit the issue.
• delete_credential Deletes data · ~138 tokens
  Remove a credential, by the id from list_credentials — the value, its reader list and the record of who read it go with it, and it cannot be brought back. Only the person who attached it and the project's lead may. To take one person's access away, use update_credential's 'readers' instead.
• delete_issue_schedule Deletes data · ~125 tokens
  Remove a recurring issue from a project. The issues it already filed stay as they are. The project's lead, the company's owner or an admin only.
• delete_person Deletes data · ~179 tokens
  Remove a person from a project's register for good, with all their spellings and facts — it cannot be undone, so do it only when the person asked for this very one to be deleted; confirm the name with them first. The journal keeps a line that a person was deleted, without the name. To turn down a PR
• delete_project_field Deletes data · ~133 tokens
  Remove a column from a project. Answers with how many issues lost a value, because that number is what the decision was about — the issues themselves are untouched. Project lead or admin only.
• delete_project_issue_type Deletes data · ~128 tokens
  Remove an issue type of this project's own. Refused while any issue is of it or any field is kept for it — change those first; a rule on it goes with it. Project lead or admin only.
• delete_project_rule Deletes data · ~146 tokens
  Remove a project rule, by its id from list_project_rules. Checklists it already added stay in their issues; its journal goes with it. To stop it for a while instead, update_project_rule with enabled=false. Project lead or admin only.
• delete_source Deletes data · ~231 tokens
  Remove a source from a project's register for good, with its authors — it cannot be undone, so do it only when the person asked for this very one to be deleted; confirm its key with them first. Its journal keeps its lines and one that it was deleted. A source found to be wrong is not deleted: set_so
• delete_term Deletes data · ~165 tokens
  Remove a term from its project for good — it cannot be undone or restored, so do it only when the person asked for this very term to be deleted; confirm the name with them first. To turn down a PROPOSED term use set_term with state 'rejected' instead — a rejected term is remembered and not proposed
• delete_wiki_attachment Deletes data · ~244 tokens
  Remove a file from a wiki page, by its 'filename' as listed by get_wiki_page. Identify the page by 'pageId', or by 'spaceKey' + 'title'. References to it in the page body are left alone — they simply stop resolving, so tidy the body too if it named the file. Requires permission to edit the page.
• delete_wiki_embed Deletes data · ~129 tokens
  Take an embed of a wiki page's scene down (PM-1076): its link answers 404 at once on every site that has it. It cannot be undone — an embed made again of the same block gets a new link. Only for somebody who may edit the page; a line in its history.
• delete_wiki_page Deletes data · ~244 tokens
  Delete a wiki page. Identify it by 'id', or by 'spaceKey' + 'title'. A page with children takes its whole subtree with it, so that is refused unless you pass includeChildren: true — the answer names what would go. The space home page can never be deleted. Requires permission to edit the wiki.
• distinct_persons ~268 tokens
  Answer a hint of list_persons' 'similar' with «these are two different people» — «Mikhailov» and «Mikhaylov» who are not one — so the pair is not hinted again; or, with 'undo', take that answer back. ASK the person first, naming both as list_persons shows them; never decide it yourself from the name
• evaluate_wl ~397 tokens
  Evaluate Wolfram Language with the very engine a wiki page's ```wl cells are evaluated by (mathics-core-rust's wl-wasm), on the server and now — to check an expression before putting it on a page, or what a page's cells will say. Pass 'code' for one cell, or 'cells' for several evaluated in one sess
• export_sources_bib ~292 tokens
  A project's register of sources as a BibTeX file's text: one entry per source, its key the source's (what \cite{} and [@KEY] name), the identifiers as eprint/archivePrefix (arXiv), doi, mrnumber, zbl, isbn; a source with the † says so in a comment above its entry. 'keys' narrows it to those sources;
• find_by_legal_document ~350 tokens
  Which issues and wiki pages refer to a legal act — the list on the act's card. Per document the value names (the same act in two languages is two): 'total' issue-and-place and page-and-place lines, 'hidden' of them where you may not read (counted, never named), and 'items' — the 'place' cited with t
• find_issues ~360 tokens
  Find issues by what they are ABOUT, in plain words — by meaning as well as by words (where the server has its embedding model), so an issue that says the same thing differently or in another language is found, which search_issues (JQL) cannot do. The same search answers with `pages` (wiki pages) and
• find_lean_declaration ~274 tokens
  Where a Lean declaration of a claim is declared — 'theorem rank5' in a .lean file — searched in the project's repositories that are open to its agents: the repository, the file, the line, the line's text and the commit the index is at. Pass the full name, e.g. 'D5.rank5_decided'; the file names its
• find_person ~440 tokens
  Who a name in this company's texts is — «Гупта», «N. D. Gupta», «Sjogren». Ask it BEFORE writing a person's name with initials or in another script: the answer is every person the spelling may be, each with all their spellings by script ('latin', 'cyrillic') and form ('full' — with initials or a fir
• get_agent_usage ~133 tokens
  What background-agent runs have cost an issue (local or mirrored/upstream): one record per run (tokens by kind, machine time, agent/model/host) plus the totals. A null metric means nobody reported it — which is not the same as zero, so 'reporting' says how many records carried each metric.
• get_attachment ~202 tokens
  Read one file attached to an issue — its bytes, base64-encoded — by the issue key and the 'filename' as get_issue lists it. The bytes travel as text through the conversation and cost roughly a third more than the file itself, so there is a size ceiling; the pm-files MCP server saves a file to a path
• get_change ~134 tokens
  The files one merge request, pull request or commit touches, with their diffs. Large diffs arrive cut.
• get_checklist ~254 tokens
  Read an issue's checklist — the '- [ ]' lines of its description — as items, in order: each with a stable 'id' (pass it to check_checklist_item), 'checked', its words ('text', without reminder or picture), its 'depth' when nested, its 'reminder' ('YYYY-MM-DD HH:MM' or null) and its 'picture' — the a
• get_claim ~229 tokens
  One claim of a project (see list_claims), with its journal: every change of its status — from what, to what, who and on what ground — newest first, and when it was created and edited; 'restingOn' names the issues whose link column rests on it (a requirement of the register), and counts those you may
• get_comments ~325 tokens
  Read the discussion on an issue, oldest first. Without 'startAt' you get the END of the thread — the most recent 'limit' comments — because catching up means reading the latest, not the first ever written; 'earlier' says how many stand before the page you got, and 'startAt' walks back through them.
• get_issue ~167 tokens
  Get one issue by key (e.g. 'UK-1') if it is visible to this token, including its description, status, assignee, labels, sub-tasks, the issues it is linked to and the wiki pages linked to it. 'comments' is a COUNT, not the text — read the thread itself with get_comments whenever it is not zero: decis
• get_jira_connection ~261 tokens
  Which Jira of its own a project is connected to: the site, the account whose token it uses (what a write there is signed as), whether a token is held ('secretSet' — the token itself never comes back) and whether the connection is switched on; and under 'confluence', whether the same site's Confluenc
• get_jira_link ~284 tokens
  Which issue of the project's own Jira this issue is, and what that Jira says of it now — its summary, status, assignee and link — read with the token the project's administrator connected. 'connected' false means the project has no Jira; 'jira.state' is 'found', 'missing' (no such issue, or one the
• get_jira_sync ~289 tokens
  How a project keeps its issues' statuses in step with its own Jira (see get_jira_link): 'direction' — 'off', 'both', 'from_jira' (Jira moves, the issue here follows) or 'to_jira' (the issue here moves, Jira follows); 'pairs' — which status here is which there, in order; 'actsFor' — the person whose
• get_legal_document ~423 tokens
  A legal act that issues or wiki pages you can read refer to, as it is kept here: title, publisher, 'state' (fresh, stale, waiting — named and not read yet, or unreachable), 'asOf' — the day its text is as of, how many issues and pages refer to it ('references': total, and 'hidden' of them where you
• get_linked_confluence_page ~370 tokens
  Read one page of the Confluence of a project's own Jira site — switched on beside the Jira (get_jira_connection's 'confluence') — on the project's token, as the agents read it: its title, space, the pages above it, its version and who changed it last, and its body as Markdown (cut at 12000 character
• get_linked_jira_comments ~304 tokens
  Read the comments of one issue of a project's own Jira (see get_linked_jira_issue), the newest first: who wrote each, when and what, and how many there are in all. Name the project by 'project', or an issue here by 'issue' — then its project's Jira is read, and the issue's own key there is the defau
• get_linked_jira_issue ~410 tokens
  Read one issue of a project's own Jira — the one its administrator connected (get_jira_connection) — on the project's token, as the issue screen and the agents read it: summary, type, status, priority, assignee, reporter, dates, labels, versions, parent, sub-tasks, links there and the description (c
• get_project_rule_runs ~317 tokens
  A project rule's journal, newest first: each time an issue entered the rule's state and matched its conditions — which issue, who moved it, and the outcome: 'applied' (checklist added), 'alreadyThere' (its marker line was already in the description, nothing added) or 'tooLong' (the description would
• get_source ~238 tokens
  One source of a project (see list_sources), with its journal: every change of how far it is checked — from what, to what, who and why — newest first, and when it was created and edited. Name it by 'id', or by 'project' and 'source' — its key, or any identifier it has in any shape: 'arXiv:2301.01234'
• get_started ~299 tokens
  What this company and one of its projects could still set up in the tracker, and what is set up already — call it when the person has just started or asks what else the tracker can do. Each step has 'id', 'scope' ('company' or 'project'), 'done', 'why' (one sentence) and 'how': the next move, either
• get_support_letter ~156 tokens
  Read one letter to the support address whole — the quoted thread and the signature that the request's comment leaves out, the HTML part as text, and the headers. 'letterId' comes from list_support_letters or from get_support_request's messages. A letter in a request is readable by whoever can read t
• get_support_request ~255 tokens
  Read who is behind a support request: the requester's name and email, whether they asked signed in (and from which workspace), their client version, what the product knew when they asked from inside it ('context': the screen, the client, the last refusal the server gave them with its request id), an
• get_wiki_attachment ~331 tokens
  Read one file attached to a wiki page — its bytes, base64-encoded — identifying the page by 'pageId' or by 'spaceKey' + 'title' and the file by 'filename' as get_wiki_page lists it. This is how a file is copied from one page to another: read it here, write it with add_wiki_attachment. The bytes trav
• get_wiki_page ~829 tokens
  Get one wiki page by id, or by space key + title, if it is visible to this token. Returns the page text, its labels, its parent and child pages, its comments, and the issues linked to it. Pass withMarkdown: true when you intend to edit it — you then get the page's Markdown source to change and hand
• get_wiki_page_approval ~269 tokens
  A wiki page's APPROVAL: which edition is in force. 'version' is the edition the page is at now and 'approved' whether that very edition is approved. 'inForce' is the newest edition somebody's approval stands on — its 'version', when it was written, when it was approved and 'by' whom (null: the page
• get_wiki_page_reading ~294 tokens
  A wiki page as REQUIRED READING: whether somebody is asked to read it and mark so. 'edition' is the version to read — the approved edition in force where the page has one (see get_wiki_page_approval), else the one its lead last asked about; null when the page is asked of nobody. 'required' says whet
• get_wiki_page_reviews ~298 tokens
  A wiki page's REVIEWS: who checked which version of it, and what they found. Each review has the 'version' its reviewer read, the 'reviewer' (and the 'agent' that read it for them, where one did), a 'verdict' — 'correct', 'gap' (something not argued), 'error', or null while under way — a 'summary',
• import_sources_bib ~464 tokens
  Read a BibTeX file's text against a project's register of sources. Without 'take' nothing is written: each entry comes back as an offer — 'new' (a source to add under the entry's key), 'fill' (the register already has the work by one of its identifiers: 'adds' lists the empty fields the entry would
• link_issues ~474 tokens
  Link two issues: link_issues('PM-419', 'PM-417', 'is blocked by') records that PM-419 is blocked by PM-417. 'type' is the PHRASE, said as a person says it — 'blocks', 'is blocked by', 'duplicates', 'is duplicated by', 'clones', 'relates to' — so the direction is in the words and the arguments cannot
• link_terms ~336 tokens
  Say how one term of a project stands to another (PM-1053): 'from' rests on 'to' ('dependsOn', the default), is a special case of it ('specialCaseOf'), or is its opposite ('oppositeOf'). 'state' 'confirmed' (the default) keeps the link — shown to readers beside the term and used for the order of read
• link_wiki_page ~289 tokens
  Link a wiki page to an issue. The link then shows on both the issue and the page, and survives the page being renamed or moved. Identify the page by 'pageId', or by 'spaceKey' + 'title'. Linking the same page again updates that link instead of adding a second one. Requires permission to edit the iss
• list_claims ~606 tokens
  A project's claims, each with its label (what a paper's \label and a citation name it by, e.g. 'thm:d5-rank5'), its number, its statement (Markdown with formulas), its status and what it rests on. A project writes them on one of two scales, answered as 'scale' with its 'statuses' and 'kinds': 'math'
• list_code ~180 tokens
  List a directory of a repository connected to a project. Only repositories whose owners opened them to agents can be read.
• list_computations ~300 tokens
  The computations issues rest on, as their runners reported them: state, progress, the commit and repository, the job's page and output, and what came of it. With 'key', one issue's; with 'projectKey', the project's, newest first and the ones still going on top — state 'open' (queued or running) is w
• list_credentials ~144 tokens
  List the credentials attached to an issue or a wiki page that this token may read — names and who attached them, never the values. Pass issueKey or pageId. Use reveal_credential to read one value, and only when you are about to use it.
• list_environments ~216 tokens
  A project's environments, in order, and its ten newest deployments. An environment is one of the places a project's work is put out to — 'dev', 'staging', 'prod' — in order; the LAST one is where finished work ends up. A deployment is a pipeline saying «this went out, there». Each issue it carried t
• list_issue_questions ~432 tokens
  Questions with answer options, in either direction: what is waiting on YOU to answer (role='to_me'), what YOU asked and are waiting on somebody for (role='asked'), or everything on one issue. This is how you find out whether the question you asked has been answered — poll it, since ask_issue_questio
• list_issue_schedules ~256 tokens
  A project's RECURRING ISSUES: issues it files by itself on a calendar — a monthly report, a quarterly review, a licence renewed every year. Each has the issue as words (summary, description, type, assignee, priority, labels), the cadence ('every' N of 'unit': week or month — 3 months is a quarter, 1
• list_join_requests ~164 tokens
  The requests of people outside the company to take part in a public project: who asked, what they wrote, when — those waiting first, then the last twenty decided. Approved, a person files issues and comments in that project and nothing else; they take no seat and see nothing else of the company. Onl
• list_legal_library ~168 tokens
  List the acts in the legal library — what this installation's agents have already read off the official sites: url, title, the day the text is as of (fetched_at), when the site last confirmed it (checked_at) and its length. Open where the company lets an agent role read laws.
• list_legal_references ~382 tokens
  The legal acts one issue or one wiki page refers to — in its own text and in the comments on it. Each reference: its 'id' (pass it to remove_legal_reference), where it stands ('in': issue, comment, page or wikiComment, with 'commentId'), the act ('document': id, url, sourceUrl, title, hasText, asOf
• list_mcp_connections ~89 tokens
  List the external MCP connections configured for a project. Auth tokens are never returned (only whether one is set).
• list_persons ~697 tokens
  A project's register of persons — the people its texts name — each with their spellings by script and form, each spelling's source and whether it is checked (see find_person), facts (born, died, wikidata, mathGenealogy, orcid, mrAuthor) the same way, and the project's note on why they are here. 'sta
• list_project_fields ~111 tokens
  The columns a project keeps about its issues: name, kind, and a list's options with their colours. Also the customfield_… name each one answers to, for searching by JQL. Any member may read them.
• list_project_presets ~136 tokens
  The ready-made projects a project can take in one action — today 'requirements', a register of what a company is obliged to do: an issue type, ten columns (the norm, the obligation, who answers, what proves it, when it is reviewed), a four-state workflow, the year's recurring compliance work and two
• list_project_rules ~627 tokens
  A project's rules: when an issue enters a state, a checklist from a template is appended to its description. A rule appends its checklist to an issue's description when the issue ENTERS the rule's state — from the board, the Jira API or update_issue alike. The block starts with a hidden marker line
• list_projects ~88 tokens
  List the projects visible to this token (a project-scoped token sees only its project). A project with a 'parent' is a subproject of that one: it has its own issues, board and wiki, and shares only who may reach it.
• list_repositories ~194 tokens
  The GitHub and GitLab repositories a project is connected to: each one's id, host, path and address, whether it is the project's open source repository (with the licence its host named and when that was last confirmed), whether a token is set (never the token), whether agents may read its code, and
• list_showcase ~245 tokens
  What a public project shows of the company's OTHER projects: issues and wiki pages shown there by reference, not copied — anybody who reads the public project reads them as they are now, while the rest of their project stays closed and their links to it are counted, never named. Each row: its id (fo
• list_sources ~426 tokens
  A project's sources — the papers, books and preprints its pages cite — each with its key (what a page cites it by, e.g. 'IMP26', a BibTeX key), its authors (the name as the work prints it, and 'personId'/'person' where it is a person of the project's register — 'hidden' where you may not see that pe
• list_support_letters ~211 tokens
  List letters to the support address that did not become part of a request: 'held' (looked like spam, or too many at once from one address or on one request), 'failed' (we could not file them), 'ignored' (an autoresponder, a bounce, a mailing list, our own letter), 'dismissed'. Without 'state', held
• list_support_queue ~375 tokens
  The support desk's queue: open requests, the most urgent first — overdue, then due soonest, then those waiting on their requester. Each item says whose turn it is ('clock.turn': 'first' = nobody has answered yet, 'reply' = the requester wrote again, 'requester' = we answered last and the clock is st
• list_terms ~537 tokens
  A project's terms: each word, its other spellings, its short definition, its kind, and its source (a wiki page or an issue, with the heading on it). 'state' is 'confirmed' (shown to readers, marked in texts), 'proposed' (found on a page by its markup or by the model, waiting for a person — set_term
• list_tracks ~158 tokens
  The tracks a project is cut into: a track is a LABEL the project declared meaningful — a play, a campaign, a rollout — and work joins one by carrying that label. A track has no key of its own; its issues keep the project's key, which is what makes it a different thing from a subproject (a separate p
• list_users ~278 tokens
  List the people you can assign work to or mention: the members of the projects this token can see. Optionally filter by free text (username, display name or email) or narrow to one project. Mention someone in a description or comment as [~username] — a mention matches the username, never the display
• list_versions ~315 tokens
  A project's versions, in their sequence. A version is what a project's work goes out in — '2.4.0', 'Autumn'. It is the project's own: an issue carries versions of its own project only, any number of them ('fixVersions' on create_issue, update_issue and get_issue; JQL 'fixVersion = "2.4.0"', 'fixVers
• list_wiki_embeds ~234 tokens
  The scenes of a wiki page — or of every page of a space you may edit — put on other sites (PM-1076): for each, its id, the block ('language' anim or anim-js and its number among that kind's blocks, as get_wiki_page's 'anims' numbers them), the link and the ready <iframe> code, the caption, the sites
• list_wiki_labels ~126 tokens
  The labels of one wiki space with how many pages carry each, most used first — counted over the pages visible to this token. `service` marks a label that does a job rather than describe a page ('template'). search_wiki with `label` lists a label's pages.
• list_wiki_spaces ~57 tokens
  List the wiki spaces visible to this token. Every project has exactly one space, keyed like the project.
• local_files_setup ~190 tokens
  How the person connects pm-files — a small local MCP server that attaches files from their own computer to issues and wiki pages by path, and saves attachments back to files, so no bytes pass through the conversation. Call it when you need a local file (a screenshot, a document, anything past the ba
• mark_wiki_page_read ~225 tokens
  Mark a wiki page as READ, IN YOUR OWN NAME: «I have read this edition». 'version' is the edition you read and must be the one get_wiki_page_reading gives as 'edition' — the call is refused when the edition to read is another one. Only for somebody the page is required reading for. The mark is a line
• merge_persons ~261 tokens
  Merge one person of a project's register into another when they are one human being — «Sjorgren» into «Sjogren». ASK the person first, naming both as list_persons shows them: 'similar' there is only a hint. Nothing is removed: the one merged keeps their spellings and facts with their sources, and fr
• merge_terms ~346 tokens
  Join one term to another of the same project when they are one notion — «Размерные подгруппы» into «Размерная подгруппа». The joined term's name and spellings become the target's variants (so the reading does not offer that spelling again), its links move to the target, and the joined term is gone;
• move_issue ~387 tokens
  Move an issue into another project, taking its comments, history, attachments, links and sub-tasks with it. The key does NOT change: 'PM-12' stays 'PM-12' wherever it lives, so every existing link and branch name goes on working. Call it with apply=false first (the default): the answer says what the
• pdf_page_image ~534 tokens
  A page of a PDF attached to an issue or a wiki page, as a picture you can look at — whole, or only the part 'box' names — drawn on the server, so nothing has to be installed on your side. Use it to read what a PDF's extracted text loses: superscripts, formulas, tables, diagrams. Name the issue by 'k
• product_help ~299 tokens
  How the TRACKER ITSELF works — not what is in anybody's project: what a feature does, where it is on the screen, who may use it, and what the product does not do. Use it when the person asks about the tool ('how do sprints work here', 'where do I switch on due reminders', 'can a wiki page be restric
• read_code ~173 tokens
  Read one file from a repository connected to a project. A long file arrives cut and says so; generated and binary files are not read.
• read_page_literature ~381 tokens
  Read a wiki page's hand-written «Literature» list (the section headed Литература, Literature, References or Bibliography) against its project's register of sources. Without 'take' nothing is written: each line comes back with what was read of it — its key in front ('[IMP26] …'), arXiv id, DOI, MR, z
• release_version ~423 tokens
  Mark a version released — or, with released=false, take the mark back. A version is what a project's work goes out in — '2.4.0', 'Autumn'. It is the project's own: an issue carries versions of its own project only, any number of them ('fixVersions' on create_issue, update_issue and get_issue; JQL 'f
• remove_from_showcase ~176 tokens
  Stop showing one row of a public project's showcase (its id from list_showcase): from the next request the issue or page is closed to everybody outside its own project again. Nothing is deleted but the row. The owner of the project it belongs to or an administrator of the public project may; written
• remove_legal_reference ~174 tokens
  Take a legal reference off an issue or a wiki page, by the 'id' list_legal_references gave it — as «Remove» in the block «Legal acts» does. A reference read from words that still stand in the text is kept as a «no» ('keptAsRefused' true, its state 'rejected'), so the next save does not put it back;
• remove_track ~202 tokens
  Undeclare a track. THE LABEL STAYS ON THE WORK: what goes is the declaration, so the issues keep their tag and declaring the track again brings exactly the same ones back. Nothing here can lose work — but the name, icon and place ARE lost, and the track's issues count as 'outside every track' afterw
• reply_to_requester Sends messages · ~222 tokens
  Write to the person who opened a support request. The text becomes a comment the requester can read on their page and is emailed to them — unlike add_comment, which is always internal and never reaches the requester. Write it to the customer, in their language (get_support_request says which). Requi
• report_agent_usage ~648 tokens
  Record what one agent run cost an issue (local or mirrored/upstream): tokens by kind and machine time. Re-sending the same 'source' + 'externalId' updates that record instead of adding a second one, so a retry never doubles the spend. Omit a metric you did not measure — omitted is 'not reported', wh
• report_computation ~849 tokens
  Say how a computation an issue rests on stands — a GAP run, a batch of work units, a Lean build that ran somewhere else; the tracker runs nothing. Call it when the job is submitted, as it progresses and when it ends, with the same 'source' + 'externalId' every time: that is one job, updated, never a
• report_deployment ~827 tokens
  Say that something was deployed to one of a project's environments — the call a pipeline step makes. An environment is one of the places a project's work is put out to — 'dev', 'staging', 'prod' — in order; the LAST one is where finished work ends up. A deployment is a pipeline saying «this went out
• report_lean_audit ~438 tokens
  Report what a CI's `#print axioms` said of Lean declarations in one repository of the project at one commit: pass Lean's output as it printed it in 'output' (lines like "'D5.rank5' depends on axioms: [propext, Classical.choice, Quot.sound]" and "'X' does not depend on any axioms"), or 'declarations'
• reveal_credential ~175 tokens
  Read one credential's value, by the id from list_credentials. This is the same act as pressing reveal on the screen and carries the same cost: it is recorded against the token you are using, and the person who owns the secret can see that you read it. Call it when you are about to use the value, not
• review_wiki_page ~573 tokens
  REVIEW a wiki page — a proof, an argument — in your person's name, on the version you read: 'version' is the page's version as get_wiki_page gave it, refused if the page has been edited since. 'verdict' is 'correct', 'gap' or 'error' (leave it out while the review is under way, and give it later wit
• search_code ~292 tokens
  Find where a string appears in the code of the repositories connected to a project, with the file, the line number and the lines around it. Only repositories whose owners opened them to agents are searched, and the answer says when what it searched was out of date.
• search_issues ~1244 tokens
  Search the issues visible to this token, with a JQL query — the same JQL the Jira REST surface takes, read by the same parser. A query naming a field this tracker does not have is REFUSED and named, never run: it would match everything and read as an answer. Without `jql`, the shorthand arguments fi
• search_legal_library ~201 tokens
  Search the laws, regulations and standards this installation's agents have already read off the official sites (EUR-Lex, legislation.gov.uk, Fedlex, FATF and others) — by words and by meaning. Not a web search. Each hit: the act's url, title, the day its text is as of, an offset into the text and a
• search_linked_confluence ~349 tokens
  Search the Confluence of a project's own Jira site (see get_linked_confluence_page) with CQL, as its own search does — e.g. 'type = page AND text ~ "onboarding" ORDER BY lastmodified DESC', 'space = ENG AND title ~ "release"', 'parent = 123456'. Answers each page's confluence_page_id, confluence_url
• search_linked_jira ~349 tokens
  Search a project's own Jira (see get_linked_jira_issue) with JQL, as its own search does — e.g. 'project = ACME AND status != Done ORDER BY updated DESC', 'text ~ "login"'; currentUser() is the project token's owner, not you. Answers each issue's jira_key, jira_url, summary, type, status, priority,
• search_wiki ~308 tokens
  Search wiki pages visible to this token by free text: by words in any form and by meaning (where the server has its embedding model), and literally — the title, the body, the labels written on an attached SVG diagram. Best match first; `match` says what found each page. `files` are PDF and Word file
• set_claim ~946 tokens
  Add a claim to a project's register, or change one — its kind, label, number in the paper, title, statement or bases. A claim is named by 'id', or by 'project' and 'label': one that does not exist yet is created (with 'statement'; 'status' says how far it is proved from the start, 'open' if left out
• set_claim_scale ~446 tokens
  Choose the scale and kinds a project's claims are written on: 'math' (theorem, lemma, proposition, corollary, conjecture, question; open, paper, computer, lean, refuted, retracted) or 'law' (position, conclusion, risk, obligation; draft, agreed, practice, disputed, outdated). Free while the project
• set_claim_status ~383 tokens
  Move a claim on its project's scale — open, paper, computer, lean, refuted, retracted on 'math'; draft, agreed, practice, disputed, outdated on 'law' — with the ground it moved on in 'reason' (a merge, a computation that finished, a reviewer's word, the issue it was decided in). 'lean' is refused un
• set_environments ~353 tokens
  Make a project's environments exactly this list, in this order — the last is where finished work ends up. An environment is one of the places a project's work is put out to — 'dev', 'staging', 'prod' — in order; the LAST one is where finished work ends up. A deployment is a pipeline saying «this wen
• set_issue_fields ~299 tokens
  Fill in a project's own columns on one issue, by their NAMES: 'Segment=AI; Country=Poland; Started=2026-08-01', or a JSON object. A country column takes the country's name or its two-letter code. A link column takes issue keys, wiki pages (a page's address or page:471) and claims (a label like thm:m
• set_issue_schedule ~790 tokens
  Add a recurring issue to a project, or change the one named by 'id' — the WHOLE of it as you write it here: what you leave out of a change is cleared, not kept. From 'nextDay' on, every 'every' weeks or months, the project files this issue at nine in the morning on YOUR clock and in YOUR name: with
• set_jira_connection ~309 tokens
  Switch a project's Jira connection on or off, keeping its token — and, with 'confluence', whether the same site's Confluence is read too. Off, nothing reads that Jira or writes to it — the issue screen, the agents, the status sync — and issues keep their keys there. Switched on, the held token is as
• set_jira_link ~207 tokens
  Say which issue of the project's own Jira this issue is: its key (ACME-123) or its link on the site. The key is asked of that Jira first — one it does not have, or the token cannot see, is refused. An empty 'jiraKey' removes the link. One Jira issue per issue; the change is a line in the issue's his
• set_jira_sync ~411 tokens
  Set how a project keeps its statuses in step with its own Jira: the direction and the pairs of statuses. Either left out keeps what is there. Moves on either side go through that side's own workflow and are never forced: a move one refuses is left undone and said on the issue (get_jira_link's 'sync'
• set_person ~731 tokens
  Add a person to a project's register, or change the one named by 'id': add spellings and facts, remove them, change the name shown or the note, and confirm or reject a proposed person with 'state'. A spelling or fact given with 'source' (the page, issue or comment you READ it in: 'page:471', 'PM-12'
• set_project_field ~624 tokens
  Add a column to a project, or edit the one that already has this name. Keyed by name rather than by id: 'make sure there is a Segment field with these options' is the request, and a name is what you just read. A field's KIND cannot be changed once it exists. Project lead or admin only.
• set_project_issue_type ~263 tokens
  Add an issue type of this project's own — e.g. 'Показ' — or rename one it already has. Keyed by name. The shared types (Epic, Story, Task, Bug, Sub-task, Client) are every project's and cannot be renamed here. Another project never sees this type. Project lead or admin only.
• set_project_parent ~273 tokens
  Make an existing project a subproject of another, or take it back out with an empty parentKey. This is about ACCESS, not about names or issues: everyone who may reach the parent may reach the subproject too, in the role they hold there. Nothing is renamed, no issue moves, and the keys stay ordinary
• set_project_public ~427 tokens
  Open a project to be READ by anybody — nobody signed in, or somebody who does not work in the company — or close it again. Opened, its board, issues, comments, attached files and wiki can be linked to from anywhere; nobody outside can write in it, people's email addresses are never shown, and the co
• set_repository_open_source ~281 tokens
  Mark a repository already connected to a project as the project's open source repository, or take the mark off. Marking asks its host, without a token, whether anybody can read it and under which licence, and is refused for a private one. Taking the mark off the last marked repository of a public pr
• set_source ~1039 tokens
  Add a source to a project's register, or change one — its key, authors, title, year, venue, identifiers or PDF — or say how far it is checked. A source is named by 'id', or by 'project' and 'key': one that does not exist yet is created (with 'title'), unchecked. A field left out keeps its value and
• set_term ~548 tokens
  Add a term to a project, or change the one named by 'id' — and confirm or reject a proposed one with 'state'. On a change, what you leave out stays as it is. A term written here is confirmed at once. 'variants' REPLACES the other spellings: send all of them — for a word that declines, the forms runn
• set_track ~639 tokens
  Declare a track on a project, or edit the one that already has this tag. The tag is the LABEL issues carry to join it ('cherry-orchard'), so it cannot contain a space — labels are stored space-separated. The name is what a reader sees ('The Cherry Orchard'); leave it out and the tag speaks for itsel
• set_wiki_page_readers ~453 tokens
  Say whom a wiki page is REQUIRED READING for, and tell them. The three arguments together are the WHOLE list and replace the one before — read it with get_wiki_page_reading first and pass back what should stay. 'users' is usernames or e-mails as 'a,b' (each must be able to read the page); 'members:
• site_traffic ~489 tokens
  How a project's website was visited, from the service that counts it: Google Search Console (clicks, impressions, ctr, position by query, page, country, device or date), Vercel Web Analytics (visitors and page views by page, referrer, source, country, device or date) or Google Analytics 4 (sessions,
• take_project_preset ~478 tokens
  Give a project a ready-made setup (see list_project_presets) — only what it does not already have: a column, a type, a recurring issue or a page of the same name is left as it is, so taking it twice adds nothing. The workflow is taken only by a project with no issues whose states are still the ones
• term_graph ~358 tokens
  What a project's terms rest on (PM-1053): its confirmed terms and its parent projects', the links between them, and 'order' — the terms in the order to read them, each after what it rests on, the ones resting on nothing first — with 'circles', terms whose definitions rest on each other (worth puttin
• unlink_issues ~294 tokens
  Remove a link between two issues: name both ends (and, when more than one link joins them, the phrase — 'blocks', 'relates to'), or give the 'linkId' get_issue returned. Ambiguity is refused rather than guessed: two issues joined twice and no phrase given comes back with the links listed. Requires p
• unlink_wiki_page ~202 tokens
  Remove the link between an issue and a wiki page. Identify the page by 'pageId', or by 'spaceKey' + 'title'. Requires permission to edit the issue. The page itself is not touched.
• unmerge_person ~158 tokens
  Undo merge_persons: the person merged is a person of their own again, with every spelling and fact they had. Name them by their own id — 'merged' in list_persons lists them under the person they were merged into. Ask the person first. Both journals keep a line. Members of the project who may write o
• update_comment ~701 tokens
  Edit a comment on an issue: pass 'body' to replace the whole of it, or 'edits' to change part of it — exact find-and-replace against the comment as get_comments hands it back, each 'oldText' occurring exactly once. One body axis per call. With 'edits' the answer says where each one landed rather tha
• update_credential ~363 tokens
  Change a credential, by the id from list_credentials: its name, its value, or who may read it — each on its own, and only what you pass is touched, so taking somebody off the list never needs the value. 'readers' REPLACES the list; noReaders: true empties it. Only the person who attached it and the
• update_issue ~1229 tokens
  Update an issue: any of summary, description, type, assignee, priority, labels, dueDate, parentKey, fixVersions, or status (which performs the transition, and fires the project's rules — a rule may append a checklist to the description, in which case 'description' is listed in 'changed'). Only the f
• update_project_rule ~1333 tokens
  Change a project rule, by its id from list_project_rules. Only what you pass changes: pass just 'enabled' to switch a rule on or off, or any of the others to edit it. An empty string for 'type' or 'label' removes that condition; an empty 'fromStatus' or 'branch' removes that one too; for a duty, an
• update_version ~455 tokens
  Change a version: its name, description, days, or whether it is archived. Only what you pass is changed. A version is what a project's work goes out in — '2.4.0', 'Autumn'. It is the project's own: an issue carries versions of its own project only, any number of them ('fixVersions' on create_issue,
• update_wiki_comment ~874 tokens
  Edit a comment on a wiki page — your own, or anyone's with full write access in that project. Read it first with get_wiki_page(withMarkdown: true), which gives each comment its 'markdown' and 'version'. Pass 'markdown' to replace the whole comment, or 'edits' to change part of it (exact find-and-rep
• update_wiki_embed ~261 tokens
  Change an embed of a wiki page's scene (PM-1076) — its caption, the sites that may frame it, its term — keeping its link, so the sites that have it keep working. Only what you pass changes: an empty caption takes it off, an empty 'sites' allows any site, days 0 removes the term. Only for somebody wh
• update_wiki_page ~1544 tokens
  Edit a wiki page: retitle it, change its body, move it under another parent (or to the top of its space), or set its labels. Identify it by 'id', or by 'spaceKey' + 'title'. To change part of the body, pass 'edits' (exact find-and-replace on the Markdown source, each 'oldText' occurring exactly once
• upsert_mcp_connection ~406 tokens
  Admin only: create or update a project's external MCP connection. Pass 'id' to update an existing one (omit to create). 'token' is stored server-side and never returned; omit it to keep the current token when updating. The assistant panel calls the server's read-only tools (readOnlyHint) directly an
• withdraw_issue_question ~158 tokens
  Take back a question you asked, when it no longer needs answering — you worked it out, or the task moved on. The comment stays in the thread (the conversation happened) and the question stops counting on the other person's list. The person who asked, or anybody with full write access in the project.
• withdraw_wiki_page_approval ~267 tokens
  Take an approval of a wiki page back: your own, or — the project's lead — somebody else's ('who'). Without 'version' it is the newest edition that person's approval stands on. Nothing is deleted: a 'withdrawn' line is added to the page's journal after the approval it answers, with your note. If nobo

Browse

• Website screenshots
• PDF tools
• Converting to Markdown
• Email

Related MCP servers

• emdly
  Search, install and submit Markdown skills for AI agents; private Brain files when signed in.
• Qretro Retro
  QRetro retrospectives and planning poker over MCP: boards, action items, poker games, estimates.
• Linear MCP by usefulapi
  Search, read and create Linear issues, projects, teams and cycles.
• Nyuchi Docs
  Search, read, and ask the Nyuchi docs (docs.nyuchi.com); send feedback or raise issues.
• ecomdly
  E-commerce skills for AI agents: feeds, Google Shopping, GA4. Your private Brain when signed in.
• EcoCarbonWiki
  Read-only MCP for the Eco game wiki: search, Markdown pages, and wiki_* lookups. No keys, no writes.
• Vinktar
  Error tracking for small teams and their coding agents.
• SHIP
  Assign Linear, Jira or GitHub issues to an AI coding agent team that plans, builds, reviews, tests.

Badge for your README

[![AptLynx](https://aptlynx.net/badge/tech.kaiku/kaiku.svg)](https://aptlynx.net/servers/tech.kaiku/kaiku)

Listing text is written by the maker; AptLynx lists tools and does not vouch for them. Find another tool · Browse by topic · For agents