Knowcap API Reference

Authentication

Every API request authenticates via the x-api-key header (or Authorization: Bearer ... for raw user tokens). All keys are prefixed kc_live_.

Getting Your API Key

Sign in at app.knowcap.ai
Navigate to Settings → API Keys
Pick the organization the key should bill to (you can own keys for any org you're owner or admin of)
Generate the key and copy it immediately — the full key is shown once and never again

🏢 Keys are pinned to one organization

Each API key is bound to a specific org. That org's api_credits_balance pays for every call made with the key, regardless of which project's data the call references. If you work across multiple orgs, create one key per org and switch which key your client uses.

You can change which org a key bills to without rotating credentials — see Move Key Org.

Example Request

curl https://app.knowcap.ai/api/projects \
  -H "x-api-key: kc_live_YOUR_KEY"

Rate Limits & Credits

A runaway loop hits one of three guard-rails: per-minute rate cap, daily rate cap, or empty credit balance. All three are scoped to the API key's organization.

Per-tier rate limits

Plan	Per minute	Per day
Free	10	100
Pro	60	5,000
Business	120	15,000

Some routes count for more than one request because they're more expensive on the server side:

Route	Cost
POST `/api/chats/:id/messages`	5
POST `/api/chats/:id/generate-title`	5
POST `/api/chats/project/:id/suggested-questions`	5
POST `/api/artifacts/generate`	5
GET `/api/sources/:id/transcriptions`	2
GET `/api/sources/:id/visuals`	2
GET `/api/projects/:id/search`	2
everything else	1

Response on 429

When you hit a limit you receive:

429 Too Many Requests

{
  "error": "Rate limit: 120 requests per minute",
  "retry_after_seconds": 42,
  "plan": "business"
}

A Retry-After header is also set. Back off with exponential delay and resume.

Read-credit gate (402)

Every successful GET debits a sub-cent fee from the key's org credit pool (default 0.1¢ per call, batched). When the balance hits zero, every subsequent GET returns:

402 Payment Required

{
  "success": false,
  "error": "Insufficient API credits...",
  "code": "INSUFFICIENT_ORG_API_CREDITS",
  "balance_cents": 0
}

POST endpoints that drive LLM calls (chat send, artifact generate) have their own token-based debit on top of this and may return 402 even when the read pool isn't exhausted.

🛑 Per-key kill switch

You can pause a leaked or runaway key without deleting it via PATCH /api/users/api-keys/:id/disable. Disabled keys return 401 immediately on the next call. Re-enable with PATCH .../enable. See the API Keys section.

GET /api/users/me

Returns the currently authenticated user's profile, including account details and subscription status.

Request

curl https://app.knowcap.ai/api/users/me \
  -H "x-api-key: YOUR_API_KEY"

Response · 200

{
  "id": "usr_a1b2c3d4",
  "email": "you@example.com",
  "name": "Jane Doe",
  "plan": "pro",
  "createdAt": "2026-01-15T08:30:00Z"
}

GET /api/projects

Retrieve a list of all projects belonging to the authenticated user. Each project contains one or more sources.

Request

curl https://app.knowcap.ai/api/projects \
  -H "x-api-key: YOUR_API_KEY"

Response · 200

[
  {
    "id": "prj_x9k2m1",
    "name": "Product Research",
    "sourceCount": 12,
    "createdAt": "2026-02-01T10:00:00Z",
    "updatedAt": "2026-03-20T14:30:00Z"
  }
]

GET /api/sources/project/{id}

List all sources within a specific project. Sources can be text entries, ingested URLs, uploaded files, or recordings.

Path Parameters

Name	Type	Description
id required	string	The project ID

Request

curl https://app.knowcap.ai/api/sources/project/prj_x9k2m1 \
  -H "x-api-key: YOUR_API_KEY"

Response · 200

[
  {
    "id": "src_f3g7h2",
    "type": "url",
    "title": "Market Analysis Report",
    "url": "https://example.com/report",
    "tags": ["research", "Q1"],
    "status": "completed",
    "createdAt": "2026-02-05T09:15:00Z"
  }
]

GET /api/sources/{id}/transcriptions

Retrieve transcript chunks for a specific source. Returns an array of text segments with timestamps (when available) from audio/video sources, or full text content for text-based sources.

Path Parameters

Name	Type	Description
id required	string	The source ID

Request

curl https://app.knowcap.ai/api/sources/src_f3g7h2/transcriptions \
  -H "x-api-key: YOUR_API_KEY"

Response · 200

{
  "sourceId": "src_f3g7h2",
  "chunks": [
    {
      "index": 0,
      "text": "The market grew 23% year over year...",
      "startTime": 0.0,
      "endTime": 4.5
    },
    {
      "index": 1,
      "text": "Key drivers include AI adoption...",
      "startTime": 4.5,
      "endTime": 9.2
    }
  ]
}

POST /api/sources/text

Create a new text source within a project. The text content will be processed and made searchable within your knowledge base.

Request Body

Field	Type	Description
projectId required	string	Target project ID
title required	string	Display title for the source
content required	string	The text content to ingest
tags	string[]	Optional tags for organization

Request

curl -X POST https://app.knowcap.ai/api/sources/text \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "projectId": "prj_x9k2m1",
    "title": "Meeting Notes — March 2026",
    "content": "Discussed Q1 targets and product roadmap...",
    "tags": ["meetings", "Q1"]
  }'

Response · 201

{
  "id": "src_n4p8q1",
  "type": "text",
  "title": "Meeting Notes — March 2026",
  "status": "processing",
  "createdAt": "2026-03-31T12:00:00Z"
}

POST /api/sources/url

Ingest a URL as a source. Knowcap will fetch the page content, extract text, and process it into your knowledge base. Supports articles, documentation pages, blog posts, and more.

Request Body

Field	Type	Description
projectId required	string	Target project ID
url required	string	The URL to ingest
tags	string[]	Optional tags for organization

Request

curl -X POST https://app.knowcap.ai/api/sources/url \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "projectId": "prj_x9k2m1",
    "url": "https://example.com/interesting-article",
    "tags": ["research"]
  }'

Response · 201

{
  "id": "src_r7t2w5",
  "type": "url",
  "url": "https://example.com/interesting-article",
  "status": "processing",
  "createdAt": "2026-03-31T12:05:00Z"
}

GET /api/users/api-keys

List the caller's keys. Returns each key's prefix (first 12 chars), name, the org it bills to, last-used timestamp, and whether it's currently disabled. Full key values are never returned after creation.

Response · 200

{
  "apiKeys": [
    {
      "id": "d127cbdd-...",
      "name": "MCP Knowcap Key",
      "key_prefix": "kc_live_kXum",
      "org_id": "b7f0489c-...",
      "org_name": "Knowcap",
      "last_used_at": "2026-05-06T15:08:25Z",
      "disabled_at": null,
      "created_at": "2026-04-26T22:29:43Z"
    }
  ]
}

POST /api/users/api-keys

Create a new API key pinned to a specific organization. The full key is returned once in plainKey — store it immediately, you can't fetch it again. To pick the org, call GET /api/users/api-key-orgs for the list of orgs you can target.

Request Body

Field	Type	Description
name	string	Human-readable label (e.g. "MCP Knowcap")
org_id	uuid	Org to bill. You must be owner or admin of it. Defaults to your primary owned org if omitted.

Request

curl -X POST https://app.knowcap.ai/api/users/api-keys \
  -H "x-api-key: kc_live_..." \
  -H "Content-Type: application/json" \
  -d '{
    "name": "MCP Knowcap",
    "org_id": "b7f0489c-..."
  }'

Response · 201

{
  "success": true,
  "apiKey": {
    "id": "...",
    "name": "MCP Knowcap",
    "key_prefix": "kc_live_aBcD",
    "org_id": "b7f0489c-...",
    "plainKey": "kc_live_aBcD..."
  }
}

PATCH /api/users/api-keys/{id}/org

Move an existing key to a different org without rotating credentials. Requires owner or admin membership on the new org. The key string itself does not change — same secret, new biller.

Request

curl -X PATCH https://app.knowcap.ai/api/users/api-keys/d127cbdd-.../org \
  -H "x-api-key: kc_live_..." \
  -H "Content-Type: application/json" \
  -d '{ "org_id": "d9196fb2-..." }'

PATCH /api/users/api-keys/{id}/disable

Soft-revoke a key. authenticateApiKey rejects the key on the next call — the kill switch is effectively instant. Use .../enable with the same id to bring it back. Pass an optional reason for audit.

Disable

curl -X PATCH https://app.knowcap.ai/api/users/api-keys/{id}/disable \
  -H "x-api-key: kc_live_..." \
  -H "Content-Type: application/json" \
  -d '{ "reason": "leaked in repo" }'

Re-enable

curl -X PATCH https://app.knowcap.ai/api/users/api-keys/{id}/enable \
  -H "x-api-key: kc_live_..."

GET /api/users/api-keys/{id}/usage

Per-key usage roll-up: 24-hour and 30-day call counts plus total bytes-out. Powered by the api_key_usage_summary view — every kc_live_ request inserts an audit row used to compute these.

Response · 200

{
  "usage": {
    "api_key_id": "d127cbdd-...",
    "name": "MCP Knowcap",
    "key_prefix": "kc_live_kXum",
    "calls_24h": 42,
    "bytes_out_24h": 3934558,
    "calls_30d": 1207,
    "bytes_out_30d": 128403211,
    "last_used_at": "2026-05-06T15:08:25Z",
    "disabled_at": null
  }
}

GET /api/projects/{id}/search

Unified search across a project's transcripts, memories, and artifacts in one round trip. Transcript hits are scored by RAG similarity; memory and artifact hits use case-insensitive substring match. Each hit carries the source id and (when available) start_time for direct deep-linking into a meeting.

Query Parameters

Name	Type	Description
q required	string	Plain-text query (1–500 chars)
kinds	string	Comma-separated subset of `transcript,memory,artifact`. Default: all three
limit	int	Max hits per kind (1–50). Default 10

Request

curl "https://app.knowcap.ai/api/projects/{id}/search?q=invoice&limit=5" \
  -H "x-api-key: kc_live_..."

Response · 200

{
  "project_id": "b58a4c12-...",
  "query": "invoice",
  "kinds": ["transcript", "memory", "artifact"],
  "total": 7,
  "hits": [
    {
      "kind": "memory",
      "memory_id": "...",
      "memory_category": "task",
      "source_id": "...",
      "source_name": "Q1 invoice review",
      "snippet": "Send invoice to Acme by EOW...",
      "start_time": 126,
      "score": null
    }
  ]
}

GET /api/projects/{id}/memories

Auto-extracted memories — open tasks, risks, decisions, facts, and people — with source-level permalinks. Each memory carries category, summary, structured fields specific to its category (e.g. tasks have title/status/assignee/deadline), and the underlying source's start_time when extracted from a recording.

Query Parameters

Name	Type	Description
category	string[]	Filter by category. Repeat the param for OR: `?category=task&category=decision`
status	string	Comma-separated review statuses. Default: `pending,confirmed,edited`. Available: `pending,confirmed,edited,rejected,auto_rejected`
source	string	`chat` or `recording`
sourceId	uuid	Restrict to memories tied to one source
limit	int	1–200, default 50
offset	int	Pagination offset. Default 0

GET /api/sources/{id}/visuals

Visual frames extracted from a recording (Vision/screen-share JPEGs). Each frame has a public Supabase Storage URL, the AI-generated caption, and the start_time so you can deep-link directly into the meeting at that moment.

Query Parameters

Name	Type	Description
startTime	number	Window start in seconds (inclusive)
endTime	number	Window end in seconds (inclusive)
limit	int	1–500, default 200

Request

curl "https://app.knowcap.ai/api/sources/{id}/visuals?startTime=60&endTime=180" \
  -H "x-api-key: kc_live_..."

Response · 200

{
  "source_id": "...",
  "project_id": "...",
  "total": 12,
  "visuals": [
    {
      "id": "...",
      "start_time": 63.2,
      "end_time": 68.0,
      "frame_url": "https://....supabase.co/storage/.../frame.jpg",
      "caption": "[Screen: Plan & Billing settings, Current Balance 5,000]",
      "type": "visual"
    }
  ]
}

PATCH /api/sources/{id}

Update metadata for an existing source. Use this to modify tags, title, or other mutable properties. Only provided fields will be updated.

Path Parameters

Name	Type	Description
id required	string	The source ID

Request Body

Field	Type	Description
title	string	New display title
tags	string[]	Replace tags array

Request

curl -X PATCH https://app.knowcap.ai/api/sources/src_f3g7h2 \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "title": "Updated Report Title",
    "tags": ["research", "updated", "Q1"]
  }'

Response · 200

{
  "id": "src_f3g7h2",
  "type": "url",
  "title": "Updated Report Title",
  "tags": ["research", "updated", "Q1"],
  "updatedAt": "2026-03-31T12:10:00Z"
}

MCP — Model Context Protocol

Knowcap runs a hosted MCP server at https://mcp.knowcap.ai/mcp (source: Knowcap-V2/knowcap-mcp). It exposes your projects, sources, memories, artifacts and chats as MCP tools, resources and slash prompts. Point Claude Code, claude.ai, Cursor, Codex or any other MCP-aware client at that URL and the model can read and write Knowcap directly.

Connect in one click — no key to copy

Recommended. Claude opens your browser, you sign in to Knowcap, and the connection is authorized. Nothing to paste, nothing to store.

Claude Code (terminal)

claude mcp add --transport http knowcap https://mcp.knowcap.ai/mcp

claude.ai (web) — Settings → Connectors → Add custom connector:

URL: https://mcp.knowcap.ai/mcp
Click Connect and sign in to Knowcap
The connector flips to Connected

Use the exact /mcp path. The bare host and /api/mcp will not work.

Connect with an API key

For scripted, headless or CI setups where a browser sign-in isn't possible. Mint a key at Settings → API Keys — the secret is shown once — then pass it as a header.

Claude Code (terminal)

claude mcp add --transport http knowcap https://mcp.knowcap.ai/mcp \
  --header "X-API-Key: kc_live_..."

In the claude.ai web connector, add a header X-API-Key set to your kc_live_… key. The server also accepts Authorization: Bearer with a raw kc_ key.

Run it locally from source

Only needed if you want to modify the server or run it fully offline against a local Knowcap. The hosted URL above is the supported path for everyone else.

Clone Knowcap-V2/knowcap-mcp, then npm install && npm run build
Add the config below to ~/.claude.json
Restart Claude Code, or run /mcp to reconnect

~/.claude.json (snippet)

{
  "mcpServers": {
    "knowcap": {
      "type": "stdio",
      "command": "node",
      "args": ["/path/to/knowcap-mcp/dist/index.js"],
      "env": {
        "KNOWCAP_API_KEY": "kc_live_...",
        "KNOWCAP_API_URL": "https://app.knowcap.ai",
        "KNOWCAP_APP_URL": "https://app.knowcap.ai"
      }
    }
  }
}

npx knowcap-mcp is not available — the package is not published to npm. Clone and build, or use the hosted URL.

🏢 One connection per organization

An MCP connection is scoped to a single organization and can only ever reach that org's data. Working across several? Add one connection per org — with API keys, that means one key per org — see Authentication.

MCP Tool Reference

The server exposes 79 tools, 8 resources and 8 slash prompts, across 12 areas. This list is generated from the running server, so it is exactly what your client sees after connecting — tools marked destructive delete data or make changes that cannot be undone.

Artifacts

Tool	What it does
`create_artifact`	Save your own written content as a new artifact inside a project, optionally linking it to the sources it came from.
`delete_artifact` destructive	Permanently remove an artifact along with its version history and any share links pointing to it. This cannot be undone.
`generate_artifact`	Have Knowcap AI write a new artifact for you from a prompt, optionally grounded in specific sources so the output reflects what was actually said.
`get_artifact`	Open a single artifact and read its full content.
`get_artifact_access`	See who can currently see an artifact — its visibility level and, if you manage it, the exact list of people or roles allowed in.
`get_artifact_access_audit`	See the history of visibility changes made to an artifact — who changed access, when, and what changed — as opposed to who currently has access.
`list_artifacts`	See every artifact — AI-generated or hand-written note, summary, or document — that has been created in a project.
`set_artifact_access` destructive	Change who can see an artifact by setting its visibility level and, for restricted access, exactly who is allowed in — this replaces the current list rather than adding to it. Setting restricted access without naming anyone who may see it would hide the artifact from your whole team, so that combination must be confirmed explicitly.
`update_artifact`	Change an artifact's title, content, or type after it has been created.

Chats

Tool	What it does
`create_chat`	Start a brand-new chat conversation inside a project, ready to send messages into.
`delete_chat` destructive	Permanently delete a chat conversation and everything in it. This cannot be undone.
`get_chat`	Look up a single chat conversation by its id, including its title and basic details.
`list_chat_messages`	Read the full back-and-forth of one chat conversation, message by message.
`list_chats`	List every chat conversation inside a project, so you can find or resume a discussion instead of starting a new one.
`send_chat_message`	Post a message into an existing chat and get back the AI-generated reply, the same way the in-app chat works. Each call sends a new message and triggers a fresh response, so re-sending is not a no-op.

Digest

Tool	What it does
`digest_project`	Gets a one-stop overview of a project — its open tasks, risks, decisions, key facts, and recent recordings, files, and chats — all in a single call instead of checking each one separately.

Folders

Tool	What it does
`create_folder`	Create a new folder to group sources inside a project. Creating one without saying who may see it defaults to keeping it hidden from everyone except owners and admins, so that combination must be confirmed explicitly.
`delete_folder` destructive	Remove a folder from a project. The sources inside are not deleted — they move back to the project's top level and stay fully visible there.
`file_sources_to_folder`	Move one or more sources into a folder inside the same project. Filing into a folder set to restricted access can hide those sources from anyone not granted access on it, so that combination must be confirmed explicitly.
`get_folder_access`	See who can currently see a folder — its visibility level and, if you manage it, the exact list of people or roles allowed in.
`get_folder_access_audit`	See the history of visibility changes made to a folder — who changed access, when, and what changed — as opposed to who currently has access.
`list_folders`	See every folder in a project, along with how many sources and members each one has and who can currently see it.
`remove_source_from_folder`	Take a source out of its folder and move it back to the project's top level, where it's fully visible again. This can be reversed by filing the source into a folder again.
`set_folder_access` destructive	Change who can see a folder by setting its visibility level and, for restricted access, exactly who is allowed in — this replaces the current list rather than adding to it. Setting a folder to restricted without naming anyone who may see it would hide it from your whole team, so that combination must be confirmed explicitly.
`update_folder`	Rename a folder or change its description. This does not change who can see it.

Hierarchy

Tool	What it does
`get_organization_md`	Fetches the shared instructions for your whole organization — things like tone, vocabulary, and what each memory category means for your team — so you can see the ground rules everyone else is working from.
`get_project_md`	Fetches a project's own instructions doc — its glossary, scope, and any special people or context that project cares about.
`get_user_md`	Fetches a person's instructions doc — their role, how they like escalations handled, and their style preferences. Defaults to your own; looking up someone else's only works if you share a project with them.

Memories

Tool	What it does
`get_memory`	Fetch one memory by its id. It looks through a project's recent memories to find the match, so a very old memory outside that recent window may not turn up.
`search_memories`	Search a project's auto-extracted memories — tasks, risks, decisions, facts — filtering by category, review status, or source, with a link back to where each one came from.
`update_memory_review`	Confirm, reject, or edit an auto-extracted memory to correct how Knowcap recorded it.

Projects

Tool	What it does
`archive_project`	Hides a project from your regular lists without deleting anything inside it — everything stays intact and can be brought back at any time.
`create_project`	Creates a new project inside one of your organizations, ready to hold meetings, memories, and files.
`delete_project` destructive	Permanently removes a project and everything inside it — recordings, transcripts, memories, and files — with no way to undo it. Archiving is the safer, reversible alternative for most cases.
`get_me`	Confirms who you're signed in as and which organization is set as your default workspace, so every other action knows where to look first.
`get_project`	Looks up a single project's details by its id.
`list_organizations`	Lists every organization you're an active member of, along with your role in each one, so you can pick the right workspace before doing anything else.
`list_projects`	Lists your projects, automatically limited to your default organization unless you ask for a specific one or for everything across all your organizations.
`set_default_org`	Sets which organization is treated as your default workspace, or clears it, so project lists and searches point at the right place automatically.
`unarchive_project`	Brings a previously archived project back into your regular lists.
`update_project`	Updates a project's name, description, or color.

Search

Tool	What it does
`search_by_speaker`	Finds every meeting where a given person spoke, by checking each project's speaker roster for a name match — handy when you know who was in the room but not which project the conversation happened in. On very large workspaces the scan may stop early and cover only some of the projects checked so far.
`search_cross_org`	Searches across every project and organization you can access at once, instead of one project at a time — useful when you don't know which project something was said in.
`search_project`	Search everything inside one project at once — meeting transcripts, extracted memories and artifacts — and get back results with links that jump straight to the moment they came from.

Sharing

Tool	What it does
`create_share_link`	Create a public link that anyone can open without an account, for a specific source or artifact. Calling this again for the same item returns the same link instead of making a new one, and you can optionally set it to expire after a number of hours.
`list_share_links`	See every public share link in a project, including ones that have expired but haven't been revoked yet, along with what each one points to.
`revoke_share_link` destructive	Turn off a public share link so it can no longer be opened. Anyone who had the link loses access immediately; a new link can be created afterwards if needed.

Sources

Tool	What it does
`confirm_source_upload`	Second step of a two-step file upload — finishes the upload once the file has been sent, and kicks off transcription and AI processing.
`delete_source` destructive	Permanently delete a source and everything tied to it — transcript, memories, screen captures, and share links. This cannot be undone.
`generate_source_tags`	Have Knowcap's AI generate fresh tags for a source based on its content, replacing whatever tags were there before.
`get_source`	Look up a single source by its id and get back its details and file link. To read what was actually said, use the transcript lookup instead.
`get_source_access`	Check who can currently see a source and, if you manage it, the full list of people and roles with access.
`get_source_access_audit`	See the history of who changed a source's visibility settings, when, and what changed.
`get_source_transcriptions`	Get the full transcript of a meeting or recording, broken into segments with clickable timestamps that jump straight to that moment. Can be narrowed to a specific time window.
`get_source_visuals`	Get the screen-share and slide images captured during a recording, each with an AI-written caption and a timestamp link — handy for finding who was on screen and when.
`list_inbox`	See everything sitting in your Knowcap Inbox that has not been filed into a project yet — newest first, with attendees, duration, and a short transcript preview for each item.
`list_sources`	List the sources in a project — meetings, recordings, and documents — newest first, with paging for large projects.
`move_source`	Move a source into a different project (or out of the Inbox), taking its transcript, memories, and share links along with it.
`prepare_source_upload`	First step of a two-step file upload — reserves a spot and hands back a secure link to send the file to. Finish with the matching second step once the file has been sent.
`resolve_source_url`	Paste in a Knowcap web link — to a meeting, recording, or share — and get back the source record it points to.
`set_source_access` destructive	Set who can see a source. This replaces the entire access list, so anyone not included loses access — check the current list first if you want to keep existing people on it.
`update_source`	Rename a source, change its status, replace its tags, or update its metadata. Tags you pass in replace the existing ones rather than adding to them.

Speakers

Tool	What it does
`delete_voiceprint` destructive	Permanently remove a saved voice from your voice library. Past transcripts keep the name they already had, but Knowcap will no longer auto-recognize that voice in new recordings.
`get_speaker`	Finds one speaker from a project's roster by id — handy when you already know the id and just want that person's details.
`identify_speaker`	Give a real name to an unidentified speaker (like "SPEAKER_00" or "Guest 1") across everywhere they spoke in a recording, and optionally save their voice so future recordings recognize them automatically.
`list_speakers`	List everyone Knowcap has identified as speaking across a project's recordings — the roster of people who appeared in its meetings.
`list_voiceprints`	List everyone whose voice you've saved to your personal voice library, so Knowcap can automatically recognize them in future recordings. This follows you across every organization, not just one project.
`merge_voiceprints` destructive	Combine two saved voices in your library into one, moving every past attribution and audio sample onto the voice you keep. The other voice is permanently deleted as part of the merge.
`rename_voiceprint`	Rename a saved voice in your voice library. This only changes the label going forward — it doesn't rewrite the name on speech that was already transcribed.

Workflow

Tool	What it does
`get_memory_edges`	See how one extracted decision, task, risk, or fact connects to others — what it replaces, what it's blocked by, or what it relates to.
`get_rate_limit_status`	Check how much of your daily usage allowance is left, so you can pace a big batch of work before you hit the limit.
`get_recap`	Get the meeting recap Knowcap generated for a recording — the same summary content used for a debrief email — without sending anything.
`join_meeting` destructive	Send the recording bot into a scheduled meeting so it joins, records, and transcribes the call. This is a real, visible action — the bot actually appears in the live meeting — so it cannot be undone once triggered.
`list_claims`	See the decisions, tasks, risks, and facts Knowcap has automatically picked out of your recordings, whether or not they've been filed into a project yet.
`list_meetings`	See what meetings are coming up on your synced calendar — the same schedule the recording bot works from.
`list_org_members`	See everyone in an organization along with their name, email, and role — useful for figuring out who's who or who can approve something.
`route_claim`	File one of those extracted decisions, tasks, risks, or facts into the project it belongs to, or take it back out again.
`route_inbox_source`	Move a recording out of your unsorted inbox and into the right project, optionally filing it into a folder at the same time.
`set_org_member_role` destructive	Change what a member is allowed to do in an organization — owner, admin, or member. Granting or removing owner (full control of billing, members, and settings) needs an extra confirmation step because of how much access it hands over.

Slash prompts

Ready-made questions you can run straight from your client.

/knowcap-decision-log — Chronological decision log for a project with rationale and source citations.
/knowcap-inbox-triage — Walk the current Knowcap Inbox (sources with project_id=NULL) and propose a disposition for each: keep / archive / route-to-project. Powers the daily inbox-zero workflow.
/knowcap-meeting-debrief — Produce a structured debrief of a Knowcap meeting/recording: agenda, decisions, tasks, risks, who said what — every reference linked to the timestamp in Knowcap.
/knowcap-open-tasks — List open tasks across a project, grouped by source meeting, deadline-sorted.
/knowcap-people-brief — What is known about a person across a project: role, recent contributions, linked memories.
/knowcap-risks-watch — Open risks for a project ordered by severity.
/knowcap-share-bundle — List every active share link in a project (sources + artifacts) with token, expiry, and what it points at. Pre-built for security review or "what is public right now?" audits.
/knowcap-source-followups — Pull every task, risk, decision, and open question tied to one source/meeting, ordered by timestamp. The right "what came out of this meeting and is still open" report.

This page is built from https://mcp.knowcap.ai/tools.json, which the server generates from its own tool definitions. It cannot drift from what the server actually offers.