Skip to main content
Glama
freeqaz

shared-wiki-mcp

by freeqaz

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
WIKI_VAULTNoPath to the wiki vault. Defaults to 'vault' in the current directory. Can also be set via the --vault command-line option.vault

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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
wiki_searchB

Search note titles and content; return ranked excerpts and status.

wiki_readB

Read body lines, metadata, hash, links, parents and backlinks of a note.

wiki_contextB

Gather bounded source excerpts for a question. The host composes the answer.

wiki_review_queueB

Rank open questions by a transparent heuristic of impact, uncertainty and time.

wiki_changesB

List notes updated since a Unix millisecond timestamp. Not a semantic diff.

wiki_captureB

Save user feedback as an unreviewed inbox note; source_ref is provenance, not authenticated identity.

wiki_proposeB

Create a separate proposed replacement after reading the current target. Never overwrites it.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.4/5.0

Scored across 7 tools

Disambiguation4/5

Each tool targets a distinct operation: search for discovery, read for a single note's body/metadata, context for bounded multi-source excerpts, changes for a time-based delta, capture for inbox writes, propose for replacement drafts, review_queue for ranking open questions. The only soft overlap is wiki_search vs wiki_context (both return excerpts), but the descriptions clarify that one is ranked retrieval and the other is question-scoped gathering.

Naming Consistency4/5

All seven tools share the wiki_ prefix and snake_case, giving a predictable namespace. However, the second element mixes verbs (search, read, capture, propose) with nouns (review_queue, changes, context), so the verb_noun pattern is not uniformly applied.

Tool Count5/5

Seven tools is a tight, well-scoped surface for a shared wiki: retrieval, inspection, review, change tracking, and two write paths. Every tool maps to a real workflow step with no filler.

Completeness3/5

Read/discovery/write-capture are covered, but two lifecycle paths dead-end: wiki_propose creates a proposed replacement with no tool to list, accept, or reject proposals, and wiki_review_queue surfaces open questions with no tool to answer or resolve them. Agents can work around this by reading and capturing notes, but the review/proposal loop is incomplete.

Maintenance

ActivitySlowing
ResponsivenessNo issues