Skip to main content
Glama

Related Servers

Alternatives to Jules MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Exposes any stdio-based MCP server to the internet via HTTP/SSE transport, enabling remote agents to access MCP tools over a network.
      29 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Coordinate and verify OpenCode worker agents over MCP Streamable HTTP. The bridge lets compatible AI harnesses dispatch scoped work, inspect progress, run approved commands, and verify results through a safe worker-only endpoint.
      2
      PolyForm Noncommercial 1.0.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI clients to interact with EDA projects via natural language by wrapping EDI's gRPC interface, CLI tools, and ANSYS HFSS as MCP tools supporting SSE and stdio transports.
      3
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables secure exposure of internal tools to LLM clients with API-key authentication, tenant isolation, per-tool guardrails, PII scrubbing, rate limiting, audit logging, and telemetry over stdio and HTTP/SSE.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Exposes remote, agent-facing MCP endpoints over Streamable HTTP for web search, webpage parsing, local knowledge-base retrieval and document creation, and delegation of tasks to configurable LLM providers. Also bundles an admin console with onboarding, provider/model configuration, API-key management, and call logging.
      MIT

    TDQS

    C2.9/5.0

    Scored across 13 tools

    Disambiguation2/5

    Several tools have unclear boundaries, especially list_activities vs list_all_activities and list_sources vs get_all_sources, which appear to perform nearly the same listing operation with only subtle pagination differences. Descriptions do not clearly explain when to choose one over the other.

    Naming Consistency4/5

    Most names follow a consistent snake_case verb_noun pattern (list_sessions, get_session, create_session, delete_session). Minor deviations exist: get_all_sources uses 'get' for a list operation, and list_all_activities/list_activities plus list_sources/get_all_sources introduce inconsistent list vs get_all phrasing.

    Tool Count4/5

    13 tools is reasonable for a session/activity/source management server. However, the redundant auto-pagination variants slightly inflate the count, meaning not every tool clearly earns its place.

    Completeness4/5

    Core session lifecycle is covered with create, get, list, delete, bulk cleanup, plan approval, and messaging. Activities and sources are read/list-oriented, which may be appropriate if they are externally managed, but there is no update or termination operation beyond delete.

    Maintenance

    ActivityStale
    ResponsivenessNo issues