The application infrastructure your agents reach for.

Feature flags, configuration, logging, audit, and scheduled jobs — the whole operational layer your apps need, exposed through one MCP server your coding agent connects to. With a first-class console and SDKs in six languages for the humans in charge.

Free tier on every product · Python · TypeScript · Go · Java · C# · Ruby

Agent-native

Your agent operates the whole platform.

Connect smplkit’s MCP server once, and your coding agent — Claude, Cursor, Copilot, and more — can provision and operate every primitive in plain language: create a feature flag, set a config value, schedule a job, query the audit log, dial logging up to debug. No dashboards to learn, no API to wire by hand. You stay the owner — every change runs under your account and shows up in your console.

You

“Schedule my cleanup endpoint to run nightly at 2am, and run it once to prove it works.”

Your agent

Creates the job, fires it on demand, and shows you the real 200 OK — without leaving your editor.

Listed in the official MCP Registry. Works with any MCP-capable agent.

Connect your agent →

Each product is first-class in the console and the six-language SDKs — and every one is agent-operable through the same MCP server.

Smpl Audit

Append-only audit logs. Who did what and when.

An append-only record of every event and every change. Each entry captures the actor, the timestamp, and any JSON detail you attach — enough to reconstruct prior state, attribute responsibility, or replay history.

  • 01 Read and write events via API POST events from any code path. Pull change history into your app to show users what happened and when.
  • 02 Full JSON snapshots in every entry Actor, timestamp, and any JSON detail you attach — including full snapshots when you need to reconstruct prior state.
  • 03 Stream to any HTTP destination Pre-configured for Datadog, Splunk HEC, Sumo Logic, and others. Generic HTTP for everything else.
View Smpl Audit →

Smpl Config

Configuration management with real inheritance.

Define a common configuration once. Service-specific configs inherit from it and override only what's different. Per-environment overrides on any value, with inheritance visible at every level.

  • 01 Inheritance you can see Every cell tells you whether the value is local or inherited.
  • 02 Per-environment overrides Override database.host in production. Staging keeps inheriting.
  • 03 Live updates, no redeploys SDKs receive changes via WebSocket and re-resolve in real time.
View Smpl Config →

Smpl Flags

Turn features on when you're ready.

Feature flags with per-environment rules. Roll out gradually, target by tier or region, kill a release the moment a bug shows up. Unlimited flags, unlimited users, unlimited servers.

  • 01 Four flag types Boolean, string, numeric, JSON. Closed value sets or freeform.
  • 02 Local evaluation SDKs evaluate flags locally with no network call per check.
  • 03 Unlimited everything Pricing scales with rule complexity — not users, servers, or connections.
View Smpl Flags →

Smpl Jobs

Scheduled HTTP jobs that run like clockwork.

Schedule an HTTP request once at a future time, or on a recurring cron schedule. Smpl Jobs runs it, retries on failure, enforces a per-run timeout, and captures every request, response, and outcome — so you always know what happened.

  • 01 Cron or one-off, your choice Schedule a request on a recurring cron expression or once at a future moment. Change or cancel it anytime from the console or the API.
  • 02 Retries and timeouts built in Failed runs retry on a policy you configure, and a per-run timeout keeps a slow endpoint from hanging your schedule.
  • 03 Every run captured Each run records its request, response, timing, and outcome — so you can debug a failure or re-run it on demand.
View Smpl Jobs →

Smpl Logging

Change log levels in real-time.

You're one line of code away from real-time control over every logger. Every service. Every environment. Temporarily turn on debug in production to diagnose an issue. Instantly silence noisy loggers.

  • 01 Auto-discovery Drop in the SDK and every logger gets reported up automatically.
  • 02 One-line install SmplClient().logging.install() — that's it.
  • 03 Live updates Change a level in the console, applied across every running process.
View Smpl Logging →