Parsley MCP Server v0.2.1

Access your Parsley recipes, menus, ingredients, and events from any MCP client.

Remote (Hosted)

Point your MCP client at the hosted endpoint. You'll need a Parsley API token, passed as a Bearer token or as a ?token= query parameter.

{
  "mcpServers": {
    "parsley": {
      "type": "streamable-http",
      "url": "https://parsley.vein.io/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_PARSLEY_API_TOKEN"
      }
    }
  }
}

To enable write operations (create/update events, manage users), use /mcp/write instead of /mcp.

Local (stdio)

Run the server locally via npx:

{
  "mcpServers": {
    "parsley": {
      "command": "npx",
      "args": ["-y", "parsley-mcp"],
      "env": {
        "PARSLEY_API_TOKEN": "YOUR_PARSLEY_API_TOKEN"
      }
    }
  }
}

Add --enable-writes to args to enable write operations.

Endpoints

• /mcp — read-only MCP endpoint
• /mcp/write — read-write MCP endpoint
• /mcp/demo — demo endpoint (no auth required)

Filtering tools

Pass ?tools=a,b,c to register only the tools you need:

https://parsley.vein.io/mcp?tools=list_menu_items,get_recipe,list_events

Unknown names return 400. Works on all endpoints.