MCP 서버는 모든 MCP 호환 클라이언트에 Raycast 확장을 브릿지.

로컬에 설치된 Raycast 확장 기능을 발견하고 도구 정의를로드하고 stdio 또는 HTTP를 통해 Model Context Protocol을 통해 제공합니다.

어떻게 작동합니까?

1. Scans ~/.config/raycast/extensions/ tools 정의에 설치된 확장
2. Raycast의 암호화 된 SQLite 데이터베이스에서 OAuth 토큰로드
3. MCP 클라이언트에 접근 가능한 MCP 도구로 등록

Raycast UI APIs(List], Detail], Form] 등)를 사용하는 확장은 지원됩니다. - UI 구성 요소는 no-ops에 shimmed이므로 언더링 도구 로직을 실행할 수 있습니다. 도구가 배경 작업을 수행하는 확장 (API 호출, 데이터 조회, 변환) 최고의.

설치

# 필수품

• 분
• Raycast는 확장에 설치
• sqlcipher CLI (OAuth 토큰 액세스) : brew install sqlcipher]

설치

MCP 클라이언트 구성

** 코드** (~/.claude/settings.json):

** 암호** (~/.cursor/mcp.json):

HTTP 전송

서버는 또한 먼 MCP 클라이언트를 위한 HTTP 서버로 달릴 수 있습니다.

서버 시작:

** 엔드포인트:**

RayBridge

MCP server that bridges Raycast extensions to any MCP-compatible client.

Discovers locally installed Raycast extensions, loads their tool definitions, and serves them over the Model Context Protocol via stdio or HTTP.

How it works

1. Scans ~/.config/raycast/extensions/ for installed extensions with tools definitions
2. Loads OAuth tokens from Raycast’s encrypted SQLite database
3. Registers tools as MCP tools accessible to any MCP client

Extensions that use Raycast UI APIs (List, Detail, Form, etc.) are supported — the UI components are shimmed to no-ops so the underlying tool logic can execute headlessly. Extensions whose tools perform background work (API calls, data lookups, transformations) work best.

Setup

Prerequisites

• Bun
• Raycast installed with extensions
• sqlcipher CLI (for OAuth token access): brew install sqlcipher

Install

bun install

Configure MCP client

Claude Code (~/.claude/settings.json):

{
  "mcpServers": {
    "raybridge": {
      "command": "bun",
      "args": ["run", "src/index.ts"],
      "cwd": "/path/to/raybridge"
    }
  }
}

Cursor (~/.cursor/mcp.json):

{
  "mcpServers": {
    "raybridge": {
      "command": "bun",
      "args": ["run", "src/index.ts"],
      "cwd": "/path/to/raybridge"
    }
  }
}

HTTP Transport

The server can also run as an HTTP server for remote MCP clients.

Start the server:

# Default: http://0.0.0.0:3000
bun run start:http

# Custom host/port
MCP_PORT=8080 MCP_HOST=0.0.0.0 bun run start:http

# With API key authentication
MCP_API_KEY=your-secret-key bun run start:http

# CLI flags also work
bun run src/index.ts --http --port 8080 --host 0.0.0.0

Endpoints:

Authentication:

When MCP_API_KEY is set, requests to /mcp must include a Bearer token (per MCP spec):

Authorization: Bearer your-secret-key

Example session:

# 1. Initialize session (capture session ID from response header)
curl -X POST http://127.0.0.1:3000/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "Authorization: Bearer your-secret-key" \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{
    "protocolVersion":"2024-11-05",
    "capabilities":{},
    "clientInfo":{"name":"my-client","version":"1.0"}
  }}'
# Response includes: mcp-session-id header

# 2. List available tools
curl -X POST http://127.0.0.1:3000/mcp \
  -H "Content-Type: application/json" \