PinAppAI turns visual website feedback into work your coding agent can actually do. Reviewers open your live site, click any element, and leave a pin. Each pin is captured with the element locator, the page URL, the device and viewport it was seen on, and an optional screenshot, so feedback never arrives as "the button looks off on mobile" with no way to act on it. Every pin becomes a structured change request. Your agent picks those up through this connector. It reads the inbox of open change requests, applies them in your codebase, and marks them resolved, closing the loop from feedback to shipped change without anyone copying text between a browser and an editor. 38 tools and 10 guided workflows cover the whole loop: the change request inbox and apply cycle, review summaries and pattern analysis across feedback, screenshots, projects and workspaces, team members and invited reviewers, audit events, and API keys. Discovery is keyless, so any client can list the tools before signing in. Running a tool needs a workspace API key sent as an Authorization bearer header, and free accounts can create one from the dashboard. Works with any client that speaks streamable HTTP MCP, including Claude Code, Codex CLI, Cursor, Claude Desktop, and Continue. A stdio npm package (@pinappai/mcp) is also published for CI and headless setups.
MCP readiness
Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here B, 79.2/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ
| Valid MCP handshake | 10/10 | initialize and tools/list both answered. |
| Live MCP endpoint | 25/25 | Endpoint answers the MCP initialize handshake (1403 ms). |
| Protocol revision | 8/10 | Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28. |
| Signed descriptor | n/a | No MCP standard defines a signed server descriptor. |
| Uptime (30 days) | 14.5/15 | 29/30 probes succeeded over 30 days (97%). |
| Tool declaration | 10/10 | Lists 38 tool(s) with descriptions. |
| Verified identity | 5/10 | Publisher declared (repository, package or homepage); claim this listing to verify domain control. |
| Freshness + modern flags | 4/5 | seen in a source within 7 days. |
| Auth declaration | 2/5 | Declares credential scheme: smithery_api_key. |
Compared with peers
Against 53,039 reachable MCP servers in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.
- Readiness
- Higher than 90% of peers
- This listing 87 · peer median 81
- Latency
- Faster than 12% of peers
- This listing 816 ms · peer median 326 ms
Where it loses the most points, and how to win them back
- Verified identity −5
— Claim the listing and prove control of its domain.
Now: Publisher declared (repository, package or homepage); claim this listing to verify domain control.
- Auth declaration −3
— State how to authenticate (an auth scheme, or that none is needed).
Now: Declares credential scheme: smithery_api_key.
- Protocol revision −2
— Support the current protocol revision.
Now: Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28.
Listed in
Directories this entry was found in.
How to connect
https://server.smithery.ai/pinappai/mcp/mcpcurl -X POST https://server.smithery.ai/pinappai/mcp/mcp \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'