Skip to content

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

Merged
us merged 2 commits into
mainfrom
feat/smithery-yaml
Aug 24, 2026
Merged

chore(mcp): add Smithery stdio config for crw-mcp#316
us merged 2 commits 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.
@us
us force-pushed the feat/smithery-yaml branch from 1da3b7d to 2f70ef8 Compare August 24, 2026 15:15
crw-mcp selects cloud vs embedded mode on CRW_API_URL being present
(crw-mcp/src/main.rs), so handing it only CRW_API_KEY left every Smithery
install in local embedded mode while the user believed they were on the
hosted API. The canonical installer already pairs the two
(mcp/crw-mcp/bin/install.js); match it. An install with no key is
unchanged and still resolves from the local config.
@us
us merged commit 566eb85 into main Aug 24, 2026
10 checks passed
@github-actions github-actions Bot locked and limited conversation to collaborators Aug 24, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant