Does MarkUp.io have an MCP server or AI features?

Not that they publish. On 2026-09-01 we checked their pricing page, their homepage and their developer hub; the hub documents an embeddable SDK, a REST API and webhooks, and nothing AI-related. One warning: searching for "markup MCP" surfaces markup.ai, an unrelated content-governance company that does ship an MCP server. Different company, different product.

Is Writhink cheaper than MarkUp.io?

Today, yes, because Writhink is free during the beta. MarkUp.io publishes a single paid tier with no free plan and a trial that asks for a card; the table above carries the figure and the date we checked it. Writhink's beta terms will change, so compare on fit rather than on a number that will move on both sides.

Do my clients need an account with either tool?

No, with both. MarkUp.io lets reviewers join as guests without registering and has worked that way for years. Writhink asks a guest only for a display name; ownership of their comments is proven by a token in their browser, so they can edit or delete their own comments and reply in the thread with no signup.

Can I switch mid-project?

There is no import from MarkUp.io. What works is starting the next round in Writhink on the same URL while old markups stay where they are. Switching at a round boundary avoids asking a client to comment in two places at once.

What does the AI prompt actually look like?

Plain text you can paste anywhere. Comments are rewritten clearly, duplicates merged, items grouped by page and by element with the pin context and screenshot attached, and priorities set. Requests that stay ambiguous are flagged rather than invented, and the prompt closes by asking the AI to draft replies for them.

Comparison

Writhink vs MarkUp.io: the same share link, a different ending

MarkUp.io has been collecting pinned comments on websites, images, PDFs and video for years, and reviewers never have to register. Writhink does the website side of that job and then keeps going: it reads the comments, writes one implementation prompt for your AI coding assistant, and lets an agent read the feedback directly over MCP. Here is the side by side, including the parts where MarkUp.io is the better buy.

Start for free

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

What MarkUp.io is good at

Breadth is the real argument for MarkUp.io. It covers more than 30 file types, including live websites, images, PDFs and video, so the same tool handles the launch page and the thirty-second cut of the brand film. Nothing else in this comparison does video, Writhink included.

Guest reviewing has been their default for a long time. You paste a URL or upload a file, share the link, and the client comments on top of it. They can register as a team member if they want to, and nothing breaks if they don't. Your own team is not seat-counted on the paid plan either, so there is no arithmetic to do before you invite a colleague.

There is also a genuine developer surface: an embeddable commenting SDK, a documented REST API and webhooks, which means MarkUp.io can sit inside a product you sell. On Enterprise they publish what a procurement team asks for, including SOC 2 documentation, SAML SSO, a dedicated success manager and custom onboarding. Writhink has none of that and this page is not going to pretend otherwise. Those figures were checked on 2026-09-01 and pricing moves, so confirm on their page before you decide.

What Writhink adds

Writhink is narrower on content types and much younger. The reason to look at it is what happens after the comments land.

One prompt instead of a list. Writhink reads every comment on the project, rewrites the vague ones in plain language without inventing requests, merges duplicates, groups them by page and by element, sets priorities, and gives you a single prompt to paste into Claude, ChatGPT, Cursor or any AI coding assistant. Each item keeps its pin metadata and its screenshot.
Gaps stay gaps. Anything still ambiguous is flagged "(unclear — ask the client)" rather than guessed at, and the prompt ends by asking the AI to draft replies for those items so you can send them back.
An agent can read the feedback itself. Writhink runs a remote MCP server. Add it to Claude Code with: claude mcp add --transport http writhink https://mcp.writhink.com/mcp — then the agent can list your projects, pull feedback with its full context, change a status, reply to the client, create a project and set up the widget. Seven tools, OAuth 2.1, and it only ever sees what your account can see.
An MCP server is not a rare thing to have any more: other tools in this comparison ship one, and BugHerd and Marker.io both do. MarkUp.io is the exception, publishing neither AI features nor an MCP server as of our check. What is actually different at Writhink is the shape of the payload — client sentences with their pin context, already rewritten and prioritized before the agent reads them.
Three ways to collect. A share link that loads the site through the Writhink proxy, a Chrome extension for pages behind a login or on a staging URL that a proxy cannot reach, and an embeddable script widget for feedback in place at any time.

Side by side

	Writhink	MarkUp.io
Price today	Free during the open beta, no card	Pro $79/mo; Enterprise custom; no free plan
Starting out	Sign up and share a link	14-day trial, credit card required
Client needs an account	No, a display name only	No, guests comment without registering
Your own team	Not seat-counted during the beta	Unlimited users on the paid plan
AI prompt from the comments	Yes, built in	No AI features published
MCP server for coding agents	Yes, 7 tools, every account	None published
Content types	Live sites and web apps, PDFs, image sets	30+ types including video
Workspaces	Unlocked during the beta	1 workspace on Pro, unlimited on Enterprise
Enterprise controls	None: no SSO, no SOC 2	SAML SSO and SOC 2 documentation on Enterprise
API and webhooks	No public API; MCP instead	REST API, webhooks, embeddable SDK

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

How a round actually runs

Same starting point as a MarkUp, different ending.

Step 1
Share one link
Create the project and share the review link. If the page sits behind a login or only exists on staging, use the Chrome extension instead. If you want feedback available permanently, drop in the widget script. The widget carries a Powered by Writhink badge.
Step 2
Your client pins comments
They are asked for a display name and nothing else. Every pin stores the position, the element anchor, the page URL, the page index, the viewport size and the device type — desktop, tablet or mobile — plus an automatic screenshot of the spot. They can attach files, reply in a public thread, and edit or delete their own comments without an account.
Step 3
Generate the prompt
When the round is done, Writhink turns the whole thread into one implementation prompt: every open comment rewritten, duplicates merged, items grouped by page and by element, priorities set, pin context and screenshots still attached.
Step 4
Hand it to your AI, or let the agent fetch it
Paste the prompt into whatever you build with. Or skip the paste: connect the MCP server and ask Claude Code to read today's feedback and start on the high-priority items.
Step 5
Close the loop
Move each item through open, in progress, in review and resolved. Replies are public to the client, so the answer lands where they asked the question. Email digests keep the team informed and feedback can be exported.

Where each one wins

Writhink fits when

You build or maintain sites with an AI coding assistant and want your client's words to arrive as a workable instruction, not a list you re-type.
Your reviewers are clients who will not create an account and will not learn a tool.
You want an agent in Claude Code or Cursor to read the feedback without you copying anything across.
You are reviewing websites or web apps, plus the odd PDF or image set on a much newer part of the product — not the thirty-odd file types MarkUp.io spans.

MarkUp.io fits when

Video review is part of your week. MarkUp.io handles it in the same place as everything else; Writhink does not do video at all.
You need SOC 2 documentation, SAML SSO or a named success manager to get a tool approved.
You want commenting embedded inside your own product, or review driven by an API and webhooks. MarkUp.io publishes an SDK and a REST API; Writhink does not.
You have a large internal team and want a known price rather than a young product's beta terms.
Track record matters to you. Writhink is new and has none to point at; MarkUp.io has years of production use behind it.

What you give up with Writhink

Read this before you switch.

No native integrations. Not fewer, none: no Jira, Linear, Slack, Asana, GitHub, Webflow, Shopify, WordPress or Figma connector. That is about pushing data out, not about coverage — a merchant's storefront reviews perfectly well through the share link or the widget, and /for/shopify shows what that looks like on a store. Feedback leaves as the generated prompt (copy it, or download the .md) or through the MCP server.
No public API and no webhooks either. MCP is the only programmatic surface, and it is built for an agent rather than for your own backend.
No video review and no session replay.
The extension is Chrome only. There is no Firefox, Safari or Edge version, and no mobile or desktop app.
No SSO, no SOC 2, no uptime SLA and no guaranteed support response time.

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 MarkUp.io have an MCP server or AI features?: Not that they publish. On 2026-09-01 we checked their pricing page, their homepage and their developer hub; the hub documents an embeddable SDK, a REST API and webhooks, and nothing AI-related. One warning: searching for "markup MCP" surfaces markup.ai, an unrelated content-governance company that does ship an MCP server. Different company, different product.
Is Writhink cheaper than MarkUp.io?: Today, yes, because Writhink is free during the beta. MarkUp.io publishes a single paid tier with no free plan and a trial that asks for a card; the table above carries the figure and the date we checked it. Writhink's beta terms will change, so compare on fit rather than on a number that will move on both sides.
Do my clients need an account with either tool?: No, with both. MarkUp.io lets reviewers join as guests without registering and has worked that way for years. Writhink asks a guest only for a display name; ownership of their comments is proven by a token in their browser, so they can edit or delete their own comments and reply in the thread with no signup.
Can I switch mid-project?: There is no import from MarkUp.io. What works is starting the next round in Writhink on the same URL while old markups stay where they are. Switching at a round boundary avoids asking a client to comment in two places at once.
What does the AI prompt actually look like?: Plain text you can paste anywhere. Comments are rewritten clearly, duplicates merged, items grouped by page and by element with the pin context and screenshot attached, and priorities set. Requests that stay ambiguous are flagged rather than invented, and the prompt closes by asking the AI to draft replies for them.

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.