Skip to main content
collectionsSource-backed
Raycast logo

Raycast Claude Power Workflow

A source-backed collection for keyboard-first Claude power users on macOS: Raycast launcher access, HeyClaude API/MCP/Raycast surface selection, MCP setup, skill installation, reusable slash commands, and Raycast extension development or publishing.

by MkDev11·added 2026-06-04·
HarnessRaycast
Bundle:6 items
Review first review before installing

Open the source and read safety notes before installing.

Citation facts

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Source URLs
https://developers.raycast.com/, https://github.com/JSONbored/awesome-claude/blob/main/content/collections/raycast-claude-power-workflow.mdx
Brand
Raycast
Brand domain
raycast.com
Brand asset source
brandfetch
Safety notes
Raycast is a fast launcher surface; review any copied install command, MCP config, skill archive, slash command, or extension action before applying it to a real workspace., MCP setup can connect Claude to tools with file, network, database, browser, or account access, so approve server permissions and credentials before launching from Raycast., Slash commands and Raycast extensions can wrap multi-step workflows; keep destructive operations, publishing, submissions, and credentialed actions behind explicit human confirmation., Extension publishing should be tested against Raycast guidance, permission needs, metadata, icons, screenshots, and store-readiness checks before public release.
Privacy notes
Raycast searches, local favorites, clipboard history, copied install snippets, extension preferences, AI prompts, and cached feed data can reveal what resources and workflows a user is researching., MCP tool arguments, server responses, local files, browser targets, API tokens, and Claude Code transcripts may be surfaced through launcher-initiated workflows., Team-shared Raycast extensions, Quicklinks, snippets, and screenshots can expose internal URLs, project names, resource choices, or contribution drafts if not reviewed first.
Author
MkDev11
Submitted by
MkDev11
Claim status
unclaimed
Last verified
2026-06-04

Decision playbook

Review trust signals before you adopt

Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.

Compare context
Selected

0

Current score

78

Baseline

Delta

No baseline selected

No major trust-signal divergence detected in the current selection.

Source and provenance checks

Complete

Confirm ownership and provenance before trusting install instructions.

  • Source link availableRequired

    Open the canonical repository and verify ownership.

    Done
  • Source provenance statusRequired

    Marked as source-backed.

    Done
  • Metadata reviewed

    Registry metadata indicates a reviewed listing.

    Done

Safety and privacy checks

Complete

Validate risk disclosures before installation or API wiring.

  • Safety notes presentRequired

    Review the listed safety guidance before running commands.

    Done
  • Privacy notes presentRequired

    Review data handling notes before connecting accounts or secrets.

    Done
  • Trust level risk gateRequired

    Trust level does not block evaluation.

    Done

Package and install checks

Needs review

Check package metadata and artifact integrity signals.

  • Install payload available

    Install or copy payload is available for review.

    Done
  • Package verification flag

    No package verification flag provided.

    Pending
  • Checksum metadata

    No checksum provided for downloaded artifact.

    Pending

Compare-driven decision checks

Needs review

Use compare context to validate trade-offs before adoption.

  • Compare tray has multiple entries

    Add at least one more entry to compare trust differences.

    Pending
  • Baseline comparison available

    No baseline peer selected yet.

    Pending
  • Diverging trust signals identified

    No major trust-signal divergence found.

    Pending

Setup at a glance

Copy & paste

Copy-ready — paste the snippet to get started.

55 minutes

Adoption plan

Balanced adoption plan

Current risk score 16/100. Use staged verification before broader rollout.

Risk 16

Pre-adoption checks

Validate source and review signals before any execution.

  • Confirm source provenanceRequired

    Source URL/provenance metadata is present.

    Done
  • Confirm metadata review state

    Listing has review metadata.

    Done
  • Verify install payload

    Install/config payload exists and can be inspected.

    Done

Security checks

Confirm safety, privacy, and package integrity signals.

  • Review safety notesRequired

    Safety notes are present.

    Done
  • Review privacy notesRequired

    Privacy notes are present.

    Done
  • Verify package integrity metadata

    No package verification/checksum metadata.

    Pending

Rollout

Adopt in controlled steps based on the selected plan.

  • Run in isolated sandbox firstRequired

    Use a constrained sandbox and observe behavior across multiple tasks.

    Pending
  • Roll out graduallyRequired

    Roll out to a small cohort before wider usage.

    Pending
  • Set monitoring and fallback

    Define rollback path and monitor errors after adoption.

    Pending

Evidence readiness

Evidence readiness matrix · balanced

Required evidence gates are covered (5/6 signals complete).

Risk 15

Source provenance

Present

Source repository/provenance is listed.

Required in this preset

Metadata review

Present

Review metadata is present.

Required in this preset

Safety notes

Present

Safety notes are present.

Required in this preset

Privacy notes

Present

Privacy notes are present.

Optional in this preset

Package integrity

Missing

Package integrity metadata is missing.

Optional in this preset

Install payload

Present

Install payload is available.

Required in this preset

Required evidence gates are covered for this preset.

Decision timeline

Decision timeline · balanced

5/6 steps complete with no blocking gaps for this preset.

Risk 14

triage

Confirm source provenanceRequired

Source/provenance metadata is available.

Done

triage

Check metadata review statusRequired

Review metadata is available.

Done

verify

Review safety notesRequired

Safety notes are available.

Done

verify

Review privacy notes

Privacy notes are available.

Done

verify

Validate package integrity metadata

Package integrity metadata is missing.

Pending

rollout

Verify install payload and commandsRequired

Install payload is available.

Done

No required blockers for this timeline preset.

Prerequisite readiness

Prerequisite readiness

4 prerequisites to line up before setup. Have accounts and credentials ready first.

0/4 ready
Account & credentials3Install & runtime155 minutes

Safety & privacy surface

Safety & privacy surface

4 safety and 3 privacy notes across 4 risk areas. Review closely: credentials & tokens, permissions & scopes.

4 areas
  • SafetyExecution & processesRaycast is a fast launcher surface; review any copied install command, MCP config, skill archive, slash command, or extension action before applying it to a real workspace.
  • SafetyCredentials & tokensMCP setup can connect Claude to tools with file, network, database, browser, or account access, so approve server permissions and credentials before launching from Raycast.
  • SafetyCredentials & tokensSlash commands and Raycast extensions can wrap multi-step workflows; keep destructive operations, publishing, submissions, and credentialed actions behind explicit human confirmation.
  • SafetyPermissions & scopesExtension publishing should be tested against Raycast guidance, permission needs, metadata, icons, screenshots, and store-readiness checks before public release.
  • PrivacyExecution & processesRaycast searches, local favorites, clipboard history, copied install snippets, extension preferences, AI prompts, and cached feed data can reveal what resources and workflows a user is researching.
  • PrivacyCredentials & tokensMCP tool arguments, server responses, local files, browser targets, API tokens, and Claude Code transcripts may be surfaced through launcher-initiated workflows.
  • PrivacyGeneralTeam-shared Raycast extensions, Quicklinks, snippets, and screenshots can expose internal URLs, project names, resource choices, or contribution drafts if not reviewed first.

Safety notes

  • Raycast is a fast launcher surface; review any copied install command, MCP config, skill archive, slash command, or extension action before applying it to a real workspace.
  • MCP setup can connect Claude to tools with file, network, database, browser, or account access, so approve server permissions and credentials before launching from Raycast.
  • Slash commands and Raycast extensions can wrap multi-step workflows; keep destructive operations, publishing, submissions, and credentialed actions behind explicit human confirmation.
  • Extension publishing should be tested against Raycast guidance, permission needs, metadata, icons, screenshots, and store-readiness checks before public release.

Privacy notes

  • Raycast searches, local favorites, clipboard history, copied install snippets, extension preferences, AI prompts, and cached feed data can reveal what resources and workflows a user is researching.
  • MCP tool arguments, server responses, local files, browser targets, API tokens, and Claude Code transcripts may be surfaced through launcher-initiated workflows.
  • Team-shared Raycast extensions, Quicklinks, snippets, and screenshots can expose internal URLs, project names, resource choices, or contribution drafts if not reviewed first.

Prerequisites

  • macOS with Raycast installed and the user account authorized for any extensions, AI features, clipboard actions, or team workflows being used.
  • Claude Code installed with a reviewed project workspace, approved MCP servers, and a clear boundary for what Raycast should open, copy, or launch.
  • HeyClaude workflow goals such as resource discovery, install guidance, daily lookup, MCP context, submission drafting, or extension development.
  • Policy for local favorites, cached feeds, snippets, copied install commands, extension permissions, API keys, and team-shared Raycast artifacts.

Schema details

Install type
copy
Troubleshooting
No
Collection metadata
Items
6 entries
Estimated setup
55 minutes
Difficulty
intermediate
Installation order
raycastheyclaude-api-mcp-raycast-workflowsmcp-setupskills-installerslash-command-genraycast-extension-dev-publish-capability-pack
Full copyable content
## What this collection sets up

This collection is for users who want Raycast to be the keyboard-first surface
around Claude and HeyClaude. It combines quick lookup, install-copy actions,
API/MCP/Raycast surface selection, MCP setup, skill installation, reusable slash
commands, and Raycast extension development.

The intent is speed with review. Raycast should make approved actions easy to
find and launch, but commands, skills, MCP servers, and extensions still need
normal source, permission, and privacy review before they touch a real project.

## Layers

### 1. Launcher and surface selection

- **raycast** is the macOS launcher and extension platform for commands,
  automations, AI workflows, copy actions, and developer integrations.
- **heyclaude-api-mcp-raycast-workflows** explains when to use the HeyClaude
  API, MCP server, or Raycast extension surface for discovery, comparison,
  install guidance, feed sync, and contribution workflows.

### 2. Claude workspace setup from Raycast-discovered resources

- **mcp-setup** helps connect approved MCP servers to Claude Code after the
  server source, credentials, and tool permissions are reviewed.
- **skills-installer** installs approved skills so Raycast-discovered resources
  can become reusable Claude Code capabilities.
- **slash-command-gen** turns repeat tasks into explicit slash commands that can
  be launched or copied from a keyboard-first workflow.

### 3. Building the Raycast surface

- **raycast-extension-dev-publish-capability-pack** guides command design,
  extension architecture, testing, metadata, and publish-readiness for teams
  that want to build or ship their own Raycast extension.

## Suggested order

Start by setting up Raycast and deciding which daily actions belong in the
launcher. Use the HeyClaude API/MCP/Raycast guide to choose the right surface
for lookup, context, install guidance, and submission drafting. Add MCP servers
only after permissions and credentials are reviewed. Install skills from trusted
sources, then turn repeated work into slash commands. Build or publish Raycast
extensions last, after the workflow has been used enough to justify a dedicated
launcher command.

## Power-user checklist

- [ ] {"task": "Surface is chosen", "description": "Raycast, API, and MCP responsibilities are mapped before workflows are automated"}
- [ ] {"task": "Install commands are reviewed", "description": "Copied snippets and skill archives are checked before running in a workspace"}
- [ ] {"task": "MCP permissions are scoped", "description": "Servers, credentials, and tool side effects are approved before launcher access"}
- [ ] {"task": "Slash commands are explicit", "description": "Repeated workflows have clear inputs, outputs, safety stops, and review points"}
- [ ] {"task": "Extension metadata is ready", "description": "Permissions, screenshots, icons, categories, and store guidance are checked before publishing"}
- [ ] {"task": "Local traces are understood", "description": "Favorites, feed caches, clipboard data, prompts, and extension preferences have retention rules"}

## Source and references

- Raycast developer documentation: https://developers.raycast.com/
- Raycast getting started: https://developers.raycast.com/basics/getting-started
- Raycast extension publishing: https://developers.raycast.com/basics/publish-an-extension
- HeyClaude Raycast feed: https://heyclau.de/data/raycast-index.json
- HeyClaude Raycast README: https://github.com/JSONbored/awesome-claude/blob/main/integrations/raycast/README.md
- Model Context Protocol introduction: https://modelcontextprotocol.io/docs/getting-started/intro
- Claude Code MCP documentation: https://code.claude.com/docs/en/mcp
- Claude Code skills documentation: https://code.claude.com/docs/en/skills
- Claude Code slash commands documentation: https://code.claude.com/docs/en/slash-commands

## Duplicate check

Checked existing collections, guides, tools, commands, skills, open PRs, closed
PRs, and issue history for `raycast-claude-power-workflow`, Raycast Claude
workflow, HeyClaude Raycast, Raycast MCP, Raycast extension publishing, skills
installer, slash command generator, and launcher workflows.
`heyclaude-api-mcp-raycast-workflows` is a guide for choosing between
integration surfaces. The `raycast` tool entry documents the launcher, and the
Raycast extension skill covers extension development. This collection bundles
those pieces into a power-user workflow for daily lookup, setup, automation, and
extension building.

## Disclosure

Editorial collection. No paid placement or affiliate link is used.

About this resource

What this collection sets up

This collection is for users who want Raycast to be the keyboard-first surface around Claude and HeyClaude. It combines quick lookup, install-copy actions, API/MCP/Raycast surface selection, MCP setup, skill installation, reusable slash commands, and Raycast extension development.

The intent is speed with review. Raycast should make approved actions easy to find and launch, but commands, skills, MCP servers, and extensions still need normal source, permission, and privacy review before they touch a real project.

Layers

1. Launcher and surface selection

  • raycast is the macOS launcher and extension platform for commands, automations, AI workflows, copy actions, and developer integrations.
  • heyclaude-api-mcp-raycast-workflows explains when to use the HeyClaude API, MCP server, or Raycast extension surface for discovery, comparison, install guidance, feed sync, and contribution workflows.

2. Claude workspace setup from Raycast-discovered resources

  • mcp-setup helps connect approved MCP servers to Claude Code after the server source, credentials, and tool permissions are reviewed.
  • skills-installer installs approved skills so Raycast-discovered resources can become reusable Claude Code capabilities.
  • slash-command-gen turns repeat tasks into explicit slash commands that can be launched or copied from a keyboard-first workflow.

3. Building the Raycast surface

  • raycast-extension-dev-publish-capability-pack guides command design, extension architecture, testing, metadata, and publish-readiness for teams that want to build or ship their own Raycast extension.

Suggested order

Start by setting up Raycast and deciding which daily actions belong in the launcher. Use the HeyClaude API/MCP/Raycast guide to choose the right surface for lookup, context, install guidance, and submission drafting. Add MCP servers only after permissions and credentials are reviewed. Install skills from trusted sources, then turn repeated work into slash commands. Build or publish Raycast extensions last, after the workflow has been used enough to justify a dedicated launcher command.

Power-user checklist

  • {"task": "Surface is chosen", "description": "Raycast, API, and MCP responsibilities are mapped before workflows are automated"}
  • {"task": "Install commands are reviewed", "description": "Copied snippets and skill archives are checked before running in a workspace"}
  • {"task": "MCP permissions are scoped", "description": "Servers, credentials, and tool side effects are approved before launcher access"}
  • {"task": "Slash commands are explicit", "description": "Repeated workflows have clear inputs, outputs, safety stops, and review points"}
  • {"task": "Extension metadata is ready", "description": "Permissions, screenshots, icons, categories, and store guidance are checked before publishing"}
  • {"task": "Local traces are understood", "description": "Favorites, feed caches, clipboard data, prompts, and extension preferences have retention rules"}

Source and references

Duplicate check

Checked existing collections, guides, tools, commands, skills, open PRs, closed PRs, and issue history for raycast-claude-power-workflow, Raycast Claude workflow, HeyClaude Raycast, Raycast MCP, Raycast extension publishing, skills installer, slash command generator, and launcher workflows. heyclaude-api-mcp-raycast-workflows is a guide for choosing between integration surfaces. The raycast tool entry documents the launcher, and the Raycast extension skill covers extension development. This collection bundles those pieces into a power-user workflow for daily lookup, setup, automation, and extension building.

Disclosure

Editorial collection. No paid placement or affiliate link is used.

Source citations

Add this badge to your README

Show that Raycast Claude Power Workflow is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/collections/raycast-claude-power-workflow.svg)](https://heyclau.de/entry/collections/raycast-claude-power-workflow)

How it compares

Raycast Claude Power Workflow side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

3 trust signals differ across this comparison (Package trust, Source provenance, Submitter).

Next steps differ across entries — use the actions in the table below to copy install commands and source links per resource.

Field

A source-backed collection for keyboard-first Claude power users on macOS: Raycast launcher access, HeyClaude API/MCP/Raycast surface selection, MCP setup, skill installation, reusable slash commands, and Raycast extension development or publishing.

Open dossier

Expert Raycast extension capability skill for command design, extension architecture, testing, and store-ready publication workflows.

Open dossier

macOS launcher and extension platform with AI commands, automations, team workflows, and developer-focused integrations.

Open dossier

Claude Code slash command that generates a new .claude/commands/*.md file from a template, with optional arguments, frontmatter, and team-sharing support.

Open dossier
Next stepsDiffers
Trust
Review statusReviewedMaintainer reviewedReviewedMaintainer reviewedReviewedMaintainer reviewedReviewedMaintainer reviewed
Package trustDiffersPackage not verifiedPackage verified2026-04-10Package not verifiedPackage not verified
Source provenanceDiffersSource-backedNo submission linkSource-backedSource-backed
SubmitterDiffersMkDev11
Install riskReview firstLow riskReview firstReview first
Notes Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety · Privacy ✓ Safety ✓ Privacy ✓
BrandRaycast logoRaycastRaycast logoRaycastRaycast logoRaycast
Categorycollectionsskillstoolscommands
SourceSource-backedFirst-partySource-backedSource-backed
AuthorMkDev11JSONboredRaycastJSONbored
Added2026-06-042026-04-102026-04-272025-10-25
Platforms
Harness
Source repo
Safety notesRaycast is a fast launcher surface; review any copied install command, MCP config, skill archive, slash command, or extension action before applying it to a real workspace. MCP setup can connect Claude to tools with file, network, database, browser, or account access, so approve server permissions and credentials before launching from Raycast. Slash commands and Raycast extensions can wrap multi-step workflows; keep destructive operations, publishing, submissions, and credentialed actions behind explicit human confirmation. Extension publishing should be tested against Raycast guidance, permission needs, metadata, icons, screenshots, and store-readiness checks before public release.Installs from a downloaded package and may run local commands or scaffold files as part of the workflow; review the package and any generated changes before applying.— missingCreates .md files in .claude/commands/ in the current project directory; review generated content before committing.
Privacy notesRaycast searches, local favorites, clipboard history, copied install snippets, extension preferences, AI prompts, and cached feed data can reveal what resources and workflows a user is researching. MCP tool arguments, server responses, local files, browser targets, API tokens, and Claude Code transcripts may be surfaced through launcher-initiated workflows. Team-shared Raycast extensions, Quicklinks, snippets, and screenshots can expose internal URLs, project names, resource choices, or contribution drafts if not reviewed first.Operates on your local project files and any context you share in the session; review what you expose before sharing — nothing is sent beyond the model unless a step calls an external service.Raycast AI features send your prompts (and selected context) to AI model providers; review which commands invoke AI and what data they include before using them on sensitive content.Creates .md files in your local .claude/commands/ directory; no content is sent externally.
Prerequisites
  • macOS with Raycast installed and the user account authorized for any extensions, AI features, clipboard actions, or team workflows being used.
  • Claude Code installed with a reviewed project workspace, approved MCP servers, and a clear boundary for what Raycast should open, copy, or launch.
  • HeyClaude workflow goals such as resource discovery, install guidance, daily lookup, MCP context, submission drafting, or extension development.
  • Policy for local favorites, cached feeds, snippets, copied install commands, extension permissions, API keys, and team-shared Raycast artifacts.
  • Raycast extension project setup
  • Product use case and command plan
  • API access for external integrations
— none listed— none listed
Install
curl -L https://heyclau.de/downloads/skills/raycast-extension-dev-publish-capability-pack.zip -o raycast-extension-dev-publish-capability-pack.zip && unzip -o raycast-extension-dev-publish-capability-pack.zip -d ./raycast-extension-dev-publish-capability-pack
/slash-command-gen [command-name] [options]
Config
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed
Open 4 picks in the interactive comparison tool

Related guides

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.