MCP Tools
Overview
Connect your AI coding agent to Clocknext.
Clocknext gives your AI coding agent everything it needs to set up and run usage-based billing from inside your project: the tools it calls to meter usage and manage your catalogue (an MCP server), the playbook it follows to wire billing into your codebase (an Agent Skill), and a one-step bundle of both (the Plugin).
Human-in-the-loop, sandbox-first
The onboarding skill drives these tools through a guided flow — detect your
models, create entitlements and a plan, meter your code, then prove it with a
dummy customer — and stops hard before anything that spends real money. Your
cnk_… key stays in the server's environment, never in the model's context.
Pick your client
Every card below sets up Clocknext for that agent. Claude Code is live today; the rest are on the way.
What you get
Plugin
One command installs the MCP server and the onboarding skill together, and wires your API key. Claude Code only.
MCP server
The tools your agent calls — whoami, list models, verify and record usage, read balances, and full catalogue CRUD. Every MCP client.
Agent skills
The step-by-step onboarding playbook that drives the tools. Every AI coding agent.
Which should I install?
The skill drives the tools, so for the full guided experience you want both. On Claude Code the plugin bundles them in one step; on any other agent, install the skill and the MCP server separately.
| Install | What you get | Works in |
|---|---|---|
Plugin — /plugin install clocknext@clocknext | MCP tools and the skill, one step | Claude Code only |
MCP server — npx -y @clocknext/mcp | the tools an agent calls | every MCP client |
Agent skill — npx skills add Clocknext/clocknext-mcp | the guided onboarding flow | every AI coding agent |
You'll need an API key
The tools authenticate with your organisation's cnk_… key from
Settings → API Keys. It's a server-side secret — keep it in env/secret
config, never in client code or a repo. See
Settings → API keys.