burrow
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LEAFWIKI_URL | No | Wiki root, e.g. `https://wiki.example.com`. `https` only, except `localhost`. | |
| BURROW_READ_ONLY | No | Set to `true` to register only the `read_` tools. | |
| LEAFWIKI_PASSWORD | No | Your LeafWiki password. Keep it in your environment, never in a shared file. Required when the wiki has sign-in. | |
| LEAFWIKI_USERNAME | No | Your LeafWiki username or email. Required when the wiki has sign-in. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| read_wikiA | Who is signed in (username, role) and which wiki features are on (revisions, link refactoring, upload size). |
| read_treeA | Page hierarchy as indented lines with path and id, for the whole wiki or below one page. |
| read_pageA | One page: Markdown content, tags, properties, authors and the version needed to change it. |
| read_lookup_pathC | Whether a path exists, segment by segment, and whether it can be created. |
| read_find_titleA | Pages whose title matches exactly (case-insensitive), with path and id. |
| read_searchA | Full-text search over page titles, content and tags, best match first, with excerpts. |
| read_search_statusB | Whether the search index is still building, and how many pages it holds. |
| read_tagsB | Tags in use with how many pages carry each. |
| read_pages_by_tagsC | Pages carrying all of the given tags. |
| read_propertiesB | Property keys in use (structured page metadata) with how many pages set each. |
| read_pages_by_propertyC | Pages that set a property, optionally to one value. |
| read_linksB | A page's links: pages linking to it, pages it links to, and broken links both ways. |
| read_broken_linksB | Every broken link in the wiki (admins only). |
| read_revisionsA | A page's revision history, newest first (needs revisions on). |
| read_revisionB | One past revision of a page with its full content. |
| read_compare_revisionsA | Line diff between two revisions of a page, or between one revision and the latest. |
| read_favoritesB | The signed-in user's favorite pages. |
| read_assetsC | Files attached to a page, with the URL to embed or link them. |
| read_slugC | The slug LeafWiki would give a title, unique under its parent (editors only). |
| read_refactor_previewA | Which pages link to a page and would be rewritten if it were renamed or moved (needs link refactoring on); changes nothing. |
| write_create_pageB | Create a page (or section) under a parent, optionally with content, tags and properties. |
| write_ensure_pathA | Make sure a path exists, creating every missing segment; the last one gets the title. |
| write_update_pageA | Change a page's title, slug, content, tags or properties; fields you leave out stay as they are. |
| write_edit_textA | Replace one exact passage of a page's content, without sending the whole page. |
| write_appendB | Add Markdown at the end of a page. |
| write_tagsB | Add or remove tags on a page, keeping the others. |
| write_propertiesB | Set or remove properties (structured metadata) on a page, keeping the others. |
| write_moveA | Move a page (with its children) under another parent; links to it are not rewritten (see write_refactor). |
| write_sortC | Set the order of the children of a page. |
| write_pinB | Pin a page to the top of its siblings, or unpin it. |
| write_favoriteB | Add a page to the signed-in user's favorites, or remove it. |
| write_convertB | Turn a page into a section or a section into a page. |
| write_copyB | Copy a page (content, tags, properties, files) under a parent with a new title. |
| write_refactorA | Rename or move a page and rewrite the links that point to it (needs link refactoring on; preview with read_refactor_preview). |
| write_restore_revisionA | Bring a page back to a past revision (the current state stays in the history). |
| write_upload_assetA | Attach a file to a page from base64 data; answers with the Markdown link to embed it. |
| write_rename_assetC | Rename a file attached to a page. |
| delete_pageA | Delete a page; a page with children is refused unless recursive is true. |
| delete_assetC | Delete a file attached to a page. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 39 tools
Tools are mostly distinct by resource and action, and descriptions clarify overlaps. Some boundaries are close, such as update_page/edit_text/append for content changes and read_links/read_refactor_preview for incoming links, but agents can generally choose correctly.
Names consistently use snake_case with clear read_, write_, and delete_ prefixes. The operation naming is predictable throughout, even when some write actions are verb-only rather than verb_noun.
At 39 tools, the surface is far above the typical 3-15 range and beyond the heavy 16-25 band. While the wiki domain is broad, the tool count creates significant context and selection overhead.
The set covers page CRUD, hierarchy, tags/properties, links and refactoring, revisions, assets, favorites, search, and auth/feature status. Standard wiki workflows have no obvious dead ends.