Skip to main content
Glama
NeonSummit

UserGate MCP

by NeonSummit
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to UserGate MCP

No user-submitted related servers found.

    Related Servers

    • doc-index

      mike-anderson
      A
      license
      Not graded
      quality
      B
      maintenance
      A local-first semantic search server for documents, supporting PDFs, Office files, and text/markdown, enabling natural language search via the Model Context Protocol (MCP).
      1
      MIT

    • ragi

      SusuTawar
      A
      license
      A
      quality
      D
      maintenance
      Local-first RAG indexing and semantic search MCP server. Enables document retrieval and context-aware queries using local embedding models.
      3
      6 npm
      MIT

    • Documents MCP Server

      corneyc
      A
      license
      Not graded
      quality
      D
      maintenance
      A production-ready Model Context Protocol server that bridges local document management with cloud synchronization (Notion) for AI agent integration, enabling seamless access and sync of local and cloud documents.
      11 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.1/5.0

    Scored across 18 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: get_doc and get_doc_section target different granularities, list_ tools cover different catalog types and facets, and each prepare_* tool addresses a specific troubleshooting or planning scenario. There is no overlapping functionality.

    Naming Consistency4/5

    Tool names follow a consistent verb_noun pattern (e.g., get_doc, list_documents_catalog, search_docs) with only minor deviations: 'prepare_change_research' lacks a 'pack' suffix unlike other prepare tools, and 'get_project_status' uses a slightly different noun structure. Overall naming is predictable and readable.

    Tool Count5/5

    With 18 tools, the set is well-scoped for a documentation and troubleshooting pack server. It covers search, listing, retrieval, and specialized pack generation without being overwhelming or sparse.

    Completeness4/5

    The tool surface covers all expected operations for the domain: browsing catalogs, searching docs, retrieving content, and generating targeted troubleshooting packs. Minor gaps exist, such as no direct tool to list generated packs, but the core workflows are fully supported.

    Maintenance

    ActivityStale
    ResponsivenessSyncing

    Resources