Does ruttl have an MCP server?

We could not find one. On 2026-09-01 we checked their own integrations page, which lists Zapier, Google Calendar, Jira, Trello, ClickUp, Slack, Gmail, Mailchimp and Asana as live, with Figma, Zendesk, Monday and others as coming soon — no MCP, Claude Code, Cursor or Windsurf anywhere on it. At least one third-party listicle claims otherwise; their own site does not, so ask them if it matters to your decision.

Is an MCP server a reason to pick Writhink?

By itself, no. Several tools in this comparison already ship one, so the connection is not the rare part any more. What is worth comparing is what travels through it: Writhink's server hands an agent client comments that already carry the pin, the element, the page and the breakpoint, merged and rewritten into implementation language. Ask any vendor what the payload contains rather than whether the server exists.

Can Writhink edit CSS on the page like ruttl does?

No. Writhink collects comments and context and then writes the instruction; it never changes the page. If your reviewers want to nudge a value and see it live, that is ruttl's feature and it is a good one.

Writhink is free right now because it is in open beta, with no card and no comment cap. ruttl's free plan carries a hard comment cap and its paid tier is priced per user with no stated billing period, so verify that before committing — the table above has the figures and the date we checked them. Compare on fit as well: Writhink's beta pricing will change and ruttl's is public today.

Does either work on a native mobile app?

ruttl does. Writhink does not — it is browser-only, covering live websites and web apps, PDFs and image sets, with a Chrome extension for pages a proxy cannot reach. There is no Writhink mobile app and no native desktop app.

My clients will not sign up for anything. Does that decide it?

No, because neither tool requires it. ruttl gives unlimited guests on every tier including free. Writhink asks a guest for a display name only, and a token stored in their browser lets them edit or delete their own comments and reply in a public thread. Decide on the AI layer, the integrations and the pricing instead.

Comparison

Writhink vs ruttl: exact CSS values or an instruction your AI can run

ruttl's trick is that a reviewer edits CSS values live on the page and hands the developer exact numbers instead of adjectives. Writhink attacks the same round trip from the other end: comments stay comments, and an AI turns them into one implementation prompt with the pin, the page and the screenshot attached. Which you want depends on who does the work after the review.

Start for free

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

What ruttl is good at

Real-time pixel-level editing is genuinely distinctive and nothing else in this comparison offers it. A reviewer changes a value on the real page and the developer receives a number rather than a description, which removes a whole round of back and forth when the person reviewing already knows what they want.

The surface coverage is the broadest here too: live websites, web apps, native mobile apps, PDFs, static images and video recordings, with plug-and-play installation for WordPress, Shopify and custom HTML or CSS. Live integrations include Jira, Trello, Slack, Asana, ClickUp and Zapier, so feedback can leave the tool and land where your team already works. Writhink has no platform plugins at all: on a Shopify store you either send the review link or paste the widget script into the theme, and /for/shopify walks through both on a real storefront.

Client access is the most permissive of any tool in this set: unlimited guests on every tier including the free one, with no signup. The free plan is a real plan rather than a demo, and the paid tier is priced per user with a generous admin-to-user ratio that scales more cheaply than a per-seat tracker; the table below has the figures and the date we checked them. One caveat before you commit: their pricing page shows no monthly-or-annual toggle and no annual figure, so confirm exactly what that rate commits you to.

Side by side

	Writhink	ruttl
Free plan	Everything unlocked during the open beta, no card	Basic: 5 users, 1 project, 5 pages, unlimited guests, 1GB storage, capped at 10 comments plus 10 private comments
Paid entry	Announced, not purchasable yet	Pro published at $18 per user per month; no monthly-or-annual toggle shown, so confirm on their page
Client access	No account, display name only	Unlimited guests on every tier, no signup
Live CSS editing on the page	No	Yes, real-time pixel-level edits
Comments into one AI prompt	Yes, built in	Not published
MCP for coding agents	Yes: 7 tools, OAuth 2.1, every account	None found on their integrations page when we checked
Other AI	Rewriting, merging, grouping and prioritizing comments	Comment sentiment analysis and performance recommendations; accessibility, SEO and code-efficiency checks listed as coming soon
Integrations	None	Jira, Trello, Slack, Asana, ClickUp, Zapier and more
Surfaces reviewed	Live sites and web apps, PDFs, image sets	Live sites, web apps, native mobile apps, PDFs, images, video

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

Where the free plans actually land

Both tools are free to start, in very different ways.

ruttl's Basic plan is a real plan: a handful of users, one project, unlimited guests, storage and integrations included. The catch is a hard comment cap that a single client review will use up — the table above has the exact limits and the date we checked them.
Writhink is free during the open beta, with no card and no comment cap. Comments, pins, screenshots, replies, exports and MCP access are not metered.
If a published, stable price you can commit to today is part of the decision, that is a point for ruttl.
Neither tool asks your client to create an account, so that is not a tiebreaker here.

Getting feedback onto a site you did not build

Three ways in, and the one you pick depends on what the page will let you do.

Step 1
A public URL: share the review link
The page loads through the Writhink proxy so comments can be pinned to real elements. Your client opens the link, gives a display name and starts pinning. No install, nothing to add to the site.
Step 2
Behind a login or on localhost: the Chrome extension
Version 1.5.0 is on the Chrome Web Store. It reaches what a proxy cannot: pages behind authentication, staging environments, a build running on your own machine. Chrome only — there is no Firefox, Safari or Edge version, which is a real limitation if your client lives in Safari.
Step 3
Always on: the embeddable widget
One script tag on your site or your client's, so feedback can be left in place at any time rather than only during a review round. It carries a Powered by Writhink badge.
Step 4
PDFs and image sets
Both are reviewed in the browser, page by page for PDFs, with the same pinning and threading — the least travelled corner of the product, so try it on something small first. ruttl reviews both surfaces as well, alongside video and native apps.

Two ways to remove the same round trip

Writhink fits when

An AI coding assistant does the implementation. A prompt is what it wants; exact CSS values still have to be applied by hand.
The comments come from clients who describe outcomes, not values. Nobody on that side is going to open a styling panel.
You want an agent in Claude Code or Cursor to read the feedback with your own permissions, set statuses and reply to the client.
You need to review a page behind a login or on staging and would rather use a Chrome extension than deploy anything.
You want no comment cap while you are evaluating.

ruttl fits when

A designer is doing the review and knows the exact value they want. Live pixel editing hands the developer numbers, and Writhink has nothing like it.
You review native mobile apps or video recordings. Writhink does neither.
The feedback has to reach Jira, Trello, Slack, Asana, ClickUp or Zapier. Writhink has no native integrations at all.
You want a per-user price you can commit to today rather than beta terms that will change.
You want an established, well-reviewed product with real integration coverage. Writhink is new and has neither.

If you are choosing today

The clean split: use a pixel editor when a human applies the change and the argument is about exact values, and use Writhink when an AI applies the change and the argument is about what the client meant. Those are different halves of the same problem and running both is reasonable — one for the design polish pass, one for the client round that ends in an implementation pass.

Writhink is the wrong choice outright for a few jobs, and it is worth naming them: a native mobile app, a video cut, a QA release that needs console logs and reproduction steps, or a procurement process that needs SOC 2 and SAML SSO. None of those are on the roadmap of this page, and pretending otherwise would cost you a week.

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 ruttl have an MCP server?: We could not find one. On 2026-09-01 we checked their own integrations page, which lists Zapier, Google Calendar, Jira, Trello, ClickUp, Slack, Gmail, Mailchimp and Asana as live, with Figma, Zendesk, Monday and others as coming soon — no MCP, Claude Code, Cursor or Windsurf anywhere on it. At least one third-party listicle claims otherwise; their own site does not, so ask them if it matters to your decision.
Is an MCP server a reason to pick Writhink?: By itself, no. Several tools in this comparison already ship one, so the connection is not the rare part any more. What is worth comparing is what travels through it: Writhink's server hands an agent client comments that already carry the pin, the element, the page and the breakpoint, merged and rewritten into implementation language. Ask any vendor what the payload contains rather than whether the server exists.
Can Writhink edit CSS on the page like ruttl does?: No. Writhink collects comments and context and then writes the instruction; it never changes the page. If your reviewers want to nudge a value and see it live, that is ruttl's feature and it is a good one.
Which is cheaper?: Writhink is free right now because it is in open beta, with no card and no comment cap. ruttl's free plan carries a hard comment cap and its paid tier is priced per user with no stated billing period, so verify that before committing — the table above has the figures and the date we checked them. Compare on fit as well: Writhink's beta pricing will change and ruttl's is public today.
Does either work on a native mobile app?: ruttl does. Writhink does not — it is browser-only, covering live websites and web apps, PDFs and image sets, with a Chrome extension for pages a proxy cannot reach. There is no Writhink mobile app and no native desktop app.
My clients will not sign up for anything. Does that decide it?: No, because neither tool requires it. ruttl gives unlimited guests on every tier including free. Writhink asks a guest for a display name only, and a token stored in their browser lets them edit or delete their own comments and reply in a public thread. Decide on the AI layer, the integrations and the pricing instead.

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.