Skip to main content
Glama

Server Details

Serve a folder of Markdown notes as an MCP server: hybrid search, reading, and sourced answers.

If you are the author of this connector, you can claim ownership. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
Repository
trip2g/trip2g
GitHub Stars
41
Server Listing
trip2g
ChatGPT
–
Claude
–

TDQS

B3.4/5.0

Scored across 12 tools

Disambiguation4/5

The local/federated split is crisp: search/note_html/expand/similar/instructions each have a clear remote mirror (federated_*), and the descriptions spell out canonical call chains that make the search -> note_html -> expand workflow unambiguous. The only real overlap is between 'instructions' ('Full tool reference for the trip2g documentation base') and 'wiki' ('Wiki Knowledge Base Instructions'), plus 'federated_instructions', which an agent could plausibly confuse.

Naming Consistency3/5

The federated_* family is perfectly consistent and predictable, mirroring local tools one-to-one. However, the base tools mix conventions: verbs (expand, search), noun_verb (note_html), and bare nouns (instructions, wiki, similar), so no single verb_noun pattern governs the set.

Tool Count5/5

12 tools is well within a healthy range and each earns its place: six local operations plus their federated counterparts for remote bases, plus one extra for remote attachments. The duplication is purposeful (different scopes), not redundant.

Completeness4/5

The read/discovery lifecycle is well covered for both local and federated bases: search, read (full/chunk/section), structure walking, similarity, and instructions. The one visible gap is that attachments can be fetched remotely (federated_asset) but there is no local counterpart, and write operations are absent (acceptable for a read-only documentation base).

Available Tools

12 tools
expandAInspect

Walk a note's table of contents level by level (progressive disclosure). Canonical call: expand(path=<result.note_path>, toc_path=[...]) — copy path verbatim from a search result's note_path field. Returns the direct children of a TOC node: omit toc_path (or pass []) for the top-level sections, or pass a toc_path to list that section's subsections. Each child has title, level, path, and has_children. A section with subsections lists them; a section without subsections is returned in full (what note_html gives for that toc_path, plus section_html in the payload), so no second call is needed to read a leaf. This cannot be turned off, and a client that wants only structure never triggers it: has_children on each listed child says where descending would turn into reading.

Inputs: pid, href, last, path, +3 more.

federated_assetAInspect

Get one attachment of a remote note — a file, not text. Canonical loop: federated_note_html(kb_id, path) -> for each name in its assets: federated_asset(kb_id, note_path=, name=). Returns the asset's size and sha256 and a short-lived download URL on this server that streams the file from the remote base; fetch it with curl (the URL needs no other credential) and check the sha256. The file itself never comes back in the tool result. Only a directly connected base: kb_id without '/'.

Inputs: name (required), kb_id (required), note_path (required).

federated_expandAInspect

Walk a remote note's table of contents level by level inside a connected knowledge base (progressive disclosure), same as expand. Canonical call: federated_expand(kb_id=..., path=<result.note_path>, toc_path=[...]). Omit toc_path for the top level, or pass a toc_path to list that node's subsections. A section with subsections lists them; a section without subsections is returned in full, as federated_note_html would return it — has_children on each listed child says where that happens.

Inputs: kb_id (required), pid, href, last, +4 more.

federated_instructionsAInspect

Fetch the instructions/guidance for a federated knowledge base by kb_id (e.g. "philosophers/nietzsche") — read a base's own conventions before searching it. Nested bases are addressed with '/' and the call routes through each peer recursively.

Inputs: kb_id (required).

federated_note_htmlAInspect

Read a remote note inside a connected knowledge base. Canonical call, copying fields verbatim from a federated_search result: federated_search(kb_id="philosophers/", query) -> federated_note_html(kb_id="philosophers/", path=<result.note_path>) — the standard way to descend into a leaf corpus and read real content there, not hub cards. federated_note_html(kb_id=..., match_id=<match.match_id>) reads just the focused chunk around a hit. Only pass pid/note_id if you already copied that exact id from a result. path is a string like "concepts/x.md"; match_id is "p:c"; a value like ":" or "/hub/goethe.md" is a PATH, not a note_id.

Inputs: kb_id (required), pid, href, path, +3 more.

federated_similarAInspect

Find remote notes similar to a known note reference inside a connected knowledge base. Preferred: path (a federated_search result's note_path field).

Inputs: kb_id (required), pid, href, path, +2 more.

instructionsCInspect

Full tool reference for the trip2g documentation base

note_htmlAInspect

Read a note. Canonical calls, copying fields verbatim from a search result: search(query) -> note_html(path=<result.note_path>) reads the whole note; search(query) -> note_html(match_id=<match.match_id>) reads just the focused chunk around a hit (cheaper, targeted); expand(path=<result.note_path>, toc_path=[...]) -> note_html(path=<result.note_path>, toc_path=[...]) reads one exact section. Only pass pid/note_id if you already copied that exact integer from a result's note_id field — never invent one. path is a string like "concepts/x.md"; match_id is "p:c"; a value like ":" or "/hub/goethe.md" is a PATH, not a note_id.

Inputs: pid, href, path, note_id, +3 more.

similarBInspect

Find related notes from a known note reference. Preferred: path (a search result's note_path field). Use this after opening a promising note when you need nearby context.

Inputs: pid, href, path, limit, +1 more.

wikiCInspect

Wiki Knowledge Base Instructions

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Turns markdown note directories into an MCP knowledge assistant server, enabling hybrid search, explanations, quizzes, and comparisons for any MCP-compatible AI tool.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Serves a folder as an MCP knowledge server: it indexes text, code, PDFs, office documents and audio or video, then answers search and ask calls with citations that name the file, the line range, the page or the time range. Runs fully local with Ollama by default; Mistral, OpenAI, Gemini and Anthropic are optional providers.
      4
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      Enables hybrid dense and BM25 search over a markdown vault, with tools for reading, writing, grepping, and managing notes through any MCP-compatible client.
      12
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables MCP-capable clients to search a folder of Markdown notes with hybrid full-text and embedding retrieval, plus read, write, append, and reindex operations that keep a single shared SQLite index in sync with the files.
      9
      2
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.