MCP Tool Reference¶

This reference lists every tool the Huddo MCP server offers to AI assistants. Each tool is something an assistant can do on behalf of the signed-in user, and it runs with that user's permissions. An assistant can never see or change more than the user could in Huddo itself.

You don't call these tools yourself. You ask the assistant in plain language, for example "What changed in the Engineering space this week?", and it picks the tools. Use this reference to find out what an assistant can do, what each tool reads or changes, and which tools to allow or restrict.

Tools by app¶

Each tool name starts with the app it belongs to:

Page	Tools	What they cover
Huddo (cross-app)	11	Who am I, recent items, weekly digest, resolving URLs, comments, links between objects, files
Core	3	Finding people and groups, organisation members
Notifications	4	Inbox, marking read, notification settings
Search	1	Full-text search across wikis and ideas
Wikis	19	Wikis, pages, history, templates, properties, likes and follows, review and approvals
Ideas	13	Labs, ideas, voting, following, turning an idea into a wiki page
Discussions	5	Comment threads: read, reply, edit, delete, react, mute, resolve
Spaces	6	Finding, reading, joining, starring, creating and deleting spaces
Links	6	Bookmarks, link details and click counts, safe link previews

That's 68 tools in total.

Which tools are available¶

Not every install offers every tool. A tool is offered only when:

Every app it needs is installed. For example, the Ideas tools appear only when Huddo Ideas is installed, and ideas_to_page needs both Ideas and Wikis. Each tool's entry lists the apps it needs.
Its tool group is switched on. An administrator can limit the groups with HUDDO_MCP_TOOLSETS (see The MCP service). All groups are on by default.

The assistant only sees the tools that are offered, so it can't try to use an app that isn't there. To check what an install has, ask the assistant "Which Huddo apps do I have?". It calls huddo_whoami, which lists the installed apps and their URLs.

Tool groups¶

Group	Tools
`core`	`huddo_whoami`, the `core_` tools and the `notifications_` tools
`crossapp`	`huddo_resolve`, `huddo_recent`, `huddo_digest`, `huddo_get_comments`, `huddo_comment`, `huddo_link`, `huddo_unlink`, `huddo_related`, `huddo_upload_file`, `huddo_delete_file`, `ideas_to_page`
`search`	`search_content`
`wikis`	The `wikis_*` tools
`ideas`	The `ideas_*` tools, except `ideas_to_page`
`discussions`	The `discussions_*` tools
`spaces`	The `spaces_*` tools
`links`	The `links_*` tools

Read, write and delete¶

Every tool tells the assistant whether it only reads, or whether it changes something. MCP clients receive these as standard tool hints (readOnlyHint, destructiveHint), and many use them to decide when to ask before running a tool. In this reference, each tool is marked as one of:

Marked as	Meaning
Read-only	Only reads. Nothing in Huddo changes.
Write	Creates or adds something, such as a page, an idea, a comment or a vote.
Overwrite	Replaces existing content or settings, such as a page body, an idea's text or notification settings.
Delete	Permanently removes something. It can't be undone.

There are 32 read-only tools, 20 write tools, 7 overwrite tools and 9 delete tools.

Require confirmation for write and delete tools

We recommend that you configure your MCP client to ask for your approval before it runs any tool that isn't read-only. Allow the read-only tools to run freely if you like, but keep write, overwrite and delete tools on "ask". In Claude Code and claude.ai, this is the default for tools that aren't marked read-only.

Delete safeguards¶

Every delete tool is permanent, so each one asks for a confirmation value that the assistant has to read from Huddo first: the exact name of the wiki or space, the title of the page or idea, the question of the lab, the file name, or the bookmark's URL. A value that doesn't match is refused. Each delete tool also tells the assistant to ask the user before calling it, and to say what will be removed (for example, how many child pages or ideas go with it).

Huddo's own permission checks still apply. A user can only delete what they could delete in the Huddo UI.

Things that apply to every tool¶

Naming things¶

Most tools let the assistant name what they act on in more than one way:

By URL. A Huddo URL, as shown in the browser. This is the simplest option when you paste a link into the chat.
By id or slug. Ids and slugs come back in the results of other tools, so an assistant can chain tools together. For example, it finds a page with wikis_find_pages and then reads it with wikis_get_page.

The parameter tables below show these as optional parameters. Give one of them.

Some cross-app tools name an object by url, or by service (wikis, ideas, spaces or links), objectType and objectId.

Text formats¶

Page bodies, idea descriptions and comments are read and written as Markdown.
Dates are ISO 8601. A since parameter takes either a date (2026-11-01) or a date and time with an offset (2026-11-01T09:00:00+10:00), and can't be in the future.

Results are capped¶

To keep answers small enough for an assistant, results are capped: lists hold a limited number of rows, and long text is cut short. A result says when something was left out (for example truncated, hasMore or nextCursor), and most list tools take a limit and a way to page on (offset, skip, page or cursor).

Content is data, not instructions¶

Pages, ideas and comments are written by people. Tools that return them tell the assistant to treat that text as quoted content, never as instructions to follow.

Errors¶

When a tool can't do what was asked, the assistant gets a short message instead of a result:

Message	Meaning
`Not allowed`	The user doesn't have permission for this.
`Not found`	The item doesn't exist, or the user can't see it.
`The user is not licensed for this app`	The user has no licence for the app the tool uses.
`API auth error: 401 (try reauthenticating)`	The sign-in has expired. Reconnect the assistant to Huddo.
A specific message	The input was wrong, for example a missing parameter or a confirmation value that doesn't match. The message says what to fix.