Skip to main content
Glama
681,155 tools. Updated 2026-10-20 12:45

"Exploring Paperless Solutions" matching MCP tools:

  • Establish traceability between user problems and planned solutions by linking or unlinking evidence items to intents.
    MIT
  • List Power Apps solutions in an environment, filtering by name and optionally including managed solutions.
    MIT
  • Open a discussion thread in DebugBase to get help from other AI agents. Describe your problem and receive solutions from the collective knowledge base.
    MIT
  • Semantically search the SHOAL oracle and fleet vector index for patterns, crates, solutions, and knowledge. Returns ranked results with conservation metadata.
    MIT
  • Retrieve and filter posts from the NaN Mesh trust network by type, agent, category, or unanswered status to find articles, questions, problems, solutions, ads, and spotlights.
    MIT
  • Submit a symptom, feature, platform, or error message for an @appolabs/appo SDK integration problem and get a diagnosis with solutions and code fixes.
    MIT

Matching MCP Servers

  • A
    license
    A
    quality
    B
    maintenance
    Provides eight deterministic, source-grounded tools for exploring the Beautiful Solutions toolbox, enabling organizers and educators to search, compare, map, and build discussion guides around liberation-focused values, principles, solutions, and stories without runtime LLM or network calls.
    8
    1
    MIT
  • A
    license
    Not graded
    quality
    C
    maintenance
    A read-only and write MCP server for Paperless-ngx, enabling document listing, metadata retrieval, and creation of tags, correspondents, document types, and sorting workflows via natural language.
    MIT

Matching MCP Connectors

  • Analyze vault structure to identify folder layouts, note counts, and navigation content for exploring personal knowledge bases.
    MIT
  • Get a comprehensive overview of the Fortnox API including base URL, authentication, rate limits, and resource groups to understand the API before exploring specific endpoints.
    MIT
  • Send custom requests to any paperless-ngx REST endpoint. This escape hatch covers workflows, share links, mail rules, trash, permissions, and other operations not handled by dedicated tools.
    MIT
    Destructive
  • List all schemas in a connected PostgreSQL database to identify available namespaces before querying tables. Use it as the first step when exploring an unfamiliar database.
    MIT
  • Check Paperless-ngx server health and version. Retrieve storage details, database, search index, classifier, and task queue status to identify the running version.
    ISC
  • Retrieve OCR-extracted text for a specific document after narrowing your search. Use offset and limit to page through long documents, reducing costly Paperless-ngx requests.
    MIT
  • Create a discrete Paperless-NGX workflow action (assignment, email, webhook, or trash) to serve as a reusable automation step. Use it when configuring workflows for document processing.
    ISC
  • Retrieve technical file metadata for a Paperless-ngx document: checksums, byte sizes, MIME type, stored filename, archived PDF/A status, and embedded PDF metadata.
    MIT
  • Create a single standalone Paperless-ngx workflow trigger. It has no effect alone; build automations with create_workflow or edit triggers inside workflows.
    ISC