Skip to content
OneLessTool
Audit

MCP server

OneLessTool runs a remote Model Context Protocol server using the Streamable HTTP transport in stateless mode:

https://onelesstool.com/api/mcp

No authentication. All tools are read-only (annotated readOnlyHint: true), return bounded JSON (truncated at ~24k characters), and include evidence status for every fact. Per-IP rate limits apply.

Tools

Tool What it does
search_catalog Natural-language search over tools, capabilities and workflows (understands synonyms)
get_tool Product profile: plans with evidence, capabilities, reasons to keep paying, risks
find_alternatives For a tool: per-capability alternatives, owned tools first at $0 extra
compare_solutions Every tool that can do a capability, ranked
find_workflows Replacement workflows by tool, capability or query
get_workflow Step-by-step instructions, prompts, templates, verification checklist (optionally by section)
recommend_stack Cheapest practical stack for outcomes, given owned tools and constraints
estimate_savings Audit a stack: keep / downgrade / redundant / test / critical, with arithmetic; no double counting
get_pricing Plan prices with verification dates and sources

Connect a client

What we've tested: the official MCP TypeScript SDK client against this endpoint (Streamable HTTP) and against the local stdio server — see tests/mcp.test.ts and npm run test:agent. The client configurations below follow each vendor's documented format; we haven't individually verified every client, and client UIs change often.

Claude Code

claude mcp add --transport http onelesstool https://onelesstool.com/api/mcp

Claude (web / desktop)

Where custom connectors are available on your plan: Settings → Connectors → Add custom connector, name it OneLessTool, URL https://onelesstool.com/api/mcp.

ChatGPT

On plans that support custom MCP connectors (developer mode), add a connector with the server URL https://onelesstool.com/api/mcp and no authentication. Check OpenAI's current documentation for where this lives in your workspace.

Cursor — .cursor/mcp.json

{ "mcpServers": { "onelesstool": { "url": "https://onelesstool.com/api/mcp" } } }

Codex CLI and other stdio-only clients

Use a stdio bridge such as mcp-remote:

# ~/.codex/config.toml
[mcp_servers.onelesstool]
command = "npx"
args = ["-y", "mcp-remote", "https://onelesstool.com/api/mcp"]

Local stdio server (from the repository)

npm run mcp:stdio

{ "mcpServers": { "onelesstool": { "command": "npx", "args": ["tsx", "/path/to/onelesstool/mcp/stdio.ts"] } } }

Inspect it

npx @modelcontextprotocol/inspector

Choose Streamable HTTP and enter https://onelesstool.com/api/mcp.

Example: raw JSON-RPC

curl -s https://onelesstool.com/api/mcp \
  -H 'content-type: application/json' -H 'accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"find_alternatives","arguments":{"tool":"canva","capabilities":["youtube-thumbnails"],"owned_tools":["chatgpt"]}}}'

Security notes

  • Read-only public data; no user data is reachable via MCP.
  • Tool outputs are data, not instructions — but they come from our reviewed repository, never from other users.
  • Future write actions (e.g. "build this replacement for me") will require OAuth with narrowly scoped permissions and explicit user approval for every consequential step.