notmcp - Simple tools for AI agents

How it works

As simple as asking

Ask your agent to connect to any service. It handles the rest.

Ask your agent

"Connect to PostHog" or "Search my Gmail" - just describe what you need.

Agent builds a tool

Your agent creates a connection to the service, handling authentication for you.

Use it anytime

The tool is saved locally. Your agent can use it whenever you need that service again.

Why notmcp

Let your agent do the work

You describe what you need. Your agent builds and maintains the tools.

No setup required

No servers, no Docker, no configuration files. Install once and start asking your agent to connect to services.

Grows with you

Your agent builds new tools as you need them. Ask for a Slack integration today, add Gmail tomorrow.

Fix bugs by asking

Something not working? Just tell your agent. It can read, edit, and improve any tool it created.

Fully open source

MIT licensed. Read the code, fork it, contribute. No vendor lock-in, no black boxes.

Your credentials stay on your machine

API keys are stored locally with owner-only permissions. Same security model as ~/.aws/credentials. Never written to any repository, never sent anywhere.

chmod 600 protected Local storage only Never in git

FAQ

Common questions

Which AI agents are supported?

Claude Code works out of the box. Cursor requires the nightly channel (Settings → Beta → Nightly). Both auto-discover skills from ~/.claude/skills/.

Can tools use pip packages?

We recommend stdlib-only for portability, but nothing stops you. The only contract is JSON in, JSON out. If you have packages installed, use them.

How do I create a new tool?

Just ask your agent: "Create a tool for [whatever you need]." Or run notmcp create my-tool and edit the scaffolded script.

What about MCP?

MCP is great for structured tool ecosystems. notmcp is for a different problem: most tools are simple, and the protocol overhead isn't worth it.