The liveknowledge MCP Tools

The tools an AI agent gets from the liveknowledge MCP server, what each returns and which scope it needs.

Applies To

liveknowledge

The liveknowledge MCP server, at https://mcp.liveknowledge.app/mcp, speaks in pages. Every answer about a page or a passage says how far it can be trusted, so an agent can tell a verified answer from a stale one. To connect a client, see Connecting an Agent.

The Page Tools

ToolWhat it doesScope
get_contextThe Always in Context pages, whole, as Markdown, in tree order and within 8,000 tokens; the caller's role and scopes; the Review Period. Call it firstread
list_pagesThe page tree: each page's id, title, depth, parent, subpage count, owner and trust, and the Review Period onceread
search_pagesPassages that match a query: titles first, then passages, verified pages before others, each with its page and headingsread
read_pageOne page as Markdown, with the pages that link to it and its subpagesread
report_gapRecords a question the Knowledgebase does not answer, for Questions Nobody Could Answer. Changes no pageread
create_pageA new page from Markdown, under a parent or at the top level. Never Verifiedsuggest
suggest_editA change to a page, with a reason: replace a passage (old_text with new_text) or append. Waits for a personsuggest
write_pageReplaces a page's writing with Markdown, or appends to it, at once. Never on a Verified or Review Due pagewrite
move_pageMoves a page and its subpages to another parent or the top level, before a named sibling or lastwrite

A page is named by its id, or by its title where one page alone has that title. [[Title]] in Markdown is a link to the page of that title.

The Trust Fields

Every page and passage in an answer carries:

FieldMeans
verifiedverified, review-due or never-verified
verified_atWhen it was last verified
verified_byWho verified it (on read_page)
review_dueWhen its review comes due, from the Knowledgebase's Review Period
staletrue when the review is due
conflicts_withThe pages it disagrees with, while a disagreement is open

get_context and list_pages also give the Review Period once, as review_period: 30 days, 90 days, 180 days, 365 days or never. No tool sets it.

What an agent reads back from search_pages: the passage, its page and heading, and its trust.

Small Answers

Answers are small unless the agent asks for more, and each names the tool to call next.

ToolBy defaultAt most
search_pages8 passages20
list_pages100 pages500
read_pageThe first 6,000 charactersPass heading for one section, or a larger max_chars

A search is at most 200 characters, a gap's question 1,000, a suggestion 20,000 characters with a reason of 500.

The Scopes

read covers the five read tools; suggest adds create_page and suggest_edit; write adds write_page and move_page. A connection your AI tool makes holds read and suggest. Only an Editor grants write, for one connection in one Knowledgebase. A person's role still bounds the agent: a Viewer's agent only reads. See What Agents Can Do.

The Knowledgebase Tools

Besides the page tools, the server has the tools every liveworkspace app has, in a Knowledgebase's words: find_documents, create_document, rename_document, share_document, archive_document, unarchive_document, delete_document, restore_document, list_trash and list_templates, the comment tools list_threads and change_threads, and the picture tools list_images, upload_image and delete_image. Sharing, archiving and deleting a whole Knowledgebase need a full token, whatever the scopes.

Good to Know

  • Every read an agent makes is counted for Connected Agents, under the name its client gives.
  • A search that finds nothing is recorded as a question nobody could answer.
  • The tool descriptions tell an agent what to do: call get_context first, prefer a verified passage, say so when it relies on a stale one, and report a gap rather than guess.

Was this article helpful?

Still need help?

Try Troubleshooting, or tell us what you were trying to do.

Contact us