# Ishara: website feedback with suggesting mode > Ishara (إشارة, Arabic for “a sign; pointing at something”) is a website feedback tool with suggesting mode. One script tag lets your clients point at anything on a live website and rewrite the text in place, replace a photo, or report a problem. Each note arrives with its page, section, element path, screen size and language in a multi-site dashboard, and AI coding agents (Claude Code, Cursor, GitHub Copilot, Codex) read and resolve the notes over MCP, then reply to the reviewer on the site. Site: https://useishara.com · Arabic: https://useishara.com/ar · Docs: https://useishara.com/docs.md ## How it works 1. **Paste one line.** Add the script to your site, or the snippet for React, Next.js, Astro, Vue or WordPress. It loads after your page, draws inside its own Shadow DOM, and stays out of the way until someone opens it. 2. **Send the reviewer link.** Your client opens the site with their link and «Leave a note» appears, for them only. They point at a sentence and rewrite it, swap a photo from their phone, or say what’s broken. 3. **Your agent applies it.** Connect Claude Code, Cursor, GitHub Copilot or Codex with one token. The agent reads each note with its page, section, element and exact wording, makes the change, and replies. Your client sees «Done» on the same page. **Nobody describes where.** Every note arrives with the page, the section heading, the element’s path, the screen size and the language. No note ever starts with “on the second page, under the photo”. **Written in Arabic first.** Ishara is Arabic for pointing at something. It started on an Arabic library’s website, where the team left notes from their phones and an agent applied them. The widget speaks English, Arabic, Spanish, French, German and Turkish, follows your page’s language, and lays itself out right to left when your page does. **One token. Any agent.** Ishara is an MCP server (the Model Context Protocol, the open standard coding agents use to reach tools). Add it to Claude Code, Cursor, GitHub Copilot or Codex, and your agent can list what’s waiting, read a note in full, fetch the reviewer’s photo, and mark the note done with a reply. Strangers don’t drive your agent: Reviewer text reaches your agent marked as untrusted data, never as instructions. On public sites, show agents only the notes a person has accepted. ## Features - **Every site, one inbox:** Notes from all your sites land in one keyboard-first inbox: j and k to move, e to mark done. - **Replies they can see:** Your answer, or your agent’s, appears under «Your notes» in the widget, on the reviewer’s own device. - **Photos from the phone:** Reviewers replace an image straight from their camera roll. It’s shrunk in the browser before it travels. - **Copy as prompt:** No MCP? Copy any note as a ready-made prompt, or export a site’s open notes as Markdown. - **Out of your CSS:** The widget draws inside its own Shadow DOM and builds its icons node by node, so it runs under strict Content Security Policies. - **Allowed domains:** Each site key works only on the domains you list. Localhost is fine while you develop. ## Pricing - **Free** ($0, no card needed): 1 site, 100 notes a month, 250 MB of photos, a small “via Ishara” link in the widget. - **Pro** ($19/month, or $180/year): 5 sites, unlimited notes, 5 GB of photos, no “via Ishara” link. - **Studio** ($49/month, or $468/year): unlimited sites, unlimited notes, 25 GB of photos, no “via Ishara” link. Every plan includes unlimited reviewers (no seats), the widget in English, Arabic, Spanish, French, German and Turkish, the MCP server, the REST API, Markdown export and email notifications. Prices are in US dollars; Creem, the merchant of record, adds VAT or sales tax where it applies. Details: https://useishara.com/pricing ## Frequently asked questions ### Will it slow my site down? The widget is one file of about 34 KB gzipped. It loads with defer, waits until your page is ready, and does nothing until someone opens it. ### Who can leave notes? By default, only people who opened your reviewer link. Switch a site to «everyone» to collect notes from every visitor. ### Is it safe to let an agent read strangers’ notes? Reviewer text reaches your agent labelled as untrusted data, and a site can show agents only the notes you’ve accepted. Your agent still works in your repository, under your review. ### Which agents does it work with? Any MCP client, including Claude Code, Cursor, GitHub Copilot in VS Code, Codex and Windsurf. There’s also a REST API and a Markdown export. ### Does it work with my stack? It’s one script tag, so it works with plain HTML, React, Next.js, Astro, Vue, Svelte, WordPress, Webflow and Framer. ### Where is the data kept? On Cloudflare: Workers for the service, a D1 database for notes and R2 for photos. Photos are shrunk in the reviewer’s browser before they travel. ### Do reviewers need an account or a seat? No. Reviewers never sign up and never count: every plan includes unlimited reviewers. ### What happens when the Free plan's notes run out? We warn you at 80%. At 100 notes, the widget tells reviewers the site isn't taking new notes until the 1st of the month; their earlier notes and your replies stay visible. Upgrading lifts the limit at once. ### Can I cancel anytime? Yes, from the billing portal. Your plan stays until the end of the period you paid for, then becomes Free. Nothing is deleted. ### Do you offer refunds? Yes: a 30-day money-back guarantee on the first payment of a plan. Just write to us. ### Who handles payments and tax? Creem, our merchant of record. It processes your card, adds VAT or sales tax where it applies, and sends your invoices. ### Will my price go up? Prices may change while Ishara is in beta. If yours does, we’ll email you at least 30 days before; the new price starts at your next renewal after that, and you can cancel before then. ### Is the agent integration in every plan? Yes. The MCP server, the REST API, the Markdown export and copy-as-prompt are on every plan, including Free. ### Nonprofit or education project? Write to us. We'd like to help community projects review their sites. ## Developer docs Ishara puts suggesting mode on any website. Reviewers leave a quick note, or point at what’s wrong and rewrite it in place; each note arrives with a screenshot of what they saw and its page, section, element path, screen and language. You answer from the dashboard, or your coding agent does over MCP. ### Install the widget Create a site in the dashboard, then add one line to every page you want notes on, before ``: ```html ``` The script is one file of about 34 KB gzipped. It waits for the page, asks for the site’s settings, and draws inside its own Shadow DOM, so your styles never reach it and its styles never reach your page. #### Frameworks - **Next.js (App Router):** in `app/layout.tsx`, ``. - **Vue · Nuxt:** add the script to `app.head.script` in `nuxt.config.ts`, or to `index.html` in a Vite app. - **WordPress · Webflow · Framer:** paste the line into the site-wide footer code (a “custom code” or “footer scripts” setting, or a header/footer plugin). The site’s **allowed domains** decide where its key works. `example.com` covers `www.example.com` and any port; `*.example.com` covers subdomains; `localhost` works while you develop. A page outside the list gets no widget, and the browser console says why. ### Options Attributes on the script tag override the site’s settings for that page. | Attribute | Values | Default | | --- | --- | --- | | `data-site` | The site’s public key, `pk_…` (required) | — | | `data-lang` | `auto`, `en`, `ar`, `es`, `fr`, `de`, `tr` | The site’s setting; `auto` reads `` | | `data-position` | `end` or `start` (bottom corner, by reading direction) | `end` | | `data-color` | A hex colour, e.g. `#c2255c` | The site’s colour | | `data-label` | The launcher’s text | “Leave a note” in the reviewer’s language | | `data-launcher` | `false` hides the floating button (open it from your own UI) | shown | | `data-first` | `quick` (a comment with a screenshot, pointing one tap away) or `pick` (point at the page first) | The site’s setting (`quick` for new sites) | | `data-screenshots` | `false` sends notes from this page without a screenshot | The site’s setting (on) | ### JavaScript API Once loaded, the widget exposes `window.Ishara`: ```js Ishara.open(); // what «Leave a note» does: the site's first view Ishara.note(); // a quick note: a comment on the page, with its screenshot Ishara.point(); // pointing: the reviewer picks a sentence, photo or section first Ishara.notes(); // the reviewer's own notes and the replies they got Ishara.close(); addEventListener("ishara:ready", (e) => console.log(e.detail)); // { lang, allowed } addEventListener("ishara:sent", (e) => console.log(e.detail)); // { id, number, kind, target, … } ``` ### Reviewers and access - **People with the reviewer link (default):** the widget appears only for people who opened the site once through its reviewer link, `https://your-site/?ishara=`. The widget remembers the key on that device and removes it from the address bar. Making a new link in the dashboard invalidates the old one. - **Everyone:** every visitor sees «Leave a note». Pair it with *Accepted notes only* for agents. Reviewers type their name once per device and never need an account. A random device token lets them see their own notes, with your status and reply; nobody else’s notes are ever shown to them. “Open on the page” in the dashboard opens the reviewer’s page with `#ishara=N-12:`, and the widget rings that element. ### Connect an agent (MCP) Ishara is a remote MCP server (Streamable HTTP, JSON responses, no session) at `https://useishara.com/mcp`, authorised with a bearer token. Create a token under *Agents* in the dashboard; each token reaches every site in your account and can be revoked there. Without a token the server answers only the handshake and the tool list; every tool call needs the token. ```sh ## Claude Code claude mcp add --transport http ishara https://useishara.com/mcp --header "Authorization: Bearer ishara_…" ## Clients that only speak stdio npx -y mcp-remote https://useishara.com/mcp --header "Authorization: Bearer ishara_…" ``` ```json { "mcpServers": { "ishara": { "url": "https://useishara.com/mcp", "headers": { "Authorization": "Bearer ishara_…" } } } } ``` **Safety.** Notes are written by people outside your team, so every reviewer-written field reaches the agent inside `` markers with an instruction to treat it as data, never as instructions. A site set to **Accepted notes only** hides new notes from agents until a person moves them to *In progress*. Your agent works in your repository, so review its changes as you would any other. ### MCP tools | Tool | Arguments | What it does | | --- | --- | --- | | `list_sites` | — | The sites (embeds) in this account, with how many notes are open on each and what agents may see there. | | `list_notes` | site?, status? (open · new · doing · done · wontdo · all), kind?, limit? (1–100) | Notes reviewers left on the live sites, newest first. Default: open notes (new and in progress) on every site. Each has an id for get_note and update_note, and a short ref like "N-12". | | `get_note` | id | One note in full: the page, the section heading, the CSS selector, the text before and after, the reviewer's words and its history. | | `get_note_photo` | id | The photo a reviewer attached (the replacement image, or one that shows the problem), as an image. With which: "screenshot", the screenshot of the page as the reviewer saw it, any element they picked ringed in gold (get_note says whether a note has one). | | `update_note` | id, status? (new · doing · done · wontdo), reply? | Set a note's status and/or reply. The reviewer sees both in the widget on their site. Use "doing" while working, "done" once the change is committed or deployed, "wontdo" with a reason when it will not be applied. Write the reply in the reviewer's language. | | `export_notes` | site? | Every open note, grouped by page, as one Markdown document (a checklist to work through). | The server’s instructions ask agents to apply text edits by finding the original wording in source, content and translation files, to save replacement photos into the project before referencing them, and to close each note with `update_note` and a reply in the reviewer’s language. ### REST API The same token works over plain HTTP (JSON; at most 300 requests a minute per token). | Request | Returns | | --- | --- | | `GET /api/v1/sites` | Your sites, open counts, agent scope | | `GET /api/v1/notes?site=&status=open&kind=&limit=50` | Notes, newest first (`site` is an id, public key or name) | | `GET /api/v1/notes/:id` | One note with its history | | `PATCH /api/v1/notes/:id` | `{"status": "done", "reply": "…"}`: the reviewer sees both | | `GET /api/v1/notes/:id/photo` | The attached photo (JPEG, PNG or WebP) | | `GET /api/v1/notes.md?site=` | Open notes as Markdown, grouped by page | ### What a note captures Only what the reviewer chose to send, plus where it was: - the kind (comment, edit text, replace image, layout, something wrong), the reviewer’s words, their name, and an optional photo (shrunk to at most 2000 px in the browser; JPEG, PNG or WebP up to 1.8 MB); - a screenshot of the visible page as they saw it, any element they picked ringed, unless the site turns screenshots off or they remove it before sending. It is drawn in their browser from the page itself: typed form values, password and payment fields, anything marked `data-ishara-mask` or `data-ishara-ignore`, editable text and other sites’ frames stay blank, and the widget is never in it; - the page address without its fragment, its title and language, the screen size and the browser’s user agent; - the chosen element: what it is, its section heading, a CSS path, its static text (or the image’s address and description). Typed form values (``, `