Skip to main content
Glama
604,334 tools. Updated 2026-09-23 18:48

"Creating a Document as a Knowledge Base" matching MCP tools:

  • [Knowledge base] Upload and process a knowledge base document (multipart form-data). Uploads a document to a knowledge base store and queues it for processing. Accepts the file either as multipart/form-data (binary `file`) or as application/json (base64 `file`).
    Connector
    Destructive
    No auth
  • Permanently delete one knowledge base entry and every passage built from it. The chatbot stops using that content immediately. This cannot be undone.
    Connector
    Destructive
    OAuth
  • Deep knowledge-base compliance audit (async; 2 credits). Produces a thorough, written risk report covering prohibited words, IP, category mismatches, GPSR and more, backed by a private 15-year compliance knowledge base. Use this when you need a complete, actionable compliance report. Do NOT use it for a quick pre-publish check - use compliance_check for that. Read-only; deducts 2 credits; runs asynchronously, poll for the result. Args: text: listing title/bullets/description (required). marketplace: marketplace code (default US). category: optional category hint. lang: zh or en (default en). images: optional list of up to 5 data:image base64 strings, each < 4MB.
    ConnectorNo auth
  • Connects an EXISTING knowledge base to something that will use it. It adds no content — for that use findagent_add_kb_document, which puts a document into the base itself. Attach a knowledge base you own to an agent or department you own, to an organization you administer (org KB — auto-available to every agent/department run for the org’s active members), or bind it as your personal KB. Identify an agent/department target by target_slug (recommended) or target_id from findagent_list_my_agents; identify an org target by its slug/id from findagent_list_orgs (you must be an org owner or admin). Choose mode: tool (the agent gets a search_knowledge tool), auto_inject (relevant passages are prepended before the call), or both. This is NOT part of the agent manifest, so updating the KB needs no agent re-publish.
    ConnectorOAuth
  • Validate a schedule document against provider rules, media limits, account state, and publish times WITHOUT creating any posts. Always run this before apply_schedule.
    ConnectorNo auth
  • List merchant knowledge base documents (uploads + scraped URLs). Use reviewStatus/syncable to see what is ready for agent retrieval. Pass `updatedAfter` for delta sync. Reviewed content is fetched via GET /v6/merchant/ai/knowledge/{id}/content; source audit text is available with ?variant=extracted.
    ConnectorNo auth

Matching MCP Servers

Matching MCP Connectors

  • A searchable knowledge base your assistant reads and writes.

  • AI agents hire a human to observe, log or film on site. Typed results, feasibility before payment.

  • List the taxonomy domains the company has indexed — with document counts, expert counts, and coverage levels — so an agent can decide whether to query before spending a Knowledge Token. Returns one row per domain with the canonical `taxonomy_domain` slug, document/chunk counts, expert count, coverage level (expert | partial | none), the single_expert risk flag, and the top contributor by authority. Use the slug as the `domain` filter on a follow-up `query_knowledge` call. Zero Knowledge Tokens consumed.
    ConnectorNo auth
  • List merchant knowledge base documents (uploads + scraped URLs). Use reviewStatus/syncable to see what is ready for agent retrieval. Pass `updatedAfter` for delta sync. Reviewed content is fetched via GET /v6/merchant/ai/knowledge/{id}/content; source audit text is available with ?variant=extracted.
    ConnectorNo auth
  • Get a compendium document as a readable summary: actors come back as a statblock (HP, AC, abilities, attacks), other types as core fields plus system data. For the complete raw JSON use compendium-document-get-raw, or uuid-resolve when you already hold the document UUID (what the filter tools return). Use compendium-browse to find document IDs.
    ConnectorAPI key
  • Render a document template’s DRAFT against sample values and show the result to the user as a visual preview in the chat. Pass realistic sampleValues (field slug → value; arrays drive repeatSection, numbers drive conditions); missingFields in the result lists fields the samples did not cover. Use after creating or editing a template so the user sees the document before publishing. Requires document:write.
    ConnectorAPI key
  • Add a local file's content to a knowledge base (txt/md/html/pdf/docx). **This MCP runs on the platform server and cannot read paths on YOUR machine.** For text files, read the content yourself and call `add_knowledge_text`; for binaries (pdf/docx), upload via the console, or curl `/knowledge-bases/{name}/documents/upload`. **To ingest a whole folder, zip it and send that one endpoint** — subdirectories are walked, md/txt/pdf/html/docx are ingested one by one, and document names use the in-archive relative path (`2025/rates.pdf` vs `2026/rates.pdf` therefore never collide). Images, `.DS_Store` etc. inside the zip are ignored; if the archive contains an encrypted, corrupt or abnormally high-compression file, **the whole archive is rejected** naming the offending entry.
    ConnectorNo auth
  • Puts CONTENT INTO a knowledge base. This is not the tool that makes a knowledge base reachable from an agent — that is findagent_attach_kb, which connects an existing base to an agent, department or organization. Add a text document to a knowledge base you own by pasting its content. It ingests asynchronously (parse → structure-aware chunk → embed with the KB’s bound key). Content is de-duplicated by hash: re-adding the exact same text is a no-op (the response `deduped` flag is true, no second document). Requires the KB to have an embedding key bound, or the document will not ingest. For files (PDF/markdown/docx), use the web Knowledge Base uploader.
    ConnectorOAuth
  • Get AI style feedback on requirements content against the project's style rubric. Pass 'markdown' to check content you're composing BEFORE creating/editing a document (recommended), or 'document' to check a document's published content. Provide exactly one of the two.
    ConnectorOAuth
  • Get the current knowledge-base snapshot/version id. Pin this kb_snapshot for reproducibility: the same query against the same kb_snapshot returns identical results.
    ConnectorNo auth
  • Soft-delete a knowledge document. The agent loses access immediately, but the document can be restored with restore_knowledge_document.
    Connector
    Destructive
    No auth
  • Get summary statistics of the Klever VM knowledge base. Returns total entry count, counts broken down by context type (code_example, best_practice, security_tip, etc.), and a sample entry title for each type. Useful for understanding what knowledge is available before querying.
    ConnectorNo auth
  • Soft-delete a knowledge document. The agent loses access immediately, but the document can be restored with restore_knowledge_document.
    Connector
    Destructive
    No auth