Raycast Bridges: connect any REST API to Raycast AI
Open-sourcing Raycast Bridges - an extension that lets you connect any REST API to Raycast AI through agent-scaffolded configurations.
Raycast Bridges is now open source on GitHub.
It’s a Raycast extension that connects any REST API, MCP server, or custom skill to Raycast AI. You describe what you want to connect in plain language, an agent scaffolds the configuration, and then Raycast AI can call it directly from your conversations. It picks the right connector - or combines several of them - to finish your task.
How it works
- Run Add Capability and describe what you want to connect - a REST API, an MCP server, or a custom skill
- Claude searches for official docs, generates a
config.jsonandguide.md, then prompts for credentials - Ask Raycast AI anything - it discovers relevant capabilities, reads the docs, and executes using whichever connectors fit the task
Everything runs locally. Credentials stay in ~/.bridges/sources/ on your machine. No proxy, no middleman.
Why I built it
Raycast AI is great for conversations, but it can’t talk to your tools out of the box. I wanted to ask it things like “what’s deployed on my Vercel project” or “show me open PRs” without leaving the command bar - and chain those with custom skills like “summarize and post to Slack.” The official extension API doesn’t expose a way to inject tools into AI conversations - so Bridges works around that by scaffolding documentation that Raycast AI reads at query time.
It’s slightly unconventional, but it works.
What’s next
This is an early release. The scaffolding agent handles common REST patterns well, but edge cases with complex auth flows or pagination will need refinement. Contributions welcome.
- Try it: Raycast Bridges
- GitHub: github.com/pa1ar/raycast-bridges
Join the discussion
On Twitter, Threads, or Reddit (r/raycastapp, r/CraftDocs).