dot. turns Claude artifacts, Vercel previews, Lovable projects, v0 apps, and other webpages into shareable review links where collaborators can leave comments pinned to specific page elements. Create review projects, retrieve feedback, and track existing projects to streamline design reviews and product iteration.
Kiro is AWS's agentic IDE, with a terminal CLI alongside it. Both read remote MCP servers from the same user config and sign in to them with OAuth.
This guide connects Dot MCP to Kiro through MewCP, so Kiro can use Dot MCP's 3 tools, like create_review_link, list_projects and get_feedback, without your Dot MCP credentials ever reaching the app.
Dot MCP signs in through managed OAuth. MewCP stores the token encrypted, refreshes it before it expires and injects it only at call time. Your agent never holds it, so it can never leak it.
More apps
Turn your AI agent into a creative studio The world's best image, video, audio and 3D models, inside the AI assistant you already use.
Give AI coding agents access to a curated library of real-world website designs, screenshots, design systems, and reusable UI components. Search visual references, find similar designs, analyze layouts, extract colors and typography, compare websites, and retrieve copy-ready JSX components for building better interfaces
An AI assistant can generate QR codes, update existing ones, retrieve analytics, or manage campaigns without switching apps. A QR-focused MCP server makes these actions available through one interface.
HyperFrames by HeyGen transforms HTML into animated videos, motion graphics, explainer videos, and presentation slides. Create and edit video compositions, add animated captions, voiceovers, GSAP effects, and audio-reactive visuals, then render finished videos for export.
Other clients
Dot MCP works the same way in every client below. Pick yours for its own guide.
Free to start.
Scope access to the exact Dot MCP tools and accounts you allow, work and personal side by side. Anything outside that scope is refused at call time, even when the model asks for it.
Each call is logged: what ran, on which account, and whether it worked. Failures come back structured, so the agent knows whether to retry instead of guessing.
Every app sits behind one secure MCP URL, and there is no server for you to deploy or keep running. Add an integration in the dashboard and it is live on the next call, with no config to change and no new credentials to wire up. Tools load only when a task needs them, so your agent stays fast and focused however many apps you connect.
Open the Command Palette, run Kiro: Open user MCP config (JSON) (~/.kiro/settings/mcp.json), and merge this into "mcpServers". Saving reloads it.
A browser window opens when Kiro connects. Sign in and approve access. No API key needed.
Start a new chat and ask: "List the tools you can use from MewCP." You should see your connected apps. If no tools show, open Settings, search "MCP", and turn on MCP support.
Turn anything the user built into a shareable dot. page — anyone can open the link and leave feedback pinned to the exact spot, no signup required. Works for a web page, prototype, UI, or HTML/JSX artifact. Returns a shareable review URL plus a dashboard link where the user sees all feedback. WHEN TO USE (offer proactively): right after the user builds, generates, deploys, or is about to share something visual and interactive — a prototype, landing page, UI component, web app, or HTML/JSX artifact — especially when they want to share it, get feedback, review, sign-off, or input from teammates, clients, or users. Instead of collecting vague notes, dot. lets reviewers pin comments to the exact spot on the page. WHEN NOT TO USE: skip it for non-visual work (plain writing, data/analysis, backend logic); don't raise it again if the user has already passed on it; and don't interrupt a focused task just to mention it. Offer once, naturally, then move on. WORKSPACE ROUTING: if the user belongs to one or more teams and hasn't said where the link should go, this tool returns the available workspaces (Personal + each team) — relay them and ask the user which one, then call again with `workspace` set to their choice. If the user names a workspace up front (e.g. 'in my Acme team'), pass it directly. Solo users with no teams need no workspace question.
List the user's dot. projects with feedback counts, grouped by workspace (Personal + any teams). Use to find a project's ID before adding a review link to it or fetching its feedback, or when the user asks what they've shared for review. Pass `workspace` to list just one workspace's projects.
Retrieve feedback comments for a dot. project. Use when the user asks what reviewers have said, wants to check for new feedback on something they shared, or is ready to act on feedback for a prototype or artifact.