Resources · Claude connector

Claude dot. connectorWhat Claude can do in your dot. account.

The Claude dot. connector exposes 3 tools. 2 read your projects and feedback, 1 creates something in your account, 0 are undocumented. Here: how a review link is born from a chat, who can comment on it, and what Claude does not do with the notes.

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What changes when you need a second opinion

You just built a landing page or a prototype with Claude and want your client's reaction. Instead of exporting it, deploying it somewhere and gathering scattered notes by email, you ask Claude for a dot. link. Reviewers open it, click on the exact spot that bothers them and leave a comment pinned there, without creating an account.

Get a review link from the conversation. create_review_link turns a web page, a prototype or an HTML or JSX artifact into a shareable dot. page, and hands you two links: one for reviewers, one for your dashboard.

Find what you already shared. list_projects shows your dot. projects with their number of comments, grouped by workspace, personal or team.

Read the verdict without leaving Claude. get_feedback brings back the comments left on a project, so you can go through them with Claude and decide what to change next.

Now the edges. The connector does not apply feedback for you: Claude reads the comments, and any rework happens in the conversation, with you. It is meant for visual work, and the publisher tells Claude to skip it for plain writing, data analysis or backend logic. Anyone who has the link can comment, which is the point, but also the thing to keep in mind before you send it. And nothing runs on its own: no new comment wakes Claude up. The Integrations hub lists the rest of the family.

Vocabulary

The vocabulary in one minute

Five words you will meet while plugging dot. in.

Connector
The link you set up once between Claude and an account you already have, so Claude can use it while it answers you.
Tool
One named thing the connector lets Claude do. Claude picks what it needs on its own; the directory lists each tool by name.
Authorization
The sign-in screen of dot. itself, where you give Claude the access it will use afterwards. Given once per person, and revocable.
Approval
The confirmation Claude waits for before it finishes an action that changes your account, shown in the chat at that moment.
MCP
The open standard connectors rely on: it is what lets an assistant such as Claude talk to an outside service like dot.
Connect

Connect dot. to Claude in three steps

  1. 01

    Locate dot. in Claude

    Open Customize, then Connectors, and find dot. in the list. On a Team or Enterprise workspace, an Owner or Primary Owner enables the connector for the organization before members can each connect.

  2. 02

    Run the connection

    Click Connect on its row and sign in to dot. in the window that dot. opens. If the connection ever breaks, click Disconnect, then connect again from the same row.

  3. 03

    Check the authorization screen

    Read the authorization screen before you accept. It is dot.'s screen, not Claude's, and it defines what the access covers. You can take that access back later from your dot. account.

Tools

The 3 tools, sorted by what they do

dot. gives Claude 3 tools: 2 that read your account, 1 that change something in it.

Two that read, one that creates. Names stay as Claude shows them, in English.

  • 2 read
  • 1 write

What Claude reads (2)

2 tools

Two tools that look at your projects and comments without touching them.

list_projects

Shows the dot. projects you own, each with its count of comments, grouped by workspace. The publisher's description presents it as the way to find a project's identifier before adding a link to it or fetching its feedback.

When it helps
you shared five prototypes last month and no longer remember which one got reactions.

Sourcemcp.leaveadot.com · October 1, 2026 ↗

get_feedback

Pulls the comments reviewers left on one dot. project into the conversation, when you want to know what reviewers said or check for new feedback on something you shared.

When it helps
the design review closed yesterday and you want a quick read of what people flagged.

Sourcemcp.leaveadot.com · October 1, 2026 ↗

What Claude changes (1)

1 tool

One tool that adds a project page to your dot. account. No source describes a confirmation for it, so the general rule below applies.

Approvals

What Claude asks before it acts

By default, Claude stops and asks for your go-ahead before any action it takes on an account for you. That rule covers the one tool here that creates something.

On a Team or Enterprise workspace, owners decide whether members can let some actions run without being asked every time. They can also limit what a connector is allowed to do for the whole organization, for example keep reading and close creation, and nobody overrides it from a personal account. Claude works with your dot. access and nothing more: a team workspace you are not part of stays out of reach. The official read-only versus write labels per tool sit only in a connected account's settings.

Plans

Which plans it is on

Out of the 819 sheets in the official directory, not one shows availability per plan. Connector by connector, that answer is published nowhere.

What is published is the general rule: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner enables a connector for the organization before each member can connect. For the up-to-date state of dot., open its sheet in the official directory from your own account.

Limits

Where this connector stops

A connector is not an automation. Claude calls these tools while it answers you: no comment, no new project and no deadline starts anything by itself.

The tool list is an observed floor, not a ceiling: an administrator could open actions that no public page shows. The partner badge in the directory is not a security audit, and Anthropic writes on every sheet that it neither picks the tools a publisher exposes nor guarantees they behave as described. Only dot. documents this connector, through its directory text and the tool list its own service publishes; Claude's help center has no page on it.

Need help

Need help connecting dot. to Claude?

A person reads every message.

FAQ

Claude dot. connector: common questions

01What can Claude do with the dot. connector?
Claude can turn what you build into a page people can comment on, then read their comments back to you. Its three tools create a review link from a web page, prototype or artifact, list your dot. projects with their comment counts by workspace, and fetch the feedback left on one project. Reviewers click directly on the spot they want to discuss and need no account to do it. You then go through the comments with Claude in the same conversation.
02Can Claude create or delete things in my dot. account?
It can create, and the sources describe nothing that deletes. The single creating tool publishes a new review page and returns a reviewer link and a dashboard link; if you belong to teams, Claude first asks which workspace should hold it. The two other tools only read projects and comments. No listed tool edits an existing project or removes feedback, and an administrator could still open actions that no public sheet lists.
03Does Claude ask before it creates a review link?
By default, Claude asks for confirmation before any action it takes on an account for you, and that is the rule that covers link creation. No source describes a confirmation specific to this tool. Do not confuse it with the workspace question: when you are in several teams, Claude asks where the link should go, which is a routing choice. On Team and Enterprise, owners decide whether members can let some actions through without being asked.
04Which Claude plans include dot.?
No official source publishes plan availability connector by connector, and none of the 819 directory sheets shows it. The general rule is that remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile, with an Owner or Primary Owner enabling them first on Team and Enterprise workspaces. To see the current state of dot. for your own account, open the connector's sheet in the official directory.
05Does Claude see every project in my dot. account?
Claude sees what your own dot. access shows, no more. Projects in your personal space and in the teams you belong to can come up; a team you are not part of stays closed. Keep in mind the other side of the coin: the review page itself is open to anyone holding the link. On Team and Enterprise Claude workspaces, an owner can also restrict or switch off the connector for everyone, and a member cannot undo it.
06Why does Claude not offer a dot. link for every answer?
Because the publisher tells it not to. The tool's own description presents the review link for a web page, a prototype, a UI or an HTML or JSX artifact, and says to skip it for non-visual work: plain writing, data analysis or backend logic. It also says to offer it once, naturally, and not to bring it up again if you passed on it. You can still ask for a link explicitly whenever you want one.
07Claude or an automation tool for dot. feedback?
They solve different problems, so pick by task. Claude works in a conversation: you ask for a link, share it, then come back and ask what reviewers said. It does not react by itself when a new comment lands. If you want each new comment forwarded somewhere automatically, that background job is what an automation tool does. For creating links and reading feedback on demand while you build, the connector covers that use.