/** * `synap mcp` — the MCP front door. * * The Synap pod exposes an MCP server at `${podUrl}/mcp` (Bearer-authed). This * command group is the turnkey funnel for pointing ANY MCP client at it: * * synap mcp url — print a ready-to-paste connection (URL + key + snippets) * for UI-only clients that accept a custom header (e.g. * Raycast) and for clients that need the raw values to * wire up by hand. claude.ai's connector UI does NOT * currently accept a bearer token here — see the note * printed by this command. * synap mcp verify — health-check: is /mcp reachable and is the key valid? * synap mcp connect — alias of `synap connect` for file-configurable clients * (Claude Code, Cursor, Desktop, …) — writes the config. * synap mcp connect-claude — print the claude.ai (web) OAuth connection * steps. claude.ai's connector UI is OAuth-only (no * header field), so this prints paste-ready values * instead of writing a file — claude.ai + the control * plane drive the actual OAuth handshake. * * For file-configurable clients, prefer `synap mcp connect ` (it mints a * dedicated agent key + writes the client's config). `synap mcp url` is the * escape hatch for clients you must configure by hand in a UI. */ interface McpBaseOpts { podUrl?: string; apiKey?: string; workspace?: string; project?: string; json?: boolean; } /** * `synap mcp url` — print a ready-to-paste MCP connection for ANY client. * * Provisions a DEDICATED agent key (separate identity, revocable) rather than * echoing the human's full-scope key into an external UI. Prints the URL, the * key, and three paste-ready forms (Claude Code command, native mcpServers JSON, * and the mcp-remote stdio bridge for clients without native HTTP transport). */ export declare function mcpUrl(opts: McpBaseOpts & { client?: string; }): Promise; /** * `synap mcp verify` — health-check the MCP endpoint + the active key. * Confirms /mcp is reachable (manifest) and the key authenticates, so the user * knows the connection works before wiring a client to it. */ export declare function mcpVerify(opts: McpBaseOpts): Promise; /** * `synap mcp connect-claude` — print the claude.ai (web) OAuth connection. * * claude.ai's "Add custom connector" UI is OAuth-only (Dynamic Client * Registration) — it has no field for a bearer header, so the file/header * based flows (`mcp connect`, `mcp url`) don't apply. The control plane's * `/mcp` endpoint now speaks OAuth, so connecting is: paste a URL, approve in * the browser. This command can't drive that click-through itself — claude.ai * and the control plane own the OAuth handshake — it only prints the exact * values so there's no guesswork. */ export declare function mcpConnectClaudeWeb(opts: McpBaseOpts & { cpUrl?: string; }): Promise; export {};