Developers
Simple Tools offers WebMCP for live Client-side Tools. Eligible Backend Tools can run through browser WebMCP when enabled, with Account access, Credits and visible approval. Remote machine access is separate.
WebMCP
Homepage registers discover_tools (index). A category page registers eligible live tools in that category. A tool page registers that tool only. No API key. Free Client-side Tools run on your device without uploading files. Client-side file tools take { mime, base64 } (max 12 MiB decoded), not OS File objects. Backend Tools run on our server when enabled, with Account access, Credits and visible approval for browser-agent operations. See the retention policy. Index: /llms.txt. Manifest: /.well-known/webmcp.json. Catalog: /api/v1/tools.
/.well-known/webmcp.json
Authentication
Send header X-STS-API-Key. API keys are coming soon. OAuth is not shipped.
REST
OpenAPI at /openapi.json. Upload then invoke under /api/v1/tools/{toolId}.
MCP
POST /mcp. Same Credits as REST. Remote access is currently off — coming soon.
POST /mcp
Credits
tools:invoke spends Credits. Same entitlement as the web Hub.
Privacy
Free Client-side Tools run on your device without uploading files. Backend Tools use server processing and Credits, including browser WebMCP operations when enabled. See the retention policy. Remote REST/MCP is a separate access channel.