smplkit/mcp

A hosted, agent-native Model Context Protocol
server — the gateway that lets an AI agent (Claude Code, Claude Desktop, Cursor,
…) **operate the whole smplkit platform** on your behalf,
without you ever leaving the chat.
One server, the whole platform:
- **Flags** — feature flags with per-environment values and targeting.
- **Config** — keyed, typed config with per-environment overrides.
- **Logging** — change runtime log levels per environment.
- **Audit** — search the audit log and wire SIEM forwarders.
- **Jobs** — scheduled HTTP jobs (cron, one-off, or on-demand) with response capture.
Once connected, tell your agent *"turn on the new checkout for enterprise users in
prod,"* *"set the staging database host,"* *"raise the SQL logger to DEBUG in
prod,"* *"stream audit events to Datadog,"* or *"POST my endpoint every morning at
7."* It makes the change, proves it works, and answers follow-up questions
straight from the live state.
It is a thin, **stateless** HTTP client to the smplkit product APIs — it holds no
credential of its own.
Connect once
1. Add the server and sign in
The server lives at **https://mcp.smplkit.com/api/mcp**. Point your MCP client
at that URL — the first time it connects, the client opens your browser for a
**one-time sign-in** (**Continue with Google or Microsoft**, standard OAuth).
After that it reconnects and refreshes access on its own; there's no key to mint,
copy, or rotate.
**Claude Code** (CLI):
…or in .mcp.json:
**Cursor** (~/.cursor/mcp.json or project .cursor/mcp.json):
**Claude Desktop** (claude_desktop_config.json) — Desktop bridges remote
servers through mcp-remote, which opens a browser for the one-time sign-in and
caches the connection:
Prefer a static key?
For non-interactive use — CI, scripts, headless clients, or writing code with the
smplkit SDKs — skip the browser
and authenticate with an API key as a bearer token. Sign up at
**https://smplkit.com** (Google or Microsoft SSO, email-verified instantly),
create an **API key** in the console, and send it as
Authorization: Bearer YOUR_SMPLKIT_API_KEY (a custom X-Smplkit-Api-Key header
is also accepted). The SDKs read the same key from SMPLKIT_API_KEY. For example,
add a headers block to the config above:
2. Ask your agent
> "Create a boolean flag new-checkout, off by default, then turn it on in prod
> only for enterprise users."
> "List my environments, then set database.host to db-staging.internal for
> staging."
> "Raise the sqlalchemy.engine logger to DEBUG in production while I debug,
> then reset it."
> "Test whether https://http-intake.logs.datadoghq.com/... accepts a sample,
> then create a Datadog forwarder for our audit events."
> "POST https://api.example.com/cache/warm every morning at 7am NY time, then
> run it now to prove it works."
Tools
All tools share intent-named verbs — list_*, get_*, create_*, set_*,
delete_* — and hide the JSON:API envelopes, per-environment nesting, and
full-replace PUTs behind partial-intent calls.
| Capability | Tools |
|---|---|
| **Flags** | create_flag, list_flags, get_flag, set_flag, delete_flag |
| **Config** | create_config, list_configs, get_config, set_config_value, delete_config |
| **Logging** | set_log_level, list_loggers, get_logger, reset_logger |
| **Audit** | query_events, get_event, list_forwarders, create_forwarder, test_forwarder, delete_forwarder |