THE NPM FOR AI TOOLS

225PACKAGES
/
667TOOLS
/
194.8KDOWNLOADS

Auto-discovers AI tools from npm. Extracts schemas, scores quality, serves them via MCP. One URL gives Claude Code, Cursor, or Windsurf instant access.

Try: “web scraper”, “discord”, “code interpreter”

get started

one command. all your editors.

Pick tool collections, choose your editors, run the install script. MCP servers configured across Claude Code, Cursor, Windsurf, and Claude Desktop in one shot.

1

pick your collections

Browse tool collections — yours, or any public one.

2

choose your editors

Map collections to Claude Code, Cursor, Windsurf, or Claude Desktop.

3

run one command

Paste in your terminal. MCP servers configured across all selected editors.

install script
$
curl -fsSL https://tpmjs.com/install.sh | bash
tip

go to tpmjs.com/setup first to select collections and get a personalized command with your token baked in.

>_Claude Code
CClaude Desktop
{;}Cursor
WWindsurf
LIVE STATS
0
Published Tools
Auto-synced from npm
0
Active Developers
Last 7 days
0
Total Executions
All-time tool calls
0.0s
Avg Response
Execution latency

Recent Activity

+pdf-generator published30s ago
sql-query invoked26s ago
+image-processor published23s ago
data-validator updated6s ago
web-scraper invoked17s ago

why tpmjs

built for real usage

works with

Claude Code
Claude Desktop
Cursor
Windsurf
any MCP client

fully open source

MIT licensed. The registry, executor, CLI, SDK, and this website are all on GitHub. Inspect the code, contribute, or self-host.

every tool is validated

Auto-synced from npm. Schemas extracted. Health checks run continuously. Quality scored on docs, downloads, maintenance, and reliability. Broken tools get flagged.

the protocol debate

mcp vs cli vs rest is the wrong argument

People on Twitter say MCP is dead. Others say MCP is the future. Some say just use REST. They're all right — in their context.

CLI is better in Claude Code — fewer tokens, native bash reasoning, no protocol overhead. MCP is better in Cursor and Claude Desktop — structured tools without a shell. REST is better in your backend. SDK is better in your TypeScript app.

The mistake is universalizing from one context. The real questions are discovery, trust, and quality — not which wire protocol carries the JSON.

write the tool once. we serve it everywhere.

A tool author publishes a Zod-schema'd function to npm. TPMJS automatically makes it available via CLI, MCP, REST, and SDK. The consumer picks the right protocol for their context.

CLIClaude Code, terminal agents

Fewest tokens. Claude Code is great at bash. stdout is native. No handshake, no protocol overhead.

$ tpm collection add my-tools --search "firecrawl"

ℹ Found 3 tool(s):
  • scrapeTool (@anthropic/firecrawl-tools)
  • searchTool (@anthropic/firecrawl-tools)
  • crawlTool (@anthropic/firecrawl-tools)

✓ Added 3 tool(s) to my-tools
try it in claude code

Install the CLI, then paste any of these prompts into Claude Code. It has everything Claude needs to run the commands.

$npm install -g @tpmjs/cli

discover & add

Use the tpm CLI to search for firecrawl tools on the TPMJS registry and add them to my web-scraping collection. Run `tpm tool search firecrawl --json` first to see what's available, then `tpm collection add web-scraping --search "firecrawl"` to add them.

list & explore

Run `tpm collection list --json` to show all my TPMJS collections, then pick the one with the most tools and run `tpm collection info <slug>` to show me what tools are in it.

build a collection from scratch

Use the tpm CLI to create a new TPMJS collection called "data-tools" with `tpm collection create`, then search for data extraction and CSV tools with `tpm tool search` and add the top 5 results to it with `tpm collection add`.

search & execute

Use `tpm tool search "weather"` to find weather tools on TPMJS, pick the best one, then run it with `tpm tool execute <package>/<tool> --input '{"city":"London"}'` to get the current weather.

discovery

Quality-scored tools, BM25 search, curated collections. Find what works.

trust

Health checks, schema validation, download metrics. Know it works.

portability

Same tool over CLI, MCP, REST, SDK. Bet on tools, not transport.

model context protocol

works with every mcp client

MCP is the open protocol that lets AI clients call external tools. Create a collection, get a URL, paste it into your editor. That's it.

how it works
1

create a collection

Pick tools from the registry and group them into a collection. Public or private.

2

copy your mcp url

Every collection gets a unique MCP endpoint URL.

3

add to your ai client

Paste the URL into your client's MCP config. Tools work immediately.

setup by client

one command — that's it

claude mcp add my-tools \
  https://tpmjs.com/@username/collections/my-tools/mcp \
  -t http
tip

run /mcp in Claude Code to verify the server is connected. run claude mcp list to see all configured servers.

url format
https://tpmjs.com/@username/collections/slug/mcp

one url gives your ai access to 667+ tools

private collections

Private collections require a TPMJS API key. Add an Authorization: Bearer YOUR_KEY header to your config. Generate keys in Settings.

for tool authors

Publish Your Tool

Add one keyword to your package.json, publish to npm, and your tool is live on the registry within minutes. Automatic schema extraction, quality scoring, and MCP endpoints.

Create a Tool Package in Seconds

Our CLI generator scaffolds a production-ready TPMJS tool package with 2-3 tools, complete setup, and best practices baked in.

$npx @tpmjs/create-basic-tools
1

Quick Setup

Add one keyword to package.json and publish to npm

2

Auto Discovery

Your tool appears on tpmjs.com within 15 minutes

3

Quality Metrics

Automatic scoring based on docs, downloads, and stars