Skip to content
Trusty Sweep Developers

MCP server

Endpoint: https://mcp.trustysweep.com/mcp (Streamable HTTP). The server is dual-era: modern clients (2026-07-28, stateless per-request _meta, MCP-Protocol-Version/Mcp-Method/Mcp-Name headers, server/discover, resultType) and legacy clients (2025-11-25 and earlier, initialize handshake, session id) are both served on the same endpoint.

Authorization

Section titled “Authorization”

OAuth 2.1 with PKCE. Unauthenticated requests get 401 with WWW-Authenticate: Bearer resource_metadata="https://mcp.trustysweep.com/.well-known/oauth-protected-resource/mcp". The AS is https://api.trustysweep.com; dynamic registration and Client ID Metadata Documents are supported; tokens are audience-bound to the MCP resource. Provider tokens never pass through.

Tools

Section titled “Tools”
Tool Annotations
sweep_list_sources, sweep_get_pressure, sweep_find_reclaimable, sweep_search_vault, sweep_explain_plan, sweep_price_plan, sweep_get_execution, sweep_get_receipt, sweep_analyze_trials, sweep_analyze_meters, search, fetch readOnlyHint: true
sweep_create_plan state-changing, destructiveHint: false, idempotentHint: true (never touches provider state)
sweep_request_approval opens a URL-mode elicitation for the delegating user
sweep_commit_plan destructiveHint: true when the plan contains trash/move; requires a plan; may return resultType: "input_required" (step-up)
sweep_restore state-changing, non-destructive
sweep_reconcile_creator_revenue long-running (returns a job)

Tools are exposed according to the token’s scopes and the user’s delegation, in deterministic order. Destructive tools cannot bypass plan → authorize → commit: sweep_commit_plan calls the same commit gate as the API. search and fetch exist for deep-research clients and are read-only.

Client setup

Section titled “Client setup”
  • Claude (Desktop, claude.ai custom connectors, Claude Code): add a remote MCP server with URL https://mcp.trustysweep.com/mcp; complete the OAuth consent in the browser.
  • Anthropic Messages API: mcp_servers: [{ type: "url", url: "https://mcp.trustysweep.com/mcp", name: "sweep", authorization_token: "<access token>" }] with the MCP client beta header.
  • ChatGPT / OpenAI: register as a connector with the same URL; search/fetch satisfy the deep-research tool requirements.
  • Cursor / other: {"mcpServers": {"sweep": {"url": "https://mcp.trustysweep.com/mcp"}}}.

Examples: examples/mcp-client (modern raw-fetch client and legacy SDK client).