Desktop clients
Back to Platform

MCP desktop clients

Common desktop AI apps and clients that work well with Onboard MCP.

Local-first AI workspaces and desktop clients are strong surfaces for MCP with Onboard. We position this as operational AI—onboarding copilots, launch coordination, and CS workflows—not only “connect a chatbot.”

Start with MCP setup for production URLs and your API key. For how to connect (including OAuth and MCP Inspector), use Connecting to Onboard MCP. Auth model details: Security & permissions (MCP).

Production hosted MCP uses https://rest.onboard.io under /mcp/. When a product asks for a single URL, use https://rest.onboard.io/mcp/sse with no trailing slash. Full endpoint table: MCP setup.

Supported AI clients (auth model)

ClientSupportedAuthentication
Claude DesktopYesOAuth (per user)
Claude organization / custom connectorsYesOAuth (per user)
Amazon QuickYesAPI key
OpenAI Agent BuilderYesAPI key
OpenAI Agents (setup & chat)YesOAuth (per user)
RaycastYesAPI key
CursorYesAPI key
MCP InspectorYesAPI key or OAuth (testing)
GeminiYesAPI key
PerplexityYesAPI key
cURL / raw HTTPYesAPI key
Claude CodeYesAPI key
Paperclip, Microsoft CopilotNo

“Supported” means we have validated hosted MCP on that surface. Auth column is the primary path for Onboard—not every build of every app exposes both options. Full who-gets-access comparison: Security & permissions (MCP).

Client guides

Other clients

These surfaces share the same hosted SSE URL and API key pattern. Complete MCP setup first.

Gemini

gemini mcp add --transport sse --header "Authorization: Bearer $YOUR_API_KEY" onboard https://rest.onboard.io/mcp/sse

Claude Code

claude mcp add --transport sse onboard https://rest.onboard.io/mcp/sse --header "Authorization: Bearer $YOUR_API_KEY"

After install, run /mcp in a Claude Code session for server details.

Raycast

Build a Raycast script that calls https://rest.onboard.io/... with Authorization: Token … (Authentication), or point an MCP-capable Raycast integration at https://rest.onboard.io/mcp/sse with your API key.

Windsurf

Register a remote MCP server whose HTTP/SSE URL is https://rest.onboard.io/mcp/sse and add your Onboard API key from Integrations → API.

Alfred

Store the API key in a workflow variable or Keychain-backed script. Call REST endpoints with Authorization: Token YOUR_KEY, or configure an MCP bridge to https://rest.onboard.io/mcp/sse. Scrub secrets before exporting workflows.

Next

Pick a guide from the table above, or continue the curriculum on MCP.

How is this guide?

On this page