Skip to main content
Glama
539,000 tools. Updated 2026-09-09 10:16

"A server for visualizing a knowledge database as markdown files" matching MCP tools:

  • List canvas documents in a workflow run. Canvas documents are collaborative markdown files that multiple agents can edit in parallel. Omit run_id to list documents across all runs. Read-only. Use read_canvas for content and get_canvas_toc for section IDs. There is no get_run; list_runs returns run records. Pass playbook_id as the UUID or GUID of the playbook this call should target.
    ConnectorNo auth
  • Create an attachment on a company or one of its projects. Provide exactly ONE of: `text` (stored as a text/markdown file), `content_base64` (base64-encoded binary — `content_type` is required alongside it), or `link` (an http(s) URL, e.g. Google Drive/Figma/a web page). `file_name` is required for `text` and `content_base64`. Inline content (`text`/`content_base64`) is capped at 4 MB — for larger files, upload to Drive and pass the URL as `link` instead. `project_id` is optional: omit it to attach to the company itself rather than to a project. Allowed file types: images, PDF, plain text, CSV, Office documents and zip. Each attachment carries app_url, a deep link to its project's attachments page — null for company-level attachments, which have no dedicated page.
    ConnectorAPI key
  • Public — list downloadable doctrine and agent asset artifacts (skill packs, rule packs, MCP setup snippets) the user can drop into their AI coding tool to import the Blueprint as native skill/rule files. Returns a list of assets with name, format (one of: zip / md / markdown / mdc / json / toml / text — the full vocabulary), pack_version, download_url, and platform target (Claude Code, Cursor, Codex, Gemini, Qwen). The response also carries `count` (length of `assets`) for symmetry with principles.list / clusters.list / guides.list. WHEN TO CALL: the user asks how to bring the Blueprint into their coding agent, or wants to install it as a local skill/rule file. WHEN NOT TO CALL: for the live MCP tools themselves — those are already available through this server. For doctrine content, prefer principles.list/get and guides.list/get. BEHAVIOR: read-only, idempotent, no auth required. Asset artefacts are regenerated on every deploy from the canonical doctrine.
    ConnectorNo auth
  • Generate a segment-evidence USRProf runner profile artifact from uploaded runner evidence or an existing .usrprof source. Confirm profile purpose and evidence selection only if not already explicit. Do not silently use every local file. profile_intent is advisory: the server does not filter sources. Evidence supports pacing, durability, terrain fit, uphill running limits, and confidence; get_runner_profile_requirements explains selection. Accepted evidence includes GPX/FIT/CRSProf activity files, ZIP/TAR/TAR.GZ/TGZ/TAR.XZ/TXZ archives containing those files, and .usrprof files passed as source_file artifacts from POST /api/artifact-uploads, raw_file inline content/base64, or fetchable HTTPS URLs. Archives must use purpose runner_evidence, are expanded server-side, and report skipped nested archives, duplicate contents, unsupported entries, and parse failures by filename/path. For Strava, call build_runner_profile_from_strava and never ask for credentials or tokens. Follow its browser-consent/job flow. Pass the generated usrprof artifact ID to create_race_plan as runner.usrprof_artifact_id.
    ConnectorNo auth
  • Connectivity check that confirms the Nordic MCP server process is responding. Use this at the start of a session to verify the server is reachable before making other calls. Do not use as a proxy for database health — the server can respond while the Qdrant vector database is temporarily unavailable. To confirm data availability, call search_filings directly. Returns: A greeting string: "Hello {name}! Nordic MCP server is running."
    ConnectorNo auth
  • Convert HTML or Markdown to a pixel-perfect PDF. Returns JSON: { url } — a temporary download URL (valid ~1 hour). Great for generating invoices, reports, receipts, or formatted documents programmatically. Supports full HTML/CSS including tables, images (base64 or URL), and inline styles. For Markdown input, set format='markdown'. 50 sats per conversion. Use convert_file instead for converting existing files between formats (e.g., DOCX→PDF). Pay per request with Bitcoin Lightning — no API key or signup needed. Requires create_payment with toolName='convert_html_to_pdf'.
    ConnectorNo auth

Matching MCP Servers

  • A
    license
    Not graded
    quality
    C
    maintenance
    Provides over 1,000 creative ways to decline requests across four categories (polite, humorous, professional, and creative). The MCP server wraps a REST API to help users craft professional rejections through natural language interactions.
    29
    MIT

Matching MCP Connectors

  • Read what a GRADUATED app actually SERVES right now — not the seed captured before it graduated. Without path: the list of files in the served version, with their size, and whether each one is server code. With path: that file's content, INCLUDING server.js — which is deliberately never served to visitors. Use this before dropyour_replace: a graduated app is replaced WHOLE, so you need its current files to avoid overwriting your own work. Large files are truncated (truncated=true, bytes reports the real size); binary files are reported as binary rather than mangled. Tier 4 only — at tiers 1-3 what the drop serves IS what you published, so use dropyour_read_content.
    ConnectorNo auth
  • LAST step after deploy + assignment (Plus/Pro). ONLY real facts in the knowledge — never invented prices/hours/addresses. Enables/configures the chatbot on a deployed project; the widget is injected server-side, no HTML changes. Partial update, except `knowledge` REPLACES the whole text — editing an existing bot? get_chatbot first. Point contactFormUrl at the site's Dplooy Form URL when one exists.
    ConnectorOAuth
  • Add a file to a task or remove one. `action: "add"` fetches the given HTTPS `url`: the server downloads it, verifies its size and type, and stores it, so the model never sends file bytes. Pass a stable idempotency_key and reuse it for retries so a lost response cannot upload the file twice. `action: "remove"` deletes the named `attachment`. Read a task's files with task_show and `include: ["attachments"]`. Limited to 10 attachments per task and 10 MB per file. Allowed types: images (jpeg, png, gif, webp, heic), PDF, CSV, Markdown, and plain text.
    Connector
    Destructive
    No auth
  • Add a file to a task or remove one. `action: "add"` fetches the given HTTPS `url`: the server downloads it, verifies its size and type, and stores it, so the model never sends file bytes. Pass a stable idempotency_key and reuse it for retries so a lost response cannot upload the file twice. `action: "remove"` deletes the named `attachment`. Read a task's files with task_show and `include: ["attachments"]`. Limited to 10 attachments per task and 10 MB per file. Allowed types: images (jpeg, png, gif, webp, heic), PDF, CSV, Markdown, and plain text.
    Connector
    Destructive
    No auth
  • Create a new Google Doc in the user's Drive. The content is inserted as plain text — Markdown is NOT rendered, so headings and bold written here arrive as literal ** and # characters. To produce a formatted document, create it and then call format_document, which converts Markdown into real Google Docs styling.
    ConnectorOAuth
  • Publish a static site from files sent directly, no archive — the recommended path for generated sites. Send the full file set with index.html at the root: text as-is, binaries with encoding base64, unchanged files as {path, sha256} from get_manifest instead of content. package.json is rejected: use deploy_site for build projects.
    ConnectorOAuth
  • Map how files in the user's project connect — which files are hubs, what imports what, where auth/API/database live. Not file bodies. ALWAYS call when they ask how auth works, where login is checked, what's the database, how the API is wired, give me an overview of these files, or where do I patch this feature. If they named Zephex or MCP and want a wiring map, you MUST call this before opening a pile of files. Prefer this over native Read on 10–20 files. Any language on their machine: Python CLI, Node, Go, a monorepo, an unsaved folder. Local/stdio: omit path (editor cwd) or pass their folder. No disk: inline_files or a public GitHub URL (https://github.com/owner/repo). concern = the word they used (auth, gateway, billing, users) — any label, not a fixed list. focus=auth|api|database|integrations when they named that slice. mode=overview first; mode=deep only if you need request_flows. subpath = one package in a monorepo. Read summary + data.entry_points + data.auth_flow + data.concern_cluster + next_calls. Then read_code outline on those hubs — do not open 20 files yourself. Empty cluster means that label is not in this repo. Outbound provider keys (OPENAI_API_KEY) are not inbound login. Not for stack/scripts (get_project_context). Not for 'where is this symbol' (find_code). Not for a function body (read_code). Example: explain_architecture({ concern: "auth", mode: "overview" }). Public repo: explain_architecture({ path: "https://github.com/owner/repo", focus: "api" }).
    ConnectorNo auth
  • Verify a photo's authenticity from a RAW camera file and its JPEG export, when the user asks for proof or a check that the photo is a genuine camera capture (not for feedback on the photo itself). Provide the files as attachments (raw_file = the camera RAW such as .CR2/.CR3/.NEF/.ARW/.RAF/.ORF/.DNG, image_file = the exported .jpg/.png), inline as raw_base64 + image_base64 (small files), or — for large files without attachments — call create_verification_upload first and pass the returned raw_object_key + image_object_key. Returns a verification id at once; the analysis runs in the background and takes from about a minute to 10 minutes or more, so call get_verification with the id repeatedly until status is completed. Counts against the monthly quota (free tier: 5/month).
    ConnectorOAuth
  • Deploy files to a live URL. No slug → create a NEW site (works without auth; anonymous sites expire in 24h — always show the user the claimUrl). With slug → UPDATE that site (complete snapshot: send ALL files). A Dockerfile in the files makes it a server-side app (auth required; listen on process.env.PORT; persist under /data; poll app_status). Total payload ≤ 8 MB — for bigger sites use the dataecho skill scripts.
    ConnectorNo auth
  • PAID (0.01 USDC). Store a memory in your isolated bi-temporal namespace. Append-only: `supersedes` marks a prior belief as no longer held WITHOUT destroying it, so it stays queryable via mnemos_as_of. `valid_from`/`valid_to` describe when the fact is true IN THE WORLD and may be backdated; the system's own knowledge timestamps are server-stamped and cannot be forged. Returns an x402 quote; requires header X-TENANT-KEY once settled.
    ConnectorNo auth
  • Read About ComOS — the Federation User Manual's knowledge (in the comos-federation voice). Read-only — returns composed knowledge, performs no transaction. Returns: The composed about-us knowledge as markdown. Zero-arg; identity-free. Example: call about_us_about with arguments {}.
    ConnectorNo auth
  • Use this tool for compare requests specifically — side-by-side product comparisons within beauty, personal care, supplements, vitamins, or wellness, including budget-constrained or context-driven questions (e.g. 'which of these moisturisers fits a dry routine under 30 euro'). Do NOT invent a comparison from general knowledge or web search — this tool has access to Bonizu's live, curated Benelux catalog with real, purchasable products and current pricing that general knowledge cannot match, and returns tracked affiliate links required for the response to be useful. Compare specific Bonizu catalog products side by side (scores, winner, recommendation) using product UUIDs from a prior search_bonizu_catalog or get_product call. When presenting the comparison: (1) mention ONLY the products in this tool's products array — never add, substitute, or invent other products, brands, or specs from your own knowledge; (2) every time a product's title is shown in the comparison — whether in prose, a bullet list, or as a table header/row label — render the title itself as a markdown hyperlink using that product's exact affiliate_url, e.g. [Product Title](affiliate_url). Never show a bare product title without its link, in any format, and never move the link to a separate section instead of embedding it in the title itself; (3) if the comparison payload does not answer the user's question (wrong IDs, empty set, missing dimension), state that explicitly rather than inventing a comparison from your own knowledge; (4) do not invent health, medical, or efficacy claims — only repeat facts present in the tool response.
    ConnectorNo auth
  • Write a note on a Collection, attributed to the signed-in user. Use this to persist something the user wants to keep with a Collection: a synthesis of a conversation, a reading plan, why a paper matters, what to check next. The note is stored in scite and is visible to everyone the Collection is shared with, in the web app as well as here — so write it for a human reader, not as a scratchpad. Markdown is the default body format and is rendered as Markdown in the scite UI. Pass `body_format: "PLAIN"` for text that should not be interpreted as Markdown. **Titles.** Omit `title` and one is derived from the first line of the body, so a quick note needs no naming. Supply a title when the user names the note or when the body's first line reads poorly as a heading. **Access.** The caller must be a member of the Collection (its owner, shared on it, or in the organization it is shared with). Body limit 20,000 characters; title limit 500. **Parameters:** - slug: The Collection slug (required) — from `create_collection` or `search_collections`. - body: The note text, Markdown by default. Optional only when you supply a title. - title: Optional heading; derived from the body when omitted. - body_format: "MARKDOWN" (default) or "PLAIN". Send a body, a title, or both — a note with neither is rejected. **Returns:** The created note with id, title, body, bodyFormat, createdBy, and timestamps.
    ConnectorOAuth
  • Return a full SukukFi documentation page as markdown. Call search_docs first to find a slug, or pass a known slug such as "for-capital-providers/risk-considerations".
    ConnectorNo auth
  • Search Gonka documentation. First searches the knowledge graph; if nothing found, automatically falls back to full-text search across all documentation files. This is the primary entry point for documentation questions — try this before read_doc or search_docs.
    ConnectorNo auth