Skip to main content
Glama
helv-io

skgate

by helv-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Remote

Related Servers

Alternatives to skgate

  • mcphub

    samanhappy
    A
    license
    Not graded
    quality
    A
    maintenance
    A unified hub for centrally managing and dynamically orchestrating multiple MCP servers/APIs into separate endpoints with flexible routing strategies.
    1,377 npm
    2,587
    Apache 2.0

Related Servers

  • Junctio

    k2so-dev
    A
    license
    Not graded
    quality
    A
    maintenance
    Self-hosted MCP gateway that unifies stdio, Docker, and remote MCP servers behind one endpoint per client, with proactive OAuth refresh and no telemetry.
    4
    MIT

  • McpMux

    mcpmux
    A
    license
    Not graded
    quality
    A
    maintenance
    McpMux is a desktop app that runs a local MCP gateway. You configure servers once — every AI client connects through a single URL.
    23 npm
    25
    GPL 3.0

  • Universal MCP Gateway

    Samuel-Mencke
    F
    license
    Not graded
    quality
    D
    maintenance
    A self-hosted MCP gateway that aggregates all your MCP servers behind a single Streamable HTTP endpoint, with automatic registry discovery (19,000+ servers), on-demand Docker provisioning, multi-device support via SSH, OAuth2 PKCE authentication, and a workflow engine for saving and replaying multi-step tool sequences.
    -

  • Grok Codex

    Meapri
    A
    license
    A
    quality
    D
    maintenance
    MCP server for integrating xAI's Grok model into OpenAI Codex Desktop/GUI, enabling direct Grok calls via chat completions or responses with OAuth or API key authentication.
    9
    MIT
Deploy Server
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

TDQS

A4.1/5.0

Scored across 3 tools

Disambiguation4/5

All three tools are read-only introspection, but they target distinct surfaces: product metadata (about), feature inventory (list_features), and environment variables (config_help). 'about' and 'list_features' are the closest pair since about returns a summary and mode while list_features returns feature entries, but the descriptions draw a workable line and about is explicitly an entry point.

Naming Consistency3/5

The names mix conventions: 'about' is a bare preposition/noun, 'list_features' is verb_noun, and 'config_help' is noun_noun. All are lowercase snake-ish and readable, but there is no predictable pattern an agent could extrapolate from.

Tool Count3/5

Three tools is thin for a server whose whole purpose is explaining a product, though each is scoped to a different information source with no redundancy. It sits at the borderline rather than being clearly under- or over-provisioned.

Completeness3/5

The surface is deliberately offline and binary-only, so it cannot read live environment values, enumerate configured MCP servers/tools, or validate an actual running config. Documentation lookup is covered, but agents that need to inspect or verify a running skgate instance hit a dead end.

Maintenance

ActivityMaintained
ResponsivenessResponsive

Resources