A website feedback MCP server.

pinthread is a hosted MCP server for website feedback. Your coding agent reads the comments your team pins on your site, makes the change, and replies in the thread. It is included on every plan, including Free at $0 a month.

What your agent reads

Each thread names the exact place on the page. Your agent gets:

The page URL
The element’s selector and visible text
The comment position or selected area
Every reply, with its author

Page: /pricing
Target: #annual-plan-button
Element text: Choose plan

Maya: Make it clear this is billed annually.
Alex: Keep the monthly equivalent visible too.

01 · Create an agent token

Read: list and read threads and new activity.
Write: also reply, start, resolve, and reopen threads.

Each token belongs to one project. Tokens start with ptk_ and are shown once. They expire after 90 days by default, or up to 365 days. Store the token as PINTHREAD_TOKEN, never in your repository.

02 · Connect your client

The server URL is https://pinthread.dev/mcp. It uses streamable HTTP with a bearer token.

claude mcp add --transport http pinthread https://pinthread.dev/mcp \
  --header "Authorization: Bearer $PINTHREAD_TOKEN"

Run it in your project with PINTHREAD_TOKEN set to your agent token.

[mcp_servers.pinthread]
url = "https://pinthread.dev/mcp"
bearer_token_env_var = "PINTHREAD_TOKEN"

Add it to ~/.codex/config.toml. Codex reads the token from PINTHREAD_TOKEN.

{
  "mcpServers": {
    "pinthread": {
      "url": "https://pinthread.dev/mcp",
      "headers": { "Authorization": "Bearer ${env:PINTHREAD_TOKEN}" }
    }
  }
}

Save it as .cursor/mcp.json in your project.

Any MCP client that supports streamable HTTP works. Send JSON-RPC with POST to https://pinthread.dev/mcp and the header Authorization: Bearer YOUR_AGENT_TOKEN.

Tools

Read tools work with any token. Write tools need a write token.

Tool	Scope	What it does
`whoami`	Read	Shows the project, token name, and scope of this connection.
`list_threads`	Read	Lists threads. Filter by status (open, resolved, all), page, or update time.
`get_thread`	Read	Reads one thread with every comment, author, and reaction.
`get_page_context`	Read	Returns the open threads on one page with their anchors.
`list_events`	Read	Reads new threads and replies after a cursor, oldest first.
`reply_thread`	Write	Adds a reply as the agent.
`create_thread`	Write	Starts a thread on a page at a given anchor.
`resolve_thread`	Write	Marks a thread resolved.
`reopen_thread`	Write	Reopens a resolved thread.

React to new feedback

Call list_events with since: "latest" to start from now. Pass back the cursor it returns, and each call returns only new threads and replies. The agent workflow guide shows the whole loop from comment to fix.

Other feedback tools with MCP

Tool	Agent access	Free plan
pinthread	MCP server and agent tokens on every plan, including Free	$0 a month, with no trial that runs out. Up to 10 projects, 25 members per project, 10,000 comments per project, 100 MB of storage per project.
Marker.io	MCP server for all customers at no extra cost	No free plan. A 15-day free trial.
BugHerd	MCP server in beta, free for all BugHerd subscribers	No free plan. A 7-day free trial.
Userback	MCP connectors on paid plans	2 feedback projects. Feedback stays available for 7 days.
Huddlekit	MCP on paid plans	1 project, 3 team members, and 100 MB of storage
Ruttl	No MCP listed on the pricing page	1 project, 5 pages, and up to 5 users

Checked on 7 October 2026. Sources: Marker.io pricing, Marker.io MCP, BugHerd pricing, BugHerd MCP, Userback pricing, Huddlekit pricing, Ruttl pricing.

Read all alternatives, or see what the free plan includes.

Questions

Which agents can use the pinthread MCP server?

Any MCP client that supports streamable HTTP, including Claude Code, Cursor, and Codex. Clients without MCP can take the copied comments as a prompt.

Is the MCP server included in the Free plan?

Yes. Agent tokens and MCP access are included on every plan, including Free at $0 a month.

Can the agent see my other projects?

No. Each token belongs to one project, so the agent sees only that project's threads. A read token cannot reply to, start, resolve, or reopen threads.