Clocknext runs on your own machine — the client starts it, so there is no endpoint to ping. 698 installs a week from npm. Last commit 5 Nov 2026.
Meter usage and manage usage-based billing from AI tools via the ClockNext API.
Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 20 October 2026. No other catalogue keeps this.
We read the source, 1 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
пакет @clocknext/mcp ссылается на clocknext/clocknext-mcp
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add mcp -e 'CLOCKNEXT_API_KEY=<CLOCKNEXT_API_KEY>' -- npx -y @clocknext/mcp
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@clocknext/mcp"
],
"env": {
"CLOCKNEXT_API_KEY": "<CLOCKNEXT_API_KEY>"
}
}
}
}
[mcp_servers.mcp]
command = "npx"
args = ["-y", "@clocknext/mcp"]
env = { CLOCKNEXT_API_KEY = "<CLOCKNEXT_API_KEY>" }
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@clocknext/mcp"
],
"env": {
"CLOCKNEXT_API_KEY": "<CLOCKNEXT_API_KEY>"
}
}
}
}
{
"servers": {
"mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@clocknext/mcp"
],
"env": {
"CLOCKNEXT_API_KEY": "<CLOCKNEXT_API_KEY>"
}
}
}
}
Put your own value in place of
<CLOCKNEXT_API_KEY> (Your organisation's cnk_… API key (Settings → API Keys)).
The author’s registry entry marks it as required.
Optional settings from the registry entry, left out of the block above:
CLOCKNEXT_BASE_URL (Override the API origin (e.g. a staging URL). Defaults to production), CLOCKNEXT_DOCS_URL (Override the docs origin for the search_docs/get_doc tools. Defaults to https://help.clocknext.com).
Meter usage and manage usage-based billing from AI tools via the ClockNext API.
Meter usage and manage usage-based billing from AI tools via the Clocknext API.
MCP server for the PostFast API — schedule and manage social media posts via AI tools
Order anything from your terminal — search, buy, track, and manage via MCP tools.
Notion pages, databases and blocks via the REST API, as MCP tools.
Manage Nextcloud tasks, calendar events and notes from Claude over CalDAV and the Notes API.
Deploy and manage Bult apps from AI coding agents.
Messaging tools for AI agents: send messages, manage chats, groups and channels.
Answers built from our own checks of this server.