Ravelry MCP Server

MCP server for the Ravelry knitting/crochet API. The ravelry mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 14 defined tools rather than through you.

What it actually does

An MCP server that gives Claude full access to the Ravelry knitting and crochet API — pattern search, yarn database, and your personal notebook (queue, stash, projects, favorites, library).

Its toolset

Everything the assistant can do here goes through one of these:

• ravelry_whoami — Verify credentials and return the authenticated user's username, avatar, and profile URL
• search_patterns — query, craft, availability, yarn_weight, difficulty_min, difficulty_max, fit, pc, colors, page, page_size, sort
• get_pattern — id (required)
• get_patterns — ids[] (required, max 100)
• search_yarns — query, weight, fiber_type, company_name, rating_min, discontinued, page, page_size, sort
• get_yarn — id (required)
• get_yarns — ids[] (required, max 100)
• get_current_user — —
• get_queue — query, page, page_size
• add_to_queue — pattern_id, stash_id?, sort_position?
• remove_from_queue — queue_entry_id
• get_stash — query, weight, color_family, stash_status, page, page_size

Configuration

You will need 2 environment variables: RAVELRY_ACCESS_KEY, RAVELRY_PERSONAL_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• Node.js 18 or later - A free Ravelry account - Claude Desktop

Adding it to your client

The server ships on npm as npm, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

When to reach for it

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Ravelry's toolset — ravelry_whoami, search_patterns, get_pattern and 11 more — is a fair guide to whether it matches your workflow. It is maintained by buzzsurfr; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Ravelry's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Ravelry.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the ravelry mcp server does with a few real requests.