Skip to content

chore(mcp): add Smithery stdio config for crw-mcp#316

Open
us wants to merge 1 commit into
mainfrom
feat/smithery-yaml
Open

chore(mcp): add Smithery stdio config for crw-mcp#316
us wants to merge 1 commit into
mainfrom
feat/smithery-yaml

Conversation

@us

@us us commented Jul 18, 2026

Copy link
Copy Markdown
Owner

Adds a repo-root smithery.yaml so crw-mcp can be listed and installed via Smithery (smithery.ai).

What

  • smithery.yaml with a startCommand.type: stdio block that launches the published crw-mcp npm package: npx -y crw-mcp.
  • configSchema exposes one optional field crwApiKey, mapped to the CRW_API_KEY env var the binary already reads. Optional because the free tier and self-host work without a key.
  • exampleConfig uses a placeholder key (no secret committed).

Why

Smithery has two publish paths: the URL method (a hosted streamable-HTTP + OAuth endpoint, already served at https://fastcrw.com/mcp) and the local stdio path. This file enables the local stdio install; the remote endpoint is listed separately via Smithery`s URL method and needs no repo file.

Notes

  • File must live at repo root for Smithery to find it; matches the stdio schema used across published Smithery servers.
  • No Rust/config touched, so the pre-commit Rust suite is a no-op for this change.
  • Publishing the listing itself is a one-time manual step on smithery.ai (GitHub-OAuth connect / URL submit); this PR only lands the config.

smithery.yaml at repo root launches the published crw-mcp npm package on
stdio (npx -y crw-mcp) with a configSchema exposing an optional fastCRW
API key mapped to CRW_API_KEY. Enables Smithery's local install path;
the hosted https://fastcrw.com/mcp endpoint is listed via the URL method.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant