smplkit MCP Server
Server Details
Operate smplkit from your agent: feature flags, config, logging, audit, and scheduled jobs.
The last two health checks of this connector failed. 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
- Uptime
- 0.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- smplkit/mcp
- GitHub Stars
- 0
- Server Listing
- smplkit MCP Server
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 29 tools
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.
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.
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.
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.
Loading tool schema changelog…
Related MCP Connectors
Admin for your app from your AI agent: users, stats, segments, feature flags and email.
Agent control plane for multi-site content ops: research, drafts, review, CMS draft delivery.
Set up paywalls, subscriptions, A/B tests, feature flags and analytics for your app from your agent.
Work with roles, tasks and delegated agent work within current workspace permissions. Setup: In a remote MCP client that supports Streamable HTTP and OAuth, add https://platform.samuelz.com/api/v1/mcp/operator?toolset=agent. Sign in to Samuelz and select your authorized workspace. An active workspace membership and the relevant module permissions are required. Review the requested permissions before authorizing. Existing approval requirements continue to apply.
Related MCP Servers
- AlicenseAqualityDmaintenanceEnables MCP-capable agents to create and invoke OpenServerless endpoints, manage secrets, and configure integrations such as S3, PostgreSQL, Redis, Milvus, and MongoDB.13Apache 2.0
- FlicenseNot gradedqualityBmaintenanceEnables a security-first engineering agent with an MCP-style JSON-RPC tool boundary, role-based authorization, and UTC audit events for every decision.-
- AlicenseBqualityDmaintenanceA safety-first MCP operations cockpit for Hermes Agent installations, exposing typed, evidence-producing management primitives.73MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to run a SaaS app's admin through a scoped, audited API — looking up users, applying support actions, reading growth and retention, building segments, toggling feature flags and drafting emails in plain language. Access is limited by key scopes, so tools outside a key's permissions never appear.MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.