Does Pastel have an MCP server?

Yes, based on their own homepage, which advertises MCP for Claude, Cursor and ChatGPT. We could not load a first-party documentation page for it on 2026-09-01, so the scope, the tool list and any plan gating are unverified. If an agent reading your feedback is central to your decision, ask them directly rather than trusting a comparison page, this one included.

So is Writhink's MCP server a reason to switch?

On its own, no. Having an MCP server has stopped being unusual in this category. The difference worth weighing is what travels through it: at Writhink the agent reads client comments that already carry the pin, the element, the page and the breakpoint, merged and prioritized into implementation language. If your feedback already arrives as structured tickets, that rewriting step buys you much less.

Which is cheaper for an agency with a dozen client sites?

Writhink is free during the beta with no project cap, so today it is cheaper. On Pastel, canvases are the metered resource — a dozen live sites pushes you to their team tier, and the table above carries the prices and the date we checked them. The caveat cuts the other way too: Writhink's beta terms will change and Pastel's price is published.

What can a client do in Writhink without an account?

Pin comments on the exact element, attach up to five files of 10 MB each, reply in a public thread, and edit or delete their own comments. They give a display name and nothing else — no email, no verification. Pastel's guests also need no login but are limited to comments and replies.

Does Writhink do approvals or feedback deadlines?

No. There is no deadline, no reminder schedule, no pause-commenting switch and no formal approval step. You get four statuses, public replies, exports and email digests. If sign-off ceremony is what you are buying, Pastel is built for it and Writhink is not.

Yes, and some studios will want to. Run Pastel for the approval round if that is where your process lives, and put a Writhink review link or widget on the build so the implementation pass has a prompt behind it. They meter different things and neither blocks the other.

Comparison

Writhink vs Pastel: sign-off is one job, shipping the change is another

Pastel is a website annotation tool with a real approvals workflow behind it: feedback deadlines, reminders, pause commenting, formal sign-off. Writhink does none of that and spends its effort elsewhere, turning what your client wrote into one prompt your AI coding assistant can act on. If your bottleneck is getting a yes, Pastel may well be the right tool, and this page says where that line falls.

Try it free during the beta

No credit card. Your client doesn’t need an account.

What Pastel is good at

Pastel is built around getting a client to say yes. Feedback deadlines, deadline reminders, pause commenting, comment labels, assigning, approvals — the sign-off half of an agency project is a product area there, not a checkbox. If your problem is a client who never finishes reviewing, that machinery is the whole point.

It also has the gentlest pricing ladder in this category: a genuinely free single-user tier, two mid plans that meter canvases rather than people, and an enterprise tier carrying a SOC 2 report, SAML SSO and custom legal terms. The table below has the figures and the date we checked them. Beyond the ladder, Pastel has years of production use behind it. Writhink does not, and that is a fair thing to weigh.

Pastel is not standing still on AI either. Their homepage advertises an MCP server that lets Claude, Cursor and ChatGPT act on Pastel feedback. When we checked on 2026-09-01 we could not reach a public documentation page for it, so ask them about scope, plan gating and beta status — but treat the capability as real. Guests need no login and can comment and reply, which is a deliberate permission ceiling rather than an oversight.

Published plans and what they cap

	Writhink	Pastel
Free	Everything unlocked during the open beta, no card	$0 plan: 1 user, 1 active canvas
Paid entry	Announced, not purchasable yet	Pro $35/mo, or $29/mo billed annually
Team tier	Not applicable during the beta	Team $119/mo, or $99/mo annually, from 5 users, +$24 per extra user
Projects	Unlocked during the beta	1 canvas free, 3 on Pro, unlimited on Team
Client access	No account, display name only	No login for guests; guests comment and reply
Comments into one AI prompt	Yes, built in	Not published as a feature
MCP server	Yes: 7 tools, OAuth 2.1, every account	Advertised on their homepage; no public docs page we could load
PM integrations	None at any level	Trello, Asana, Jira, ClickUp, Monday, Zapier on Team and above
Enterprise controls	None	SOC 2 report and SAML SSO on Enterprise ($450/mo)

Competitor details checked on 2026-09-01. Pricing and features change — check their site before deciding.

What the AI layer does to a comment

This is the part with no equivalent we could find in Pastel's published feature set. A worked example.

"The header feels cramped on my phone" arrives with the page URL, the element it was pinned to, the viewport width, the device type and a screenshot of the spot. The prompt item names which header, on which page, at which breakpoint, so the AI is not guessing. What Writhink does not record is the operating system, the browser or the handset model — device type means desktop, tablet or mobile, and nothing finer.
Three people complaining about the same pricing table become one item, not three tickets that produce three conflicting edits.
Items are grouped by page and by element and given a priority, so work happens in an order that makes sense rather than in the order people happened to comment.
"Make it pop" is not turned into a design decision. It is flagged "(unclear — ask the client)" and the prompt asks the AI to draft the question you send back.
The output is plain text. Paste it into Claude, Cursor or ChatGPT, or hand it to a junior developer. Nothing about it requires you to keep using Writhink.

Wiring an AI agent to your feedback

Pastel advertises an MCP server too, so the connection itself is not the differentiator — what differs is the shape of what the agent reads. Here is Writhink's side documented end to end so you can compare like for like.

Step 1
Add the server
In Claude Code, run: claude mcp add --transport http writhink https://mcp.writhink.com/mcp. Any MCP-compatible client works — Claude Desktop and Cursor included.
Step 2
Sign in as yourself
OAuth 2.1 opens in the browser and the agent authenticates as you — nothing to paste into a config file. Pastel advertises an MCP server but publishes no docs page we could load, so we cannot tell you how theirs is authorized; ours is written out on /visual-feedback-for-ai-agents.
Step 3
Ask for the feedback, and answer it
Ask for the open feedback on a project and it comes back comment by comment, each with its pin context and its screenshot, already rewritten into implementation language rather than raw client prose. From the same session the agent can answer the commenter in their own thread and move an item along the four statuses, which is the half a paste buffer cannot do.
Step 4
Know the limit
The agent reads one active organization at a time, so switch first if you run several. Against Pastel's tiering, the thing worth noting is what is not metered here: MCP access is on every account, not held behind a plan, and there is no canvas count for a project to spend.

Pick the one that matches your bottleneck

Writhink fits when

The site is built or maintained with an AI assistant, and the slow part is turning feedback into changes rather than getting approval.
You run several client sites at once and do not want to think about canvas counts.
You want an agent to read the feedback with your own permissions and reply to the client from your editor.
What the round has to produce at the end is a shipped change, not a signature: four statuses, a public reply thread and an export are all the ceremony you want.

Pastel fits when

Approvals are the job. Deadlines, reminders, pause commenting and formal sign-off are a workflow there, and Writhink has no equivalent.
You want to buy today at a published price rather than start on beta terms.
You need SOC 2 or SAML SSO to get past a security review.
Your feedback has to reach Jira, Asana, Trello, ClickUp or Monday. Pastel gates those to their team tier and above; Writhink has no integrations at all.
You want a tool with years of production use behind it. Writhink launched recently and has no such record.

What Writhink does not do that Pastel does

There is no approvals machine. Writhink has four statuses — open, in progress, in review, resolved — public replies to the client, exports and email digests. That is a lighter mechanism than deadlines and reminders, and if a client's silence is your actual problem it will not fix it.

There are no project management integrations at any tier, because there are no integrations at all. Feedback leaves as the generated prompt — copied or downloaded as a .md — or through the MCP server, and that is the entire list. If your studio's process depends on a card appearing in Jira the moment a client complains, that gap is the reason to stay where you are.

Before you count on it

Writhink is in open beta: everything described here is available and free, no credit card. Paid plans are announced but not purchasable yet. The one limit that applies today is five AI prompt generations a month per organization.

FAQ

Questions people actually ask

Does Pastel have an MCP server?: Yes, based on their own homepage, which advertises MCP for Claude, Cursor and ChatGPT. We could not load a first-party documentation page for it on 2026-09-01, so the scope, the tool list and any plan gating are unverified. If an agent reading your feedback is central to your decision, ask them directly rather than trusting a comparison page, this one included.
So is Writhink's MCP server a reason to switch?: On its own, no. Having an MCP server has stopped being unusual in this category. The difference worth weighing is what travels through it: at Writhink the agent reads client comments that already carry the pin, the element, the page and the breakpoint, merged and prioritized into implementation language. If your feedback already arrives as structured tickets, that rewriting step buys you much less.
Which is cheaper for an agency with a dozen client sites?: Writhink is free during the beta with no project cap, so today it is cheaper. On Pastel, canvases are the metered resource — a dozen live sites pushes you to their team tier, and the table above carries the prices and the date we checked them. The caveat cuts the other way too: Writhink's beta terms will change and Pastel's price is published.
What can a client do in Writhink without an account?: Pin comments on the exact element, attach up to five files of 10 MB each, reply in a public thread, and edit or delete their own comments. They give a display name and nothing else — no email, no verification. Pastel's guests also need no login but are limited to comments and replies.
Does Writhink do approvals or feedback deadlines?: No. There is no deadline, no reminder schedule, no pause-commenting switch and no formal approval step. You get four statuses, public replies, exports and email digests. If sign-off ceremony is what you are buying, Pastel is built for it and Writhink is not.
Can I use both?: Yes, and some studios will want to. Run Pastel for the approval round if that is where your process lives, and put a Writhink review link or widget on the build so the implementation pass has a prompt behind it. They meter different things and neither blocks the other.

Start

Send one link. Get feedback you can build from.

Your clients comment right on the page — no account, no screenshots, no voice notes. Writhink sorts the comments and writes the prompt for your AI.