Skip to main content
Glama

smplkit MCP Server

by com.smplkit
OverviewDiscussionsAdmin

Server Details

Operate smplkit from your agent: feature flags, config, logging, audit, and scheduled jobs.

Ownership verified

Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Last Tested
Transport
Streamable HTTP
URL
Repository
smplkit/mcp
GitHub Stars
0
Server Listing
smplkit MCP Server

TDQS

A3.7/5.0

Scored across 29 tools

Disambiguation5/5

Every tool targets a distinct resource and action. There is no overlap: create, delete, get, list, set, run, test, etc., each apply to specific entities (configs, flags, forwarders, jobs, events, loggers, environments), making it impossible to confuse one tool for another.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern using lowercase and underscores. Singular nouns for get operations (e.g., get_config) and plural for list operations (e.g., list_configs) are used uniformly. This creates a predictable and readable naming scheme.

Tool Count4/5

With 29 tools, the count is slightly on the high side but justified by the variety of managed resources (configs, flags, forwarders, jobs, events, loggers, environments) and the need for distinct CRUD-like operations. It remains within a reasonable range for a comprehensive MCP server.

Completeness3/5

The tool set covers most lifecycle operations for each resource, but notable gaps exist: forwarders lack get and update tools, and configs have no metadata update tool. These gaps could cause agents to resort to workarounds like delete-and-recreate. Overall, coverage is decent but incomplete.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 5 tool updates
    • Changedcreate_job1 field changed
      • changedInput schema / properties / retry_policy / description
        Previous value: -"The id of a named retry policy to apply to failed runs."New value: +"The id of an existing named retry policy to apply to failed\nruns. Retry policies are managed in the smplkit console — create one\nthere, then pass its id."
    • Changedset_config_value1 field changed
      • changedInput schema / properties / environment / description
        Previous value: -"Environment to set the value in (default 'production')."New value: +"Environment to set the value in (default 'production'). Use\nlist_environments to see valid targets."
    • Changedset_flag1 field changed
      • changedInput schema / properties / rules / description
        Previous value: -"Replace this environment's targeting rules. Each rule is\n{\"when\": [{\"attribute\",\"operator\",\"value\"}, ...], \"serve\": <value>,\n\"description\"?: str}; conditions are AND-ed. Operators: ==, !=, >, <,\n>=, <=, in, contains. Pass [] to clear all rules."New value: +"**This replaces the environment's entire rule set.** To add a rule\nwithout dropping the others, call get_flag first and pass the full\nlist including the existing ones. Each rule is\n{\"when\": [{\"attribute\",\"operator\",\"value\"}, ...], \"serve\": <value>,\n\"description\"?: str}; conditions are AND-ed. Operators: ==, !=, >, <,\n>=, <=, in, contains. Pass [] to clear all rules."
    • Changedset_log_level1 field changed
      • changedInput schema / properties / environment / description
        Previous value: -"Environment to set the level in (default 'production')."New value: +"Environment to set the level in (default 'production'). Use\nlist_environments to see valid targets."
    • Changedupdate_job1 field changed
      • changedInput schema / properties / retry_policy / description
        Previous value: -"New named retry-policy id."New value: +"New named retry-policy id; manage policies in the console."
  2. 21 tool updates
    • Addedcreate_config
    • Addedcreate_flag
    • Addedcreate_forwarder
    • Addeddelete_config
    • Addeddelete_flag
    • Addeddelete_forwarder
    • Addedget_config
    • Addedget_event
    • Addedget_flag
    • Addedget_logger
    • Addedlist_configs
    • Addedlist_environments
    • Addedlist_flags
    • Addedlist_forwarders
    • Addedlist_loggers
    • Addedquery_events
    • Addedreset_logger
    • Addedset_config_value
    • Addedset_flag
    • Addedset_log_level
    • Addedtest_forwarder
  3. 8 tool updates
    • First observedcreate_job
    • First observeddelete_job
    • First observedget_job
    • First observedget_run
    • First observedlist_jobs
    • First observedlist_runs
    • First observedrun_job
    • First observedupdate_job

Related MCP Connectors

Related MCP Servers

  • MCP Engineering Agent

    Lekha-2023
    F
    license
    Not graded
    quality
    B
    maintenance
    Enables a security-first engineering agent with an MCP-style JSON-RPC tool boundary, role-based authorization, and UTC audit events for every decision.
    -

  • Hermes Toolkit MCP

    hermegeddon
    A
    license
    B
    quality
    C
    maintenance
    A safety-first MCP operations cockpit for Hermes Agent installations, exposing typed, evidence-producing management primitives.
    73
    MIT

  • managed-agent-control-mcp

    modus-agendi
    A
    license
    A
    quality
    D
    maintenance
    Start, observe, and interact with Claude Managed Agents from any MCP client — launch an agent, watch its events, reply, approve the tools it wants to run, and stop it. Runs over stdio, HTTP, or AWS Lambda with pluggable auth.
    17
    1
    MIT
Try in Browser
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

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources