OperatorNest tools

com.operatornestv1.0.0Updated Oct 2, 2026

Calculate API and subscription costs, meeting time zones, recurring schedules and cron matches.

VerifiedStreamable HTTPWeb executableDeveloper ToolsFinanceProductivity & Workflow

Overview

AI-generated overview

Lets an assistant run five deterministic calculators for AI API and subscription costs, meeting time zones, recurring schedules, and cron matches.

What it does
OperatorNest exposes five calculation tools: ai_api_cost estimates USD per request, day and month from token counts and model rates; ai_subscription_stack_cost totals monthly and annual plan costs with overlapping capabilities; meeting_time_zones finds shared 30-minute slots for 2-8 people; recurring_schedule returns monthly hours, recurrence rules and an RFC 5545 calendar; cron_next_runs lists 1-10 matches after a UTC instant. Each result includes normalized inputs, units, method, assumptions, dated sources and a link to open the result on the OperatorNest site. Calculations use bundled data and make no network calls.
When to use it
Useful when you need quick, reproducible estimates rather than live data: comparing model or subscription costs, finding meeting windows across time zones, previewing recurring schedules, or checking when a cron expression next fires. It is a calculator, not an automation service.
Requirements
The hosted endpoint at operatornest.com/mcp needs no API key or account. Self-hosting needs Node.js 22.19 or newer and pnpm 12.6.0; the package is prepared as @operatornest/mcp-tools 1.0.0, and npm publication is a separate maintainer action. Optional rate limiting uses an MCP_LIMITER binding.
Before you install
Results are estimates and schedule previews: API rates are frozen at a 2026-09-28 snapshot, subscription data was checked on 27 September 2026, and taxes, regional differences, promotions and non-token charges are excluded. The tools do not create events, install schedules or execute tasks. Self-hosted HTTP deployments may hash the CF-Connecting-IP header for optional rate limiting.

Installation

In SourceWeft

  1. Open OperatorNest tools in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "tools": {
      "type": "http",
      "url": "https://operatornest.com/mcp"
    }
  }
}

README

OperatorNest tools

Hosted MCP endpoint: https://operatornest.com/mcp (Streamable HTTP, no API key).

Five deterministic calculations, with runnable TypeScript source and the same tool definitions over HTTP and stdio. Each result includes normalized inputs, units, method, assumptions, dated sources and a link to open the result on OperatorNest. Calculations use bundled data and make no network calls. They do not create events, install schedules or execute tasks.

ToolResult
ai_api_costUSD per request, day and month from token counts and selected model rates
meeting_time_zonesShared 30-minute slots within 09:00–17:00 for 2–8 people
recurring_scheduleMonthly hours, recurrence rules and an RFC 5545 calendar
ai_subscription_stack_costMonthly and annual totals with overlapping capabilities
cron_next_runs1–10 matches after a UTC instant, within 366 days

Self-hosting

Requires Node.js 22.19 or newer and pnpm 12.6.0.

sh
git clone https://github.com/OperatorNest/mcp-tools.gitcd mcp-toolspnpm install --frozen-lockfilepnpm test:localpnpm buildnode dist/stdio.js

The last command serves newline-delimited MCP messages on stdin/stdout. Logs go to stderr. For a client with stdio support, use node with the absolute path to dist/stdio.js as its argument.

The package is prepared as @operatornest/mcp-tools version 1.0.0. To run a local package through npx before registry publication:

sh
pnpm pack --out /tmp/operatornest-mcp-tools-1.0.0.tgznpx --yes --package /tmp/operatornest-mcp-tools-1.0.0.tgz operatornest-mcp-tools

After npm publication, the equivalent command is npx --yes @operatornest/[email protected]. 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:

sh
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 caps request bodies at 32 KiB, rejects JSON-RPC batches, returns generic errors and supports CORS for HTTPS origins. Local endpoints accept local origins. It uses stateless JSON responses, without sessions or subscription streams.

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:

text
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:

sh
claude mcp add --transport http operatornest https://operatornest.com/mcp

Check the connection with /mcp. Official instructions.

Codex

sh
codex mcp add operatornest --url https://operatornest.com/mcp

Alternatively, in ~/.codex/config.toml:

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:

json
{  "mcpServers": {    "operatornest": { "url": "https://operatornest.com/mcp" }  }}

Official instructions.

Gemini CLI

Add to ~/.gemini/settings.json:

json
{  "mcpServers": {    "operatornest": { "httpUrl": "https://operatornest.com/mcp" }  }}

Official instructions.

VS Code

Add .vscode/mcp.json to your project:

json
{  "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

sh
pnpm checkpnpm test:localpnpm buildpnpm 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.

Source: README.md at commit 8036144

Tools

0
Tool metadata has not been indexed yet.

Version history

1
  1. v1.0.0LatestOct 2, 2026