---
title: "Katman tools: what each MCP tool does and writes"
description: "Reference for all 17 Katman MCP tools: what each one does, whether it needs Audit Week or Pro, its key inputs, what it writes, and an example call to copy."
url: https://katman.pro/docs/tools
lang: en
updated: 2026-09-30
---

Docs Updated 30 Sep 2026

# Tools reference

> Katman has 17 tools in three groups: method tools for research, planning, prompts and content checks; crawl tools that scan your code and audit your live site; and visibility tools that measure what AI assistants say. Every tool except katman_account needs KATMAN_KEY. Ten work with Audit Week ($3 once, for 7 days) or Katman Pro: they find what’s wrong and tell you what to do. The other six (prompts, page briefs, file generation, IndexNow, monitoring and the dashboard sync) need Pro. All accept project_root, and only two can write outside the .katman folder, when you pass write: true.

## How the tools fit together

The tools follow the four steps of [the Katman method](https://katman.pro/method): research, plan, build, verify. Your agent doesn’t need to remember the order: `katman_start` always returns the next call.

Every tool accepts `project_root`, the absolute path of your site’s project. If you leave it out, Katman uses `KATMAN_PROJECT_ROOT`, then the root your MCP client reports, then the current folder. Tools return Markdown for the agent, plus structured data where useful. Read-only tools are marked `readOnlyHint`, tools that use the network `openWorldHint`, and no tool is destructive. Parameter names below match the current build; your client shows each tool’s live schema.

## Audit Week and Pro

Every tool except `katman_account` needs `KATMAN_KEY`, which comes with Audit Week or Katman Pro ([pricing](https://katman.pro/pricing)):

-   **Audit Week** costs $3, paid once, for 7 days. It doesn’t renew, and each account can buy it once. It unlocks the ten audit and recommendation tools: it finds what’s wrong and tells you what to do.
-   **Katman Pro** costs $29/month at the founding price for the first 100 customers (later $49/month), or $290/year. It unlocks every tool: building pages and writing files is Pro.

Without a valid key, a tool explains how to get Audit Week or Pro instead of running, and a Pro-only tool called with an Audit Week key explains that it needs Pro. `katman_account` needs no key and shows your plan. How to add the key is in [Getting started](https://katman.pro/docs/getting-started).

| Tool | Plan | Group |
| --- | --- | --- |
| `katman_start` | Audit Week and Pro | Method |
| `katman_research` | Audit Week and Pro | Method |
| `katman_plan` | Audit Week and Pro | Method |
| `katman_lint_content` | Audit Week and Pro | Method |
| `katman_report` | Audit Week and Pro | Method |
| `katman_scan_code` | Audit Week and Pro | Crawl |
| `katman_audit_site` | Audit Week and Pro | Crawl |
| `katman_keywords` | Audit Week and Pro | Crawl |
| `katman_visibility_run` | Audit Week and Pro | Visibility |
| `katman_manual_check` | Audit Week and Pro | Visibility |
| `katman_prompt` | Pro | Method |
| `katman_page_brief` | Pro | Method |
| `katman_generate` | Pro | Method |
| `katman_indexnow` | Pro | Crawl |
| `katman_setup_monitoring` | Pro | Visibility |
| `katman_sync` | Pro | Visibility |
| `katman_account` | No key needed | Method |

## Method tools

### katman\_start

The entry point. Reads `.katman/`, shows the status of the four steps and returns the next step as an exact tool call. It also adds a one-line plan status.

-   **Plan:** Audit Week and Pro.
-   **Inputs:** `site_url` (optional; saved to `config.json`).
-   **Writes:** `config.json` when you pass `site_url`.

```json
{ "site_url": "https://your-site.com" }
```

### katman\_research

Creates or updates your research: brand, the four-part sentence, the not-X note, 10–12 situations without your brand name, competitors with source and check date, proof with a source, keywords, and the question set (12 unbranded + 2 diagnostic). It rejects situations that contain your brand, competitors without a URL and check date, and proof without a source, and marks every gap as `[FILL]`.

-   **Plan:** Audit Week and Pro.
-   **Inputs:** `mode` (`template`, `update` or `show`); `data` (fields to merge, in `update` mode); `generate_questions: true` builds the 12 + 2 questions from templates.
-   **Writes:** `research.json` and `research.md`.

```json
{ "mode": "update", "generate_questions": true }
```

### katman\_account

Shows your plan (Audit Week with the days left, Pro, or none), the features your key unlocks, the masked email of the account, when the key was last checked, and how to connect or upgrade. It’s the one tool that runs without a key. Call it after adding or changing a key.

-   **Plan:** No key needed.
-   **Inputs:** none beyond `project_root`.
-   **Writes:** nothing. Contacts katman.pro only when `KATMAN_KEY` is set.

```json
{}
```

### katman\_plan

Builds the page plan and the task list in the book’s 30-day order from your research, scan, audit and latest run. Each task has an id, a prompt code (P0–P14), file hints, an acceptance criterion and the tool that verifies it.

-   **Plan:** Audit Week and Pro.
-   **Inputs:** none beyond `project_root`.
-   **Writes:** `plan.json` and `plan.md`; ticked tasks stay ticked when you regenerate.

```json
{}
```

### katman\_prompt

Returns one of the 15 prompts, P0–P14, filled with your research data, together with its acceptance criterion, the reason for it, and how Katman verifies it. It adds notes for your framework, such as prerendering options for a Vite single-page app.

-   **Plan:** Pro.
-   **Inputs:** `id` (`P0`–`P14`); `situation_id` (for P6); `lang` (`en` or `tr`).
-   **Writes:** nothing.

```json
{ "id": "P6", "situation_id": "s1" }
```

### katman\_page\_brief

A filled page brief: URL, title (situation first, about 60 characters), first sentence, action, proof, who it’s not for, alternatives, FAQ, related pages, the 11-block page anatomy, the JSON-LD to include, and where the file goes in your framework.

-   **Plan:** Pro.
-   **Inputs:** `type` (`situation`, `comparison`, `pricing`, `faq`, `about`, `single-question`, `glossary`, `tool` or `home`); `situation_id`; `topic`; `lang`.
-   **Writes:** nothing.

```json
{ "type": "situation", "situation_id": "s1" }
```

### katman\_generate

Generates files from your research, which stays the single source of truth: `robots.txt`, `llms.txt`, Organization, WebSite and SoftwareApplication JSON-LD (with your not-X line in `disambiguatingDescription`), FAQPage and BreadcrumbList JSON-LD, an analytics snippet that applies the human filter and the ChatGPT channel rule, a server-side bot counter for your platform (Cloudflare Worker, Next.js middleware, Express, Astro or SvelteKit), and an IndexNow key file.

-   **Plan:** Pro.
-   **Inputs:** `artifact` (for example `robots.txt`, `llms.txt`, `organization-jsonld`, `analytics-channel-snippet`, `bot-counter-snippet`); `options`; `write` (default false); `overwrite` (default false).
-   **Writes:** nothing by default: it returns the content and the target path. With `write: true` it writes that file, and it never replaces an existing file unless you also pass `overwrite: true`.

```json
{ "artifact": "llms.txt", "write": true }
```

### katman\_lint\_content

Checks a page against the content rules and the P6, P7 and P8 acceptance criteria: the first 1–3 sentences answer on their own, the one sentence matches your research and llms.txt, no hype words, no unsourced numbers, no placeholders, an update date, 5–8 FAQs, a not-for section, alternatives, at least 3 internal links, and title and description lengths.

-   **Plan:** Audit Week and Pro.
-   **Inputs:** one of `file`, `url` or `text`; `page_type` (for example `situation` or `comparison`).
-   **Writes:** nothing.

```json
{ "url": "https://your-site.com/your-situation-page", "page_type": "situation" }
```

### katman\_report

Summarises research completeness, the latest audit’s gate pass rates, visibility changes since the last run, the competitors and domains assistants cite most, plan progress, the top 10 open issues and the next 7 days.

-   **Plan:** Audit Week and Pro.
-   **Writes:** `report.md`.

```json
{}
```

## Crawl tools

### katman\_scan\_code

A deterministic scan of your codebase: framework and version, builder signatures (Lovable, Bolt, v0, Replit), a rendering verdict (server, static, hybrid or browser-only) with evidence, hosting and preview-URL patterns, public versus app routes, where head tags come from, robots, sitemap, llms.txt, 404 page, JSON-LD, hreflang, onClick navigation, images without alt or size, and whether analytics counts AI visitors.

-   **Plan:** Audit Week and Pro.
-   **Writes:** `scan.json`.

```json
{}
```

### katman\_audit\_site

Audits the live site the way AI crawlers see it: robots.txt (AI bot rules, bare prefixes, Cloudflare’s managed block), sitemaps, redirects, HSTS, compression, soft 404s, llms.txt, AI bot access through your CDN or firewall, and for each page its status, noindex, title, description, canonical, headings, words visible without JavaScript, first paragraph, JSON-LD, Open Graph, language, hreflang, images and internal links. Pass `urls` for a quick check of specific pages after a deploy.

-   **Plan:** Audit Week and Pro.
-   **Inputs:** `site_url` (your site) or `urls` (quick verify mode); `max_urls` (50 by default); `include_bot_test`; `preview_urls`.
-   **Writes:** `audits/<time>.json` and `audit.md`.

```json
{ "urls": ["https://your-site.com/pricing", "https://your-site.com/faq"] }
```

### katman\_indexnow

Sets up and verifies your IndexNow key file, submits only new or changed URLs, and returns the manual checklist for Google Search Console, Bing Webmaster Tools and Brave’s submit form.

-   **Plan:** Pro.
-   **Inputs:** `dry_run` (default true: shows what would be sent).
-   **Writes:** `indexnow.json`; contacts `api.indexnow.org` only with `dry_run: false`.

```json
{ "dry_run": false }
```

### katman\_keywords

Expands a seed phrase through Google’s autocomplete (the seed plus a–z and 0–9, at most 40 throttled requests), groups the results and suggests single-question and situation pages.

-   **Plan:** Audit Week and Pro.
-   **Inputs:** `seed`; `lang`; `country`; `save`.
-   **Writes:** nothing, unless you save the keywords to your research.

```json
{ "seed": "invoice template for freelancers" }
```

## Visibility tools

### katman\_visibility\_run

Asks your question set to ChatGPT, Claude, Gemini, Perplexity and Grok through OpenRouter, with live web search and your own key, and records for each answer whether you were named, recommended first or cited, and who else was named. It always starts as a dry run that prints the calls and the estimated cost: about $2.4 per run on the default `economy` panel (range $1.2–3.7), paid by you to OpenRouter. Details: [Visibility runs](https://katman.pro/docs/visibility-runs).

-   **Plan:** Audit Week and Pro (plus your own OpenRouter key).
-   **Inputs:** `dry_run` (default true); `models` (`economy` by default, `full`, `probe`, family names or OpenRouter slugs); `question_ids`; `samples` (1–5 repeats per question); `max_cost_usd` (default 3); `judge`; `follow_up_sources`; `temperature`; `concurrency`; `allow_google_grounding`.
-   **Writes:** `runs/<time>.json` and `measurements.md`.

```json
{ "dry_run": true, "models": "probe" }
```

### katman\_manual\_check

No API cost and within the apps’ terms: you ask a consumer app yourself, logged out with web search on, and paste the answer. Without `answer_text` it returns the instructions and the exact questions.

-   **Plan:** Audit Week and Pro.
-   **Inputs:** `assistant` (`chatgpt`, `claude`, `gemini`, `perplexity`, `copilot`, `grok`, `google-ai-mode` or `other`); `question_id` or `question`; `answer_text`; `sources`; `logged_in` (default false); `web_search` (default true).
-   **Writes:** a manual run in `runs/` and an updated `measurements.md`.

```json
{ "assistant": "chatgpt", "question_id": "q1", "answer_text": "…pasted answer…" }
```

### katman\_setup\_monitoring

Generates a GitHub Actions workflow that re-runs the visibility check, and optionally the audit, on a schedule with your `OPENROUTER_API_KEY` and `KATMAN_KEY` repository secrets, commits `.katman/` changes and opens an issue when your mention rate drops. It makes no network calls itself.

-   **Plan:** Pro.
-   **Inputs:** `schedule` (cron in UTC; default `0 6 * * 1`, Mondays; the book’s 14-day rhythm is `0 6 1,15 * *`); `include_audit`; `models`; `max_cost_usd`; `write`; `overwrite`.
-   **Writes:** `.github/workflows/katman.yml`, only with `write: true`.

```json
{ "schedule": "0 6 1,15 * *", "models": "economy", "write": true }
```

### katman\_sync

Sends a summary of your project to your katman.pro dashboard: gate pass counts, visibility rates by assistant and language, plan progress, the top 10 issue titles, dates and the Katman version. It never sends code, file contents, answers, questions or prompts. By default it’s a dry run that shows the exact JSON it would send.

-   **Plan:** Pro.
-   **Inputs:** `dry_run` (default true).
-   **Writes:** nothing locally; contacts katman.pro only with `dry_run: false`.

```json
{ "dry_run": true }
```

## Prompts and resources

MCP prompts, shown as slash commands in many clients: `katman-start`, `katman-audit` (P1: a report, no code changes), `katman-situation-page` (takes a `situation`) and `katman-measure`.

Resources your agent can read: `katman://method`, `katman://checklist/prepublish`, `katman://checklist/site-audit`, `katman://content-rules`, `katman://prompts/{id}` and `katman://research`.

What each tool may read, write and send is listed on [Permissions](https://katman.pro/docs/permissions).

## Frequently asked questions

### Which tool should I call first?

katman\_start. It reads your .katman folder, shows which of the four steps are done and returns the exact next call.

### Which tools come with Audit Week?

katman\_start, katman\_research, katman\_scan\_code, katman\_audit\_site, katman\_keywords, katman\_plan, katman\_lint\_content, katman\_visibility\_run, katman\_manual\_check and katman\_report. Audit Week finds what’s wrong and tells you what to do; building pages and writing files is Pro, so katman\_prompt, katman\_page\_brief, katman\_generate, katman\_indexnow, katman\_setup\_monitoring and katman\_sync need Katman Pro. katman\_account needs no key.

### What does a tool do without a valid key?

It doesn’t run. It tells your agent how to get Audit Week or Pro and how to add KATMAN\_KEY to your MCP config. A Pro-only tool called with an Audit Week key explains that it needs Pro.

### Which tools spend money?

Only katman\_visibility\_run, on your own OpenRouter key, and only with dry\_run: false after you’ve seen the estimate. katman\_manual\_check may make one small judge call if an OpenRouter key is set.

### Which tools can change files outside .katman?

katman\_generate and katman\_setup\_monitoring, and only when called with write: true. Neither replaces an existing file unless you also pass overwrite: true.

### Do the tools work offline?

Scanning, research, planning, prompts, briefs and file generation work offline. Audits, content checks by URL, IndexNow, keyword research and visibility runs need the network. Katman checks your key with katman.pro at most once a day and keeps working offline for 7 days after the last successful check; Audit Week still ends on its end date.

### Why does my client show different parameters?

Your MCP client shows each tool’s live input schema, and that schema wins over this page.

## Related pages

-   [**Getting started with Katman** Install Katman MCP in Cursor, Claude Code, VS Code, Windsurf, Codex or Gemini CLI, add your Katman key and optional OpenRouter key, and run your first session.](https://katman.pro/docs/getting-started)
-   [**Permissions: what Katman can do** What Katman reads in your project, what it writes, which network calls it makes and when, what goes to katman.pro with your key, and how it handles your keys.](https://katman.pro/docs/permissions)
-   [**Visibility runs** How Katman measures AI visibility: 12+2 question set, five assistants via OpenRouter, cost caps, manual checks in the apps, and why one run is a small sample.](https://katman.pro/docs/visibility-runs)
-   [**The Katman method: research, plan, build, verify** Four steps, three gates and 15 prompts with acceptance criteria that make a site readable, quotable and recommendable by ChatGPT, Claude, Gemini and Perplexity.](https://katman.pro/method)
-   [**Troubleshooting** Fixes for common Katman problems: server not showing up, wrong project folder, missing keys, locked tools, 402 errors, Cloudflare challenges, empty pages.](https://katman.pro/docs/troubleshooting)
-   [**Pricing** Audit Week costs $3 once for 7 days of Katman's audit and recommendation tools. Katman Pro adds the build tools, the course and the community: $29/month.](https://katman.pro/pricing)

Updated 30 September 2026 · Katman
