Skip to main content
Glama
mwe-support

WeKnora MCP Dispatch

by mwe-support
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to WeKnora MCP Dispatch

No user-submitted related servers found.

    Related Servers

    • mcp-streamable-http-bridge

      elad-bar
      F
      license
      Not graded
      quality
      B
      maintenance
      Bridges stdio Model Context Protocol (MCP) servers to MCP Streamable HTTP behind a single gateway, enabling multi-tenant, multi-user deployment with per-tenant environment variables via HTTP headers.
      -
    • AISIX AI Gateway by api7

      AISIX AI Gatewayofficial

      api7
      A
      license
      A
      quality
      A
      maintenance
      Self-hosted MCP gateway that registers upstream MCP servers and fronts them behind one governed Streamable HTTP endpoint: per-tool access control by caller API key, guardrails over tool arguments and results, rate limits, and usage logs. The same Rust gateway also proxies LLM and A2A agent traffic.
      4
      1
      157
      Apache 2.0

    • ChatATP Studio MCP Server

      sam-14uel
      F
      license
      Not graded
      quality
      C
      maintenance
      Exposes ChatATP Studio's backend API as MCP tools over Streamable HTTP, enabling clients to manage agents, knowledge bases, MCP connections, HTTP APIs, LLM providers, messaging platforms, and teams with forwarded authorization.
      -

    • nodus-mcp

      BlaineHeffron
      A
      license
      A
      quality
      B
      maintenance
      A thin stdio gateway to Nodus's Streamable HTTP MCP server, exposing a curated allowlist of tools for the Research Workbench. It enables secure, bearer-authenticated interactions with Nodus without graph logic or caching.
      1
      MIT

    • LKPlanWise MCP Server

      luecha-work
      F
      license
      Not graded
      quality
      C
      maintenance
      Stateless MCP adapter for the LKPlanWise Go REST API, enabling AI agents to call curated financial tools via Streamable HTTP while forwarding bearer credentials.
      -
    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

    C2.7/5.0

    Scored across 28 tools

    Disambiguation4/5

    Most tools target distinct resources (knowledge bases, knowledge items, sessions, agents, models, wiki). The only real overlap is list_knowledge vs list_chunks and possibly chat vs agent_chat, but the descriptions help differentiate these.

    Naming Consistency4/5

    The majority follow a verb_noun snake_case pattern (get_, create_, delete_, list_). Minor deviations like chat, agent_chat, and wiki_index_view are still readable and do not break the overall consistency.

    Tool Count2/5

    With 28 tools, the set exceeds the recommended 25-tool threshold and feels heavy. While the broader domain (knowledge, chat, agents, wiki, models, tenants) justifies some size, the number is still unwieldy for an agent to navigate efficiently.

    Completeness3/5

    The surface covers core CRUD for knowledge bases and knowledge items, but lacks update operations for most resources (e.g., update_knowledge, update_model, update_agent). Agent management includes only inspection, and wiki lacks editing capabilities, leaving notable gaps.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources