@webpinch/mcp

WebPinch ships anMCPserver (@webpinch/mcp) that exposes your tasks, projects, site audits, and stats to Claude Code, Cursor, and any other MCP client.

It’s a thin client over theREST API— same auth, same authorization, same response data. Where the REST API gives you raw HTTP endpoints, MCP gives you tools the model can call directly.

- 13 toolsfor reading and writing tasks, projects, audits, and stats
- 4 resourcesfor browseable, mention-able data (projects, tasks, audit reports)
- 3 promptsfor common workflows (triage, audit summary, weekly status)
- Pre-flight scope checks so write attempts fail fast with a clear message instead of an HTTP 403
- A WebPinchpersonal access token. Mint atDashboard → API Tokens.
- Node 18+ on the machine running the MCP client.

{ "mcpServers": { "webpinch": { "command": "npx", "args": ["-y", "@webpinch/mcp"], "env": { "WEBPINCH_TOKEN": "wp_pat_...", "WEBPINCH_API_URL": "https://www.webpinch.com" } } } }

Fully restart Claude Code (quit, don’t just close the window). Run/mcp—webpinchshould be listed asconnectedwith 13 tools, 4 resources, 3 prompts.

Local development?ReplaceWEBPINCH_API_URLwithhttp://localhost:3000. If you’re running the MCP server from a checkout (not yet published to npm), swap thecommand/argstonode /absolute/path/to/mcp-server/src/index.js.

The token is read at server startup and never logged or echoed in tool output. Network errors redact it explicitly.

Output is pruned for token efficiency. List tools never includedescriptionHtmlor full activity logs — call the matchingget_*tool when you need detail.

Write tools fetch your scopes once viawhoamiand cache them. If you ask the model to do something your token can’t do, the tool throwsbeforeany HTTP request:

This action requires the “tasks:write” scope. Your token does not have it. Mint a new token with that scope at /dashboard/settings/api.

Server-side scope enforcement still runs as the source of truth — pre-flight is purely a UX optimization to give the model a useful error message instead of an opaque HTTP 403.

Resources are URIs the model can pull without you naming a tool. In Claude Code’s resource picker / Cursor’s@-mention:

The Markdown audit report is the friendliest way to feed audit results into a chat — it’s pre-formatted, prioritized, and short.

Prompts are saved instructions that compose tools. They show up as slash commands or prompt picks in your client.

Args:projectId?,sinceHours?(default24).

Pulls tasks created in the last N hours, walks each for context (description, screenshot, reporter), and proposes priority + assignee + a one-sentence rationale as a markdown table. Doesn’t mutate anything — review before applying.

Fetches the latest audit for the project, categorizes findings (Critical / High / Medium / Low), and writes a fix list with affected URLs and one-sentence fixes. Ends with a “Top 3 actions for this week” section.

Pulls stats and recent activity, drafts a < 200-word status note in Markdown — what’s new, what’s at risk, per-project progress, what’s coming due.

The MCP spec supports both stdio (process-per-client) and Streamable HTTP (hosted) transports. WebPinch runs both, and they expose the same tools, resources and prompts — pick whichever your client supports.

WebPinch hosts an MCP endpoint athttps://www.webpinch.com/api/mcp. Nothing to install and nothing to keep running — useful for clients that accept a remote MCP URL, such as the Claude.ai and ChatGPT connectors.

{ "mcpServers": { "webpinch": { "url": "https://www.webpinch.com/api/mcp", "headers": { "Authorization": "Bearer wp_pat_..." } } } }

Authentication is per request via theAuthorizationheader rather than an environment variable, so the same endpoint serves every user — the token decides what you can see. The endpoint is stateless and CORS-enabled.

AGETreturns a small discovery document, which is a quick way to confirm reachability:

curl https://www.webpinch.com/api/mcp # {"ok":true,"name":"webpinch-mcp","version":"0.2.1","transport":"http","endpoint":"/api/mcp"}

If you’d rather run it inside your own network, the same server speaks HTTP:

WEBPINCH_TRANSPORT=http PORT=8787 WEBPINCH_TOKEN=wp_pat_... npx -y @webpinch/mcp

It listens onPOST /mcp(and/v1/mcpfor compatibility).

stdio remains the right default for local editors — Claude Code, Cursor and Windsurf all launch the process themselves, so there’s nothing to host and the token stays in your local config.

This is a web browser that enables your coding agent, such as Claude Code, to visit websites on your behalf and assist you in identifying bugs or creating UI test cases.

Share your team's Coding Best Practices with Cursor, VS Code, Claude code, Windsurf, JetBrains IDEs and other coding tools supporting remote MCP connection.

Lance is an agent that runs on its own cloud Mac and handles everything on the App Store Connect side of shipping an iOS app. It connects to coding agents like Claude Code and Codex through MCP and takes over the parts they can't do: creating apps on App Store Connect, setting up notifications / widgets, filling out listing metadata, uploading builds to TestFlight, submitting for review, and responding to App Review feedback. Because it has its own Mac, it can also build, run, and test users' apps and capture screenshots.

AI-powered semantic search over React documentation for Claude, Cursor, and other MCP clients.

AI-native static site generator with built-in MCP server. Build sites, create content, apply themes, search docs, and deploy via Claude Code or any MCP client.

A universal MCP server that connects to any Storybook site and extracts documentation in real-time using Playwright. Use it with any AI or client that supports MCP (Model Context Protocol)—Cursor, Claude Desktop, Windsurf, or other MCP hosts.

Access WordPress documentation and development tools.

The DataFast MCP server lets MCP-compatible clients such as Codex, Claude Code, and Cursor query your analytics and manage your account through natural language.

Inkrun's remote MCP server lets AI agents like Claude turn Markdown into themed, consistent and reproducible on-brand PDFs with a single tool call

Transform your scattered documentation into AI-ready knowledge that works seamlessly with Claude, Cursor, VS Code, and other AI tools.