Hosted MCP endpoint: https://operatornest.com/mcp (Streamable HTTP, no API key).
Five deterministic cost, time-zone and scheduling calculations use bundled data and the same tool definitions over HTTP and stdio, returning normalized inputs, units, method, assumptions, dated sources and a link to open each result on OperatorNest. No network calls. The TypeScript source is included; calculations do not create events, install schedules or execute tasks.
| Tool | Result |
|---|
ai_api_cost | USD per request, day and month from token counts and selected model rates |
meeting_time_zones | Shared 30-minute slots within 09:00–17:00 for 2–8 people |
recurring_schedule | Monthly hours, recurrence rules and an RFC 5545 calendar |
ai_subscription_stack_cost | Monthly and annual totals with overlapping capabilities |
cron_next_runs | 1–10 matches after a UTC instant, within 366 days |
The justfile installs frozen dependencies, checks prerequisites and runs the build and tests:
just setup
just doctor
just check
Self-hosting
For checkout development, run just setup to install Node 26 and pnpm 12. The published package supports Node.js 22.19 or newer.
git clone https://github.com/OperatorNest/mcp-tools.git
cd mcp-tools
pnpm install --frozen-lockfile
pnpm test:local
pnpm build
node dist/stdio.js
For a client with stdio support, use node with the absolute path to dist/stdio.js as its argument to serve newline-delimited MCP messages on stdin/stdout, keeping protocol traffic separate from the logs written to stderr.
The package is prepared as @operatornest/mcp-tools version 1.1.0. To run a local package through npx before registry publication:
pnpm pack --out /tmp/operatornest-mcp-tools-1.1.0.tgz
npx --yes --package /tmp/operatornest-mcp-tools-1.1.0.tgz operatornest-mcp-tools
After npm publication, the equivalent command is npx --yes @operatornest/mcp-tools@1.1.0. Publication is a separate maintainer action.
HTTP Worker
src/worker.ts exports a standalone Worker with an /mcp endpoint. Use your own Worker configuration; wrangler.jsonc is a local starting point. Run it locally with:
pnpm dev:worker --port 8787
Connect a client to http://localhost:8787/mcp. For remote hosting, follow the Worker setup documentation in your own account.
The HTTP handler uses stateless JSON responses without sessions or subscription streams, caps request bodies at 32 KiB, rejects JSON-RPC batches and returns generic errors, with CORS for HTTPS origins and local-origin access to local endpoints.
Rate limiting is optional. To enable it, configure an MCP_LIMITER rate-limit binding. When present, it uses a SHA-256 hash of CF-Connecting-IP; rejection returns HTTP 429 with Retry-After: 60. Missing client IP or a binding error returns HTTP 503. No binding means no rate limiting.
Client setup
These snippets connect to the hosted endpoint. Substitute your own HTTPS /mcp URL to use your HTTP instance. Setup documentation checked on 2 October 2026; account and workspace controls may affect tool access.
ChatGPT
Enable Developer mode in Settings → Security and login. In Plugins, use the plus button to create a developer-mode app with this URL and No Authentication:
https://operatornest.com/mcp
Select the app from Developer mode in the conversation's plus menu. Official instructions.
Claude
In Claude, open Customize → Connectors, select Add custom connector, and enter https://operatornest.com/mcp. Choose No sign in and add the connector. Enable it for your conversation from the plus menu's Connectors list. Organization owners may need to add it first. Official connector instructions.
For Claude Code:
claude mcp add --transport http operatornest https://operatornest.com/mcp
Check the connection with /mcp. Official instructions.
Codex
codex mcp add operatornest --url https://operatornest.com/mcp
Alternatively, in ~/.codex/config.toml:
[mcp_servers.operatornest]
url = "https://operatornest.com/mcp"
Official instructions.
Cursor
Add to .cursor/mcp.json in your project, or ~/.cursor/mcp.json for all projects:
{
"mcpServers": {
"operatornest": { "url": "https://operatornest.com/mcp" }
}
}
Official instructions.
Gemini CLI
Add to ~/.gemini/settings.json:
{
"mcpServers": {
"operatornest": { "httpUrl": "https://operatornest.com/mcp" }
}
}
Official instructions.
VS Code
Add .vscode/mcp.json to your project:
{
"servers": {
"operatornest": { "type": "http", "url": "https://operatornest.com/mcp" }
}
}
Start the server from the configuration file and enable its tools in Agent mode. Official instructions.
Data and limits
API rates are frozen at 2026-09-28T17:08:16.340Z in src/data/pricing-snapshot.json, containing 194 models from models.dev. This is the hosted MCP's filtered snapshot. Use the bundled modelId values; the broader website catalog can include records this server does not accept. Null rates stay unlisted. Caching falls back to the input rate when absent; batch discounts require published data. Non-token charges are excluded.
Subscription plans are in src/data/ai-plans.ts, checked on 27 September 2026 with official source links. Annual totals use published annual charges, or twelve monthly charges when no annual charge is listed. Taxes, regional differences and promotions are excluded.
Meeting and cron results use the runtime's IANA time-zone database. Recurring calendars use floating local times in the importing calendar. Cron supports numeric stars, lists, ranges, steps and weekday names across GitHub, Cloudflare, Quartz and AWS dialects; L, W, # and named months are rejected. Results describe estimates and schedule previews.
Development
pnpm check
pnpm test:local
pnpm build
pnpm dlx @modelcontextprotocol/inspector --cli node dist/stdio.js \
--method tools/call --tool-name cron_next_runs \
--tool-arg 'expression=0 9 * * 1-5' --tool-arg dialect=github \
--tool-arg zone=UTC --tool-arg after=2026-10-02T00:00:00Z --tool-arg count=1
Tests validate input and output schemas, valid and invalid calls, HTTP limits, and initialize/list/call on both transports. See Inspector CLI documentation, contribution guidance, security reporting and data attribution.
MIT. Copyright (c) 2026 OperatorNest.