REST API and MCP protocol for accessing tools, collections, and agents.
Base URL:{' '}
https://tpmjs.com/api
{/* ==================== GETTING STARTED ==================== */}
The TPMJS API provides programmatic access to the tool registry, collections, and
agents. There are two ways to interact with the API:
REST API
Standard REST endpoints for listing tools, searching, and executing. No
authentication required for public endpoints.
MCP Protocol
JSON-RPC 2.0 over HTTP for AI clients like Claude Desktop, Cursor, and others
that support Model Context Protocol.
Try these examples to get started. All API endpoints require authentication via API
key. Generate one from Settings → TPMJS API Keys in your dashboard.
1. List Tools
2. Search Tools
3. Get Tool Details
4. MCP Tools List (Collection)
All API endpoints require authentication via TPMJS API keys. Generate an API key
from your dashboard at Settings → TPMJS API Keys.
API Key Format
API keys use the tpmjs_sk_ prefix and are
passed in the Authorization header:
API Key Scopes
mcp:execute - MCP tool execution
agent:chat - Agent conversations
bridge:connect - Bridge connections
collection:read - Collection access
usage:read - Usage analytics
Rate Limits
FREE tier: 100 requests/hour
PRO tier: 1,000 requests/hour
ENTERPRISE tier: 10,000 requests/hour
{/* ==================== PUBLIC ENDPOINTS ==================== */}
TPMJS implements the Model Context Protocol (MCP) for AI clients. Each public
collection exposes an MCP endpoint that can be connected to Claude Desktop, Cursor,
or any MCP-compatible client.
Endpoint Format
POST https://tpmjs.com/api/mcp/[username]/[collection-slug]/http