██████╗ ███╗   ██╗███╗   ███╗ ██████╗██████╗
██╔═████╗████╗  ██║████╗ ████║██╔════╝██╔══██╗
██║██╔██║██╔██╗ ██║██╔████╔██║██║     ██████╔╝
████╔╝██║██║╚██╗██║██║╚██╔╝██║██║     ██╔═══╝
╚██████╔╝██║ ╚████║██║ ╚═╝ ██║╚██████╗██║
 ╚═════╝ ╚═╝  ╚═══╝╚═╝     ╚═╝ ╚═════╝╚═╝

v1.2.0 — 245 CRM tools across 12 modules, full API coverage, rate limiting, webhooks, TypeScript definitions, and a growing open source community. See what's new.

The Problem

You have Stripe for payments. SendGrid for email. Slack for messaging. Airtable for data. A CRM for contacts.

Today, to automate across them, you need:

• Zapier ($50+/month) — and build complex zaps
• n8n/Make — and learn their visual builders
• Custom code — and maintain API integrations forever

What if you could just... talk to them?

The Solution

You: "Invoice john@acme.com for $500 and notify #sales on Slack when it's sent"

0nMCP figures out the rest:

Step 1: Found John Smith (john@acme.com) in Stripe
Step 2: Created invoice INV-0042 for $500.00
Step 3: Posted to #sales: "New invoice sent to John Smith for $500"

Done. 3 steps. 2 services. 1.2 seconds.

No workflows. No mapping. No code. Just results.

Watch It Work

# In Claude Desktop after setup:

You: "Connect to Stripe with key sk_live_xxx"
AI:  Connected to Stripe (8 capabilities available)

You: "Connect to Slack with bot token xoxb-xxx"
AI:  Connected to Slack (4 capabilities available)

You: "Get my Stripe balance and post it to #finance"
AI:  Your Stripe balance is $12,450.00. Posted to #finance.

That's it. No configuration files. No workflow builders. No decisions about which API to use.

Installation

One Command

npx 0nmcp

Or install globally:

npm install -g 0nmcp

Configure Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json (Mac) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

{
  "mcpServers": {
    "0nmcp": {
      "command": "npx",
      "args": ["0nmcp"],
      "env": {
        "ANTHROPIC_API_KEY": "sk-ant-..."
      }
    }
  }
}

ANTHROPIC_API_KEY is optional. It enables AI-powered multi-step task planning. Without it, 0nMCP still works using keyword-based routing.

Restart Claude Desktop. Start talking.

Supported Services

17 services. 252 tools. One interface.

More coming: Mailchimp, QuickBooks, Jira, Asana, Zendesk, Intercom, Webflow, WordPress...

Examples

Simple Tasks

"Send an email to sarah@example.com: Meeting moved to 3pm"

"Create a Stripe customer for mike@startup.io"

"Post to #engineering on Slack: Deploy complete!"

"Send SMS to +1555123456: Your order shipped"

"What's my Stripe balance?"

"Search Notion for project roadmap"

Multi-Step

"Create a Stripe invoice for $1000, then email the link to john@client.com"

"Create a GitHub issue for the login bug, then post it to #bugs on Slack"

"Look up sarah@example.com in my CRM and send her a follow-up email"

Complex Orchestration

"Check if we have any overdue invoices in Stripe. If so, send a summary
 to #finance on Slack and email the finance team."

The AI:

1. Queries Stripe for overdue invoices
2. Formats a summary
3. Posts to Slack
4. Sends the email
5. Reports back

You describe the outcome. AI figures out the path.

CRM Snapshots — Deploy Entire Configurations

"Deploy a full CRM snapshot with a 12-stage sales pipeline,
 all lead tags, custom values, and 18 workflow definitions"

One tool call. Everything deployed:

{
  "pipeline": {
    "name": "Sales Pipeline",
    "stages": ["001. New Lead", "002. Attempt to Contact", "003. Engaged",
               "004. Appointment Set", "005. Appointment Showed", "006. Proposal Sent"]
  },
  "tags": ["New Lead", "FB Lead", "Hot Lead", "Booked Appointment", "No Show"],
  "custom_values": {
    "calendar_link": "https://calendly.com/yourlink",
    "support_email": "support@yourco.com",
    "welcome_sms": "Hey {{contact.first_name}}, welcome aboard!"
  }
}

All Tools

Universal Tools (7)

CRM Tools (245)

The deepest CRM integration available in any MCP server. 245 tools across 12 modules — every endpoint, every parameter, full CRUD.

252 total tools. Universal orchestration + the most comprehensive CRM integration in the MCP ecosystem.

Every CRM tool is data-driven — defined as configuration, not code. Adding new endpoints takes minutes, not hours. See CONTRIBUTING.md.

What's New in v1.2

• 245 CRM tools — up from 10. Full API coverage across 12 modules
• Data-driven tool factory — every tool is a config object, new endpoints in minutes
• Rate limiting — built-in per-service rate limits with automatic retry
• Webhook support — receive and process external events
• TypeScript definitions — full type coverage for all exports
• CLI improvements — interactive setup, legacy migration, colored output

How It Works

┌─────────────────┐     ┌──────────────────┐     ┌─────────────────┐
│   You (Claude)  │────▶│      0nMCP        │────▶│   Your APIs     │
│                 │     │                  │     │                 │
│ "Invoice John   │     │ 1. Parse intent  │     │ Stripe          │
│  for $500 and   │     │ 2. Plan steps    │     │ SendGrid        │
│  notify #sales" │     │ 3. Execute APIs  │     │ Slack           │
│                 │◀────│ 4. Chain data    │◀────│ CRM             │
│                 │     │ 5. Summarize     │     │ + 13 more...    │
└─────────────────┘     └──────────────────┘     └─────────────────┘

With ANTHROPIC_API_KEY (AI Mode)

Claude analyzes your task, inspects connected services and their capabilities, creates a multi-step execution plan, runs every API call in order, passes data between steps, and summarizes the results.

Without API Key (Keyword Mode)

The orchestrator uses keyword matching to route tasks to the right service. Less intelligent but still functional for straightforward single-service requests.

Why Not Just Use...

The .0n Standard

0nMCP implements the .0n Standard — a universal configuration format for AI orchestration.

~/.0n/
├── config.json               # Global settings
├── connections/              # Service credentials as .0n files
│   ├── stripe.0n
│   ├── slack.0n
│   └── sendgrid.0n
├── workflows/                # Saved automation definitions
│   └── invoice-notify.0n
├── snapshots/                # System state captures
│   └── crm-setup.0n
├── history/                  # Execution logs (JSONL by date)
│   └── 2026-02-06.jsonl
└── cache/

Every connection is stored as a .0n file with a standard header:

{
  "$0n": {
    "type": "connection",
    "version": "1.0.0",
    "name": "Production Stripe"
  },
  "service": "stripe",
  "auth": {
    "type": "api_key",
    "credentials": { "api_key": "sk_live_..." }
  }
}

Every task execution is logged to ~/.0n/history/ as JSONL — full audit trail of what ran, when, and how.

Read the full spec

Architecture

0nMCP/
├── index.js          # Entry point — 7 universal tools + server startup
├── catalog.js        # Service catalog — 17 integrations with endpoints
├── connections.js    # Connection manager — ~/.0n/connections/*.0n
├── orchestrator.js   # AI execution planner — the brain
├── webhooks.js       # Webhook receiver and event processing
├── ratelimit.js      # Per-service rate limiting with retry
├── cli.js            # CLI — init, connect, migrate, interactive setup
├── crm/              # 245 CRM tools across 12 modules
│   ├── index.js      # Tool orchestrator — registers all modules
│   ├── helpers.js    # Data-driven tool factory — registerTools()
│   ├── auth.js       # OAuth, tokens, snapshots, workflows
│   ├── contacts.js   # 23 contact management tools
│   ├── conversations.js  # 13 messaging tools
│   ├── calendars.js  # 27 calendar & scheduling tools
│   ├── opportunities.js  # 14 pipeline & deal tools
│   ├── invoices.js   # 20 invoicing tools
│   ├── payments.js   # 16 payment processing tools
│   ├── products.js   # 10 product catalog tools
│   ├── locations.js  # 24 location management tools
│   ├── social.js     # 35 social media & blog tools
│   ├── users.js      # 24 user & form tools
│   └── objects.js    # 34 custom object & association tools
├── types/
│   └── index.d.ts    # Full TypeScript definitions
├── package.json
├── LICENSE           # MIT
└── CONTRIBUTING.md

Security

• Local execution — MCP server runs on your machine, not in the cloud
• Direct API calls — Requests go straight to each service, not through a proxy
• Your credentials — Stored locally in ~/.0n/connections/ as .0n files, never sent anywhere
• Anthropic key — Only used for task planning (never passed to external services)
• Rate limiting — Built-in per-service rate limits prevent accidental API abuse
• Execution history — Full audit trail in ~/.0n/history/
• Open source — Audit every line yourself

See SECURITY.md for our security policy and how to report vulnerabilities.

Configuration

Environment Variables

Credential Storage

Connections stored as .0n files in ~/.0n/connections/. For production:

• Use a secrets manager
• Enable encryption via ~/.0n/config.json
• Use environment variables: "api_key": "{{env.STRIPE_KEY}}"

For Developers

Adding a New Service

Drop a definition into catalog.js:

your_service: {
  name: "Your Service",
  type: "category",
  description: "What it does",
  baseUrl: "https://api.yourservice.com",
  authType: "api_key",
  credentialKeys: ["apiKey"],
  capabilities: [
    { name: "do_thing", actions: ["create", "list"], description: "Does the thing" },
  ],
  endpoints: {
    do_thing:    { method: "POST", path: "/things", body: { name: "" } },
    list_things: { method: "GET",  path: "/things" },
  },
  authHeader: (creds) => ({
    "Authorization": `Bearer ${creds.apiKey}`,
    "Content-Type": "application/json",
  }),
},

Adding CRM Endpoints

Even easier — just add a config object to the relevant module:

{
  name: "crm_do_thing",
  description: "Does the thing in the CRM",
  method: "POST",
  path: "/things/:thingId",
  params: {
    thingId: { type: "string", description: "Thing ID", required: true, in: "path" },
    name:    { type: "string", description: "Thing name", required: true, in: "body" },
  },
  body: ["name"],
}

The tool factory handles registration, validation, API calls, error handling — everything. See CONTRIBUTING.md for the full guide.

Roadmap

Shipped:

• Core orchestration engine with AI planning
• 17 service integrations
• Multi-step execution with data chaining
• 245 CRM tools — full API coverage across 12 modules
• Data-driven tool factory — config, not code
• Full snapshot deployment (pipeline + tags + values + workflows)
• Keyword fallback mode (works without Anthropic key)
• .0n Standard — universal config format (~/.0n/)
• Execution history — JSONL logs in ~/.0n/history/
• Rate limiting — per-service with automatic retry
• Webhook support — receive external events
• TypeScript definitions — full type coverage
• CLI — interactive setup, migration, colored output
• npm published — npx 0nmcp live on npm

In Progress:

• OAuth flows — connect with one click (Q1 2026)
• Credential encryption — AES-256-GCM at-rest (Q1 2026)
• Scheduled tasks — "every Monday, send a report"
• More services — 50+ planned (Mailchimp, QuickBooks, Jira, Asana...)
• Plugin system — bring your own services
• Web dashboard — manage connections visually
• Conditionals — "if balance < $100, alert me"
• Test suite — comprehensive unit + integration tests

Community

0nMCP is built in the open by a growing network of developers who believe AI orchestration should be free, composable, and community-owned.

The 0n community is 1,000+ developers strong — building integrations, shipping tools, and pushing the boundaries of what MCP can do.

This is not a side project. This is infrastructure.

We ship weekly. The codebase is active. The community is real. If you're building with MCP, you're already one of us.

Get Involved

• Star this repo — it helps more than you think
• Open an issue — bugs, ideas, questions
• Join the discussion — GitHub Discussions
• Submit a PR — Contributing Guide
• Learn the .0n Standard — 0n-spec
• Spread the word — tell a developer friend

Community Stats

License & Philosophy

MIT Licensed — free to use, modify, and distribute. See LICENSE.

Our position: 0nMCP is and always will be free and open source. We built this because we believe AI orchestration is infrastructure — it should be accessible to every developer, not locked behind enterprise paywalls or monthly subscriptions.

If you find someone selling this tool, know that it's free right here. Always has been, always will be. The entire codebase is open, auditable, and community-maintained.

We chose MIT for maximum freedom. Use it in your projects, your products, your startups. But if you build something great with it, give back to the community that made it possible. That's the deal.

Trademarks: The names "0nMCP", "0nORK", and ".0n Standard" are trademarks of RocketOpp. The MIT license grants rights to the software, not to the trademarks. You may not use these names to promote derivative products without permission.

Contributing

We want 0nMCP to be the open standard for AI-powered API orchestration.

Ways to contribute:

• Add a service — Drop it in the catalog. See CONTRIBUTING.md
• Add CRM tools — Config-driven, takes minutes
• Report bugs — Open an issue
• Suggest features — Start a discussion
• Improve docs — PRs welcome
• Star the repo — Help others find it

git clone https://github.com/0nork/0nMCP.git
cd 0nMCP
npm install
node index.js

The 0n Network

0nMCP is part of the 0n Network — an open ecosystem of AI-native tools built by 0nORK.

Built With

• Anthropic — Claude and the MCP standard
• Model Context Protocol — The protocol that makes this possible

Support the Network

0nMCP is free and always will be. If it saves you time or money: