Kai MCP server

• Addresshttps://hirekai.ai/mcpnot in the official registry: answered when asked

No entry in the official MCP registry names this server. It answered on hirekai.ai when the Atlas asked at the address servers are usually mounted on, so it is the vendor's own. Clients and catalogues that list servers from the registry do not show it.

• Stateanswerschecked 2026-10-27
• Tools7
• Server calls itselfkai-content
• Server version0.1.1
• Protocol version2025-06-18

On 2026-10-27 the server answered initialize and tools/list without a sign-in. First answer in 865 ms.

• Whether its tools do the product's job has not been judged yet.
• Checked on 1 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 1 so far
• Answeredmeasuring1 of the 7 daily checks it takes to print a share
• Median first answer916 ms
• Space in an agent's context≈ 1,032 tokensthe definitions of all its tools (7), which an agent carries on every turn
• Tool definitionsB · 83 of 100
• Typed results0 of 7 toolsdeclared outputSchema: results come typed, read once

• Not saying whether it only reads or can destroy: 7 of 7

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• search_kai

  Full-text search across Kai's knowledge base: blog posts, feature pages, KB, FAQs, free tools, and competitor comparisons. Returns ranked hits with title, url, source, and a short snippet. Use this first when asked open-ended product…

• get_feature

  Get Kai's structured product info for a specific feature page (meetings, email, calendar, daily-planning, action-items). Returns hero, capabilities, steps, integrations, FAQ, and a markdown rendering.

• get_product_info

  Return a specific canonical section of Kai's product knowledge base: positioning, pricing, integrations, what-kai-is-not, or brand. Use when you need authoritative product facts, not search results.

• list_blog_posts

  List Kai blog posts. Optional filter by tag (tool/topic slug, e.g. 'granola' or 'otter-ai') and/or articleType (review, comparison, alternatives, pricing, guide). Returns compact records (slug, title, description, datePublished, tags…

• get_blog_post

  Fetch a single Kai blog post by slug. Returns frontmatter + plain markdown with custom MDX components stripped or converted to plaintext.

• compare_kai_with

  Fetch Kai's structured comparison against a specific competitor (otter-ai, fyxer-ai, granola-ai). Returns hero copy, key differences, best-for segments, a feature comparison table, and FAQ.

• get_free_tool

  Fetch description and FAQ for one of Kai's free web tools (meeting-cost-calculator, meeting-agenda-generator, time-blocking-template). Returns the interactive URL plus context agents can share.