{"id":"tech.kaiku/kaiku","slug":"tech-kaiku-kaiku","title":"Kaiku","description":"Issue tracker and wiki for teams and their agents; answer your agents' questions from your phone.","version":"1.3.1","publisher":{"kind":"domain","id":"kaiku.tech","label":"kaiku.tech","url":"https://kaiku.tech"},"website":"https://kaiku.tech/en/docs/mcp?utm_source=mcp-registry","repository":"","remotes":[{"type":"streamable-http","url":"https://app.kaiku.tech/mcp"},{"type":"streamable-http","url":"https://mcp.kaiku.tech/mcp","headers":[{"description":"Leave empty to sign in through the browser (OAuth); or Bearer <token> made in Settings → Connect over MCP; the token says which workspace","isSecret":true,"name":"Authorization"}]},{"type":"streamable-http","url":"https://{workspace}.kaiku.tech/mcp","headers":[{"description":"Leave empty to sign in through the browser (OAuth); or Bearer <token> made in Settings → Connect over MCP","isSecret":true,"name":"Authorization"}],"variables":{"workspace":{"description":"Your workspace: the company name in front of kaiku.tech in the address you sign in at","isRequired":true}}}],"packages":[],"published":"2026-11-04","updated":"2026-11-04","status":"online","auth":"","latency_ms":1438,"checked":"2026-11-19","uptime":100,"checks":3,"tools":[{"name":"add_attachment","title":"Add attachment","description":"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 — is better attached by path through the pm-files MCP server than typed out as base64; local_files_s","read_only":false},{"name":"add_comment","title":"Add comment","description":"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 that project (read-only members cannot). Answers with 'notified' (who this actually reaches, the ans","read_only":false},{"name":"add_legal_reference","title":"Add legal reference","description":"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 false at first. 'place' is the place in the act in words («Article 18»). With 'commentId' the referenc","read_only":false},{"name":"add_to_showcase","title":"Add to showcase","description":"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 closed, and its links to other closed things are counted, never named. A claim is shown with its stateme","read_only":false},{"name":"add_wiki_attachment","title":"Add wiki attachment","description":"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 this call cannot leave two copies. A file on the person's own disk — a screenshot, a PDF — is better at","read_only":false},{"name":"add_wiki_comment","title":"Add wiki comment","description":"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 'spaceKey' + 'title'. Markdown is rendered; mention someone as [@Their Name](user:username), the wik","read_only":false},{"name":"admin_bank_transfer","title":"Admin bank transfer","description":"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 customer pick a transfer right now»: it is switched on AND carrying everything a payment needs, which is no","read_only":true},{"name":"admin_errors_week","title":"Admin errors week","description":"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 project the collector did not answer about has null counts and a reason, never zeros. Ask for an earl","read_only":true},{"name":"admin_funnel","title":"Admin funnel","description":"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, 'revenue' is what actually arrived inside the period. Each carries its own currency. Figures come from the ","read_only":true},{"name":"admin_invoices","title":"Admin invoices","description":"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 ledger, so 'machines' says how current each machine's copy is. One invoice's delivery record belong","read_only":true},{"name":"admin_landing_week","title":"Admin landing week","description":"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.","read_only":true},{"name":"admin_list_feature_flags","title":"Admin list feature flags","description":"Administrators only: the feature flags, as the console's Features screen shows them. Every declared flag with its kind ('rollout' — a feature on its way out, to be deleted once on for everyone; 'capability' — something a company may have taken away), its declared default, its description, and the answer for everyone ('*'). Ask with 'workspace' to read the flags for one company, narrowest first: 'o","read_only":true},{"name":"admin_load","title":"Admin load","description":"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 translation over a rolling window, with totals and breakdowns by feature, by model and by day; costs are est","read_only":true},{"name":"admin_overview","title":"Admin overview","description":"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 zero, when a machine of the fleet did not answer: 'fleet' says which machines were asked and which are ","read_only":true},{"name":"admin_set_bank_transfer","title":"Admin set bank transfer","description":"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 you are not changing. Switching the method on is refused while anything a payment needs is missing ","read_only":false},{"name":"admin_set_feature_flag","title":"Admin set feature flag","description":"Administrators only, and this one CHANGES things: answer one feature flag for one company, or for everyone with '*' — exactly what the console's Features screen does. 'enabled' is true (on), false (off — a decision that overrules everyone's answer for this company) or null (take the answer away, so the wider scope decides again: the company falls back to '*', '*' falls back to the declared default","read_only":false},{"name":"admin_set_workspace_ours","title":"Admin set workspace ours","description":"Administrators only, and this one CHANGES things: mark a company as one of ours — our own, a test somebody here made — or take the mark off. The funnel's 'firstSession' leaves our companies out, so that 'external' means somebody who came from outside. A company that is not billed, or the demo, is ours whatever the mark says. Answers the company's row with 'ours' and 'oursBy' (marked, not-billed, d","read_only":false},{"name":"admin_workspace_journal","title":"Admin workspace journal","description":"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 nobody paid for'. The actor is our own operator, and is named because an entry without one answers ","read_only":true},{"name":"admin_workspaces","title":"Admin workspaces","description":"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 that soon, which is how 'whose trial ends this week' is answered in one call. 'attention' is the conso","read_only":true},{"name":"answer_issue_question","title":"Answer issue question","description":"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 replaces whatever the deadline took, and the change is recorded. The answer is written into the thre","read_only":false},{"name":"answer_review_remark","title":"Answer review remark","description":"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 reviewer — or the project's lead — 'action': 'reopen' puts a remark said fixed back as standing, 'wi","read_only":false},{"name":"approve_reconfigurations","title":"Approve reconfigurations","description":"An administrator's word that one week may have more reconfigurations than the ceiling: up to 'count', or as many as it has now. Every later write of that week — a bot's too — is held to it. Only somebody who configures the project.","read_only":false},{"name":"approve_wiki_page","title":"Approve wiki page","description":"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 is never edited or deleted (withdraw_wiki_page_approval adds a line that takes it back). A later edit","read_only":false},{"name":"archive_issues","title":"Archive issues","description":"Archive issues — put finished work on the shelf so boards and searches show what is still live. Nothing is deleted: an archived issue keeps its key, history and comments, search_issues finds it with `archived in (true, false)`, and unarchive_issues brings it back. Only issues in a done status may be archived, exactly as on the board; any other is refused and named with the state it stands in (\"not","read_only":false},{"name":"archive_project","title":"Archive project","description":"Archive a whole project whose work is finished. It becomes read-only for everybody (like a pause) and leaves the lists: list_projects and the project switcher no longer show it, and search_issues counts its issues as archived — `project = AN` answers empty with archivedLeftOut, `archived in (true, false)` includes them. It stays readable by its link and through list_projects with includeArchived, ","read_only":false},{"name":"ask_issue_question","title":"Ask issue question","description":"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 in their Questions list until they answer. It does not wait for ever — give 'defaultOption' and the ","read_only":false},{"name":"ask_wiki_page_approval","title":"Ask wiki page approval","description":"Name the people who may approve a wiki page — or, with signatures: true, ask them to SIGN it — 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 'who' are taken OFF the list instead; what they al","read_only":false},{"name":"check_checklist_item","title":"Check checklist item","description":"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 lost. Ticking a ticked item changes nothing ('changed' false). An id that finds nothing means the item ","read_only":false},{"name":"check_source","title":"Check source","description":"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' (checked by a service) and takes the † off; a service disagreeing or not having the work makes it 'mi","read_only":false},{"name":"cite","title":"Cite","description":"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 bibliography prints (with † while it is unchecked or disagrees with what it names), and its BibTeX entry fo","read_only":true},{"name":"claim_team_roles","title":"Claim team roles","description":"Mark team roles as a person's own, the way they do it on the board's sheet: a role without 'needsApproval' is held at once; a role with it becomes a request the board's administrators confirm or decline (they are told) and counts nowhere until then — even when you, marking for somebody, are an administrator: giving outright is give_team_role. 'roles' are names as 'a,b'. With 'replace': true the li","read_only":false},{"name":"code_calls","title":"Code calls","description":"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 choose from.","read_only":true},{"name":"code_symbols","title":"Code symbols","description":"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.","read_only":true},{"name":"computation_hours","title":"Computation hours","description":"What a project's computations spent over a period — the machine-hours of its stats screen: CPU-hours measured and core-hours allocated in total, by machine, by week (weeks begin on Monday) and the issues that spent most, and how many jobs finished done, failed, cancelled or lost in it. Only the time inside the period counts: a job that ran across its edge is cut there in proportion, and a job stil","read_only":true},{"name":"connect_repository","title":"Connect repository","description":"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, with the screen to connect it on with a token. With openSource: true it is also marked as the projec","read_only":false},{"name":"copy_pdf_to_wiki","title":"Copy pdf to wiki","description":"Copy a PDF from another site onto a wiki page by its link — an article a conspectus cites, kept here in case it disappears there. The server fetches it: an https address on the public internet only, a PDF by its bytes, at most 50 MB. The copy is attached to the page (pageId, or spaceKey + title) under 'filename' or the address's own name, with where it came from and when; the page's history says w","read_only":false},{"name":"create_chat","title":"Create chat","description":"Open a chat. kind 'direct': the chat with one colleague ('with') — there is one per pair, so an existing one is found rather than made ('created' false). kind 'group': a group with a title and its members, you its administrator. kind 'agent': a chat of your own with one of the company's agents ('agent', e.g. 'product'), found if you have one. Only the company's own people. A project's chat is neve","read_only":false},{"name":"create_claim_embed","title":"Create claim embed","description":"Put one claim of a project on other sites (PM-1165, PM-1166): a link anybody can open with no account, which shows its kind, number, title, statement with its formulas and status — never its bases, journal or review — and, while the project is public, the page it rests on. Answers with the ready code: 'script' once per page and 'mark' around the words on the site, which open the claim in a cloud, ","read_only":false},{"name":"create_credential","title":"Create credential","description":"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 people in 'readers', and by the project's lead, who reads every secret in the project — and by nobody el","read_only":false},{"name":"create_embed_set","title":"Create embed set","description":"Put a list of a project's terms and claims on other sites under ONE link (PM-1167) — for an article that cites many: the site puts 'script' in once and marks its words by name, <span data-kaiku-term=\"kernel\"> or data-kaiku-claim=\"thm:d5-rank5\", each opening its cloud. Only what the list names goes out, each thing as its own link would show it; a name not on it says so and nothing of the project. T","read_only":false},{"name":"create_issue","title":"Create issue","description":"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 'as' — never yourself) and 'unresolvedMentions' (what looked like a mention and reached nobody, eac","read_only":false},{"name":"create_issue_from_chat_message","title":"Create issue from chat message","description":"Make an issue of a message in one of the company's chats — or of a thread of them — in one step, as the screen's «Make an issue» does (PM-1237). The description quotes the messages (who wrote each and when) unless you give your own, and always ends with a link back to the message, which opens only for the chat's people; the messages' files are copied onto the issue; the message shows «→ KEY» to wh","read_only":false},{"name":"create_project","title":"Create project","description":"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 shows in every issue key, link and commit, and renaming it later costs more than creating the project di","read_only":false},{"name":"create_project_rule","title":"Create project rule","description":"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-rule:<id>)'; while that line is in the description, entering the state again adds nothing (the journal","read_only":false},{"name":"create_term_embed","title":"Create term embed","description":"Put one confirmed term of a project on other sites (PM-1165, PM-1166): a link anybody can open with no account, which shows the term's word, its definition with its formulas and — while the project is public — where it is defined; nothing else of the project. Answers with the ready code: 'script' once per page and 'mark' around the words on the site, which open the term in a cloud, or 'iframe', a ","read_only":false},{"name":"create_version","title":"Create version","description":"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.4.0\"', 'fixVersion in unreleasedVersions()'). The name is unique in its project, whatever the case. ","read_only":false},{"name":"create_wiki_embed","title":"Create wiki embed","description":"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> to paste into a site. The block is named by 'language' (anim, or anim-js where the company has sce","read_only":false},{"name":"create_wiki_page","title":"Create wiki page","description":"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 notifies, not the [~username] used in issues; link another page as [text](page:Title) or [text](pag","read_only":false},{"name":"decide_join_request","title":"Decide join request","description":"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 person is told by email either way, and the decision is written to the company's journal. Only the p","read_only":false},{"name":"decide_persons","title":"Decide persons","description":"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 first. Members of the project who may write only. Only where the company's plan includes AI.","read_only":false},{"name":"decide_support_letter","title":"Decide support letter","description":"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 files are dropped and the row is deleted with the other unfiled letters after 30 days. Requires full wr","read_only":false},{"name":"decide_team_role_request","title":"Decide team role request","description":"Confirm or decline somebody's request for a team role that needs an administrator's yes (list_team_roles shows who waits under each role). 'decision': 'approve' — they hold the role from now, at the back of its holders; 'reject' — the request goes. They are told either way, and it is written to the board's journal. The board's owner and its administrators only.","read_only":false},{"name":"decide_terms","title":"Decide terms","description":"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 different now (somebody decided some, or the page was read again), nothing is written and the answer says","read_only":false},{"name":"define_term","title":"Define term","description":"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 it is defined (a wiki page or an issue, and the heading on it) and the other ways it is written, and","read_only":true},{"name":"delete_agent_usage","title":"Delete agent usage","description":"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.","read_only":false},{"name":"delete_attachment","title":"Delete attachment","description":"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.","read_only":false},{"name":"delete_calendar_event","title":"Delete calendar event","description":"Remove an event from a project's calendar — every occurrence of it, and every change of one. To take out a single occurrence, cancel it with set_calendar_occurrence instead. Anybody who may write in the project.","read_only":false},{"name":"delete_calendar_pause","title":"Delete calendar pause","description":"Lift a pause or a day off of a project's calendar: its occurrences are back, each as its rule and its own changes say. Anybody who may write in the project.","read_only":false},{"name":"delete_chat_message","title":"Delete chat message","description":"Delete a message you wrote, as the screen does: its words and files are gone for everybody, and the message stays in its place as «deleted» so the replies to it still point somewhere. Cannot be undone. Only your own message.","read_only":false},{"name":"delete_claim","title":"Delete claim","description":"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 deleted: set_claim_status 'refuted' or 'retracted' keeps it said. Members of the project who may write onl","read_only":false},{"name":"delete_computation","title":"Delete computation","description":"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.","read_only":false},{"name":"delete_credential","title":"Delete credential","description":"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.","read_only":false},{"name":"delete_issue_schedule","title":"Delete issue schedule","description":"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.","read_only":false},{"name":"delete_machine_price","title":"Delete machine price","description":"Remove one row of the machines' price list, by the id list_machine_prices gives — a price entered by mistake. The days it priced fall back on the row before it, or on no price. To change a price from a day on, set_machine_price a new row instead: that keeps the history. The company's owner and administrators only.","read_only":false},{"name":"delete_person","title":"Delete person","description":"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 PROPOSED person use set_person with state 'rejected' instead, so they are not proposed again. Members ","read_only":false},{"name":"delete_project_field","title":"Delete project field","description":"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.","read_only":false},{"name":"delete_project_issue_type","title":"Delete project issue type","description":"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.","read_only":false},{"name":"delete_project_rule","title":"Delete project rule","description":"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.","read_only":false},{"name":"delete_registry_embed","title":"Delete registry embed","description":"Take a term's, a claim's or a set's link down (PM-1168): it answers 404 at once on every site that has it — the clouds and cards there say the thing is not available. It cannot be undone; a link made again is a new one. Only for somebody who may write in the project; a line in its history.","read_only":false},{"name":"delete_resource","title":"Delete resource","description":"Remove a resource from a project; the events that took it no longer do. Anybody who may write in the project.","read_only":false},{"name":"delete_source","title":"Delete source","description":"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_source 'check' 'mismatch' with the reason keeps it said. Members of the project who may write only.","read_only":false},{"name":"delete_term","title":"Delete term","description":"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 again; a deleted one may be found and proposed anew. Members of the project who may write only.","read_only":false},{"name":"delete_wiki_attachment","title":"Delete wiki attachment","description":"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.","read_only":false},{"name":"delete_wiki_embed","title":"Delete wiki embed","description":"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.","read_only":false},{"name":"delete_wiki_page","title":"Delete wiki page","description":"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.","read_only":false},{"name":"distinct_persons","title":"Distinct persons","description":"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 names. A person merged into another answers as the one they were merged into. merge_persons on such a pa","read_only":false},{"name":"edit_chat_message","title":"Edit chat message","description":"Change the words of a message you wrote, as the screen's «Edit» does: it says «edited», the chat's open screens show the new words at once, and nobody is told anew — a mention added by an edit notifies nobody. Only your own message, not a deleted one.","read_only":false},{"name":"evaluate_wl","title":"Evaluate Wolfram Language","description":"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 session and in order, as the page's «Evaluate all» does (a definition in one is seen by the next). The w","read_only":true},{"name":"export_sources_bib","title":"Export sources bib","description":"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; 'page' to the ones a wiki page of the project cites ([@KEY], or [KEY] where the key is a source's),","read_only":true},{"name":"find_by_legal_document","title":"Find by legal document","description":"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 the 'issue' (key, summary) or the 'page' (id, title, spaceKey). Only accepted references in projects ","read_only":true}],"server_info":{"name":"kaiku","title":"Kaiku","version":"1.3.1","websiteUrl":"https://mcp.kaiku.tech"},"category":"productivity","tags":["project","communication","agents"],"kind":"remote","source":"registry","submitted":{},"first_party":true,"domain_rank":null,"score":100,"indexable":true,"first_seen":"2026-09-22","stars":0,"badges":[],"sponsor":null,"page":"https://agentsindex.org/agents/tech-kaiku-kaiku/"}