pavel 1ar.ionov

Raycast Bridges

Connect any REST API, MCP server, or CLI tool to Raycast AI

Raycast Bridges makes Raycast AI extensible: connect any REST API, MCP server, or shell CLI, describe it in plain English, and an agent (Claude) searches for real docs, writes a config and a guide, then prompts you for credentials. The result is a callable tool the AI can use in any future conversation.

Capability Types

TypeWhat it doesExamples
API SourceAuthenticated REST API callsCraft API, GitHub API, Stripe
MCP ServerModel Context Protocol servers (stdio or remote)GitHub MCP, Craft MCP
CLI ToolShell CLI execution (30s timeout, 50KB output)gh, vercel, kubectl, yt-dlp
SkillAI instructions referencing other capabilities“Review my daily notes”

How it works

  1. Add Capability — describe an API, MCP server, CLI tool, or skill in plain English. An agent searches the web for real docs, writes a config and a guide, then prompts you for credentials if needed.
  2. Use it — ask Raycast AI anything that involves that capability. It discovers capabilities via keyword search, reads the guide once, then makes authenticated requests or executes commands on your behalf.
  3. Manage — edit configs, rotate credentials, disable or remove capabilities from the Manage Capabilities command.

Prerequisites

AI Tools

Four tools are registered in Raycast AI, used automatically in conversations:

ToolPurpose
search-capabilitiesKeyword search across names, descriptions, and guides. Called first.
list-capabilitiesLists all installed capabilities. Fallback when search returns nothing.
get-capability-guideLoads full documentation for a capability. Called once per conversation.
call-capabilityExecutes: REST API calls, MCP pseudo-paths, or CLI commands.

Privacy

Everything runs locally. Credentials stay in ~/.bridges/ on your machine. No proxy, no middleman.

Open source

Raycast Bridges is open source. Inspired by Craft Agents.

View on GitHub →