bots.st/kaiku
Kaiku
Answer questions in issue and wiki threads
1693 ms
answered our call
- State
- Answered
- Protocol
- MCP 2025-06-18
- Tools listed
- 200
- Answered
- 3 of the last 3 calls
How to reach it
- MCP, HTTP
https://app.kaiku.tech/mcp - MCP, HTTP
https://mcp.kaiku.tech/mcp - MCP, HTTP
https://{workspace}.kaiku.tech/mcpNeeds your own URL values
What it can do
| Tool | What it says it does |
|---|---|
add_attachment | 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… |
add_comment | 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… |
add_legal_reference | 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… |
add_to_showcase | 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… |
add_wiki_attachment | 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… |
add_wiki_comment | 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… |
admin_bank_transfer | 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… |
admin_errors_week | 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… |
admin_funnel | 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… |
admin_invoices | 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… |
admin_landing_week | 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 | 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… |
admin_overview | 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… |
admin_set_bank_transfer | 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… |
admin_set_workspace_ours | 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… |
admin_workspace_journal | 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… |
admin_workspaces | 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… |
answer_issue_question | 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 —… |
answer_review_remark | 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… |
approve_wiki_page | 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… |
archive_issues | 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… |
archive_project | 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… |
ask_issue_question | 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… |
ask_wiki_page_approval | 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… |
check_checklist_item | 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… |
check_source | 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 | 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… |
code_calls | 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… |
code_symbols | 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. |
computation_hours | 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… |
connect_repository | 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… |
copy_pdf_to_wiki | 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)… |
create_chat | 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… |
create_claim_embed | 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… |
create_credential | 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… |
create_embed_set | 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… |
create_issue | 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'… |
create_issue_from_chat_message | 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… |
create_project | 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… |
create_project_rule | 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 '[//]: #… |
create_term_embed | 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'… |
create_version | 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 =… |
create_wiki_embed | 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… |
create_wiki_page | 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… |
decide_join_request | 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… |
decide_persons | 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… |
decide_support_letter | 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… |
decide_terms | 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… |
define_term | 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… |
delete_agent_usage | 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 | 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_chat_message | 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. |
delete_claim | 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_computation | 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 | 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 | 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_machine_price | 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… |
delete_person | 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… |
delete_project_field | 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 | 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. |
And 140 more tools.
In its maker's words
Issue tracker and wiki for teams and their agents; answer your agents' questions from your phone.
- Website
- kaiku.tech/en/docs/mcp?utm_source=mcp-registry
- Publisher
- kaiku.tech
- Listed from
- the official MCP Registry as
tech.kaiku/kaiku - Version
- 1.3.1, updated 4 Nov 2026
- Kinds of work
- Messaging and support, Productivity, Writing and translation
The domain it lives on
- kaiku.tech
- registered 22 Aug 2026 (3 months ago), at NAMECHEAP INC, its home page is a working site
From our own crawl of domain names: registry records and the home page as our crawler last saw it.
Every call we made
| When | What happened | Time |
|---|---|---|
| Answered | 1693 ms | |
| Answered | 2362 ms | |
| Answered | 681 ms |
Next door
- Inbin: email for AI agentsDisposable inboxes for agent email verification
- AgentLairEmail delegation via inbox and vault
- Mailrith Email MarketingManage email subscribers, broadcasts, and automations with r
- faxforagents-mcpSend and receive faxes with approval
- AnyHookManage webhook inboxes for agent events
Is this your bot? Claim its address to add a verified badge and keep the listing current.