How TPMJS Compares
TPMJS is an npm-native registry with automated tool discovery, schema extraction, and MCP serving. Here's how the architecture differs from the alternatives.
TPMJS vs Custom MCP Servers
TPMJS provides a three-phase sync pipeline, automated schema extraction, and a pluggable executor interface — so you ship agents instead of server infrastructure.
- Auto-discovered tools from npm exports
- JSON-RPC 2.0 with HTTP + SSE transports
- Quality scoring with BM25 search
TPMJS vs LangChain Tools
TPMJS tools are standalone npm packages with Zod-validated schemas. No framework runtime, no transitive dependency tree, no vendor-specific adapters.
- Vercel AI SDK 6 tool() format
- Works with any MCP client natively
- Independent versioning per tool
TPMJS vs Composio
TPMJS tools are npm packages that run in your process. No API intermediary, no usage billing, no data routing through third-party servers.
- Tools execute locally in your runtime
- Open MCP protocol, not proprietary API
- Self-hostable with custom executors
TPMJS vs Manual Function Calling
TPMJS auto-extracts inputSchema from tool exports at enrichment time, generates Zod validation, and exposes tools via a universal MCP interface — no per-provider schema writing.
- Schemas auto-extracted from exports
- Zod validation built into every tool
- One interface for all LLM providers
Architecture at a Glance
How each approach handles distribution, protocol, schema management, execution, and discovery.
| TPMJS | LangChain | Custom MCP | Composio | Manual | |
|---|---|---|---|---|---|
| Distribution | npm packages | Framework-bundled | Self-hosted servers | Hosted SaaS API | Inline code |
| Protocol | MCP (JSON-RPC 2.0) | LangChain adapters | MCP (custom impl) | Proprietary REST | Vendor-specific |
| Schema format | Zod + JSON Schema (auto) | LangChain tool class | JSON Schema (manual) | Composio SDK types | JSON Schema (manual) |
| Execution | Local or pluggable executor | LangChain runtime | Your server process | Composio cloud | Your process |
| Discovery | BM25 search + categories | Docs / source | None | Composio catalog | None |
| Quality signal | Scored (0-1.0) | None | None | None | None |
How TPMJS Works Under the Hood
Discovery Pipeline
A three-phase async pipeline monitors the npm changes feed, extracts JSON schemas from tool exports, and calculates quality scores using npm downloads and GitHub stars on a logarithmic scale.
MCP Protocol
Collections are served as JSON-RPC 2.0 endpoints with HTTP and SSE transports. Supports tools/list, tools/call, and initialize methods with API key authentication and per-key rate limiting.
Pluggable Executors
Tools execute via a default Railway-hosted executor or any custom HTTPS endpoint. The executor contract accepts a package name, tool name, params, and env vars — and returns output with execution time.
Ready to try TPMJS?
Browse the registry, install a tool, and integrate it into your agent in minutes.