IsharaBeta
Agent guides (16)

Connect Cursor to Ishara

Connect Cursor’s agent to Ishara’s MCP server with one entry in mcp.json, so it can apply your reviewers’ edits and reply to them.

Server
https://useishara.com/mcp
Where it goes
.cursor/mcp.json in your project, or ~/.cursor/mcp.json for every project
Transport
Streamable HTTP, built in
Authentication
A bearer token in the Authorization header
Time
About 2 minutes

Steps

  1. In Ishara, open Agents, name a token under New token (for example “Cursor on my laptop”) and click Create token. Copy it now: it won’t be shown again.

  2. Add Ishara to Cursor, with your token in place of ishara_…:

    ~/.cursor/mcp.json
    {
      "mcpServers": {
        "ishara": {
          "url": "https://useishara.com/mcp",
          "headers": { "Authorization": "Bearer ishara_…" }
        }
      }
    }

    For every project on this computer.

    .cursor/mcp.json
    {
      "mcpServers": {
        "ishara": {
          "url": "https://useishara.com/mcp",
          "headers": { "Authorization": "Bearer ${env:ISHARA_TOKEN}" }
        }
      }
    }

    For one project, safe to commit: Cursor fills in ${env:ISHARA_TOKEN} from your environment.

  3. Restart Cursor. Under Customize → MCPs, Ishara is listed and switched on, and its tools appear under Available Tools in the chat. If it fails, the logs are under Output → MCP Logs.

  4. Ask your agent: “Apply the open Ishara notes.” It lists them, applies each edit in your code, and marks each note done with a reply the reviewer sees on the site.

Good to know

  • Don’t add an auth block: that’s for servers that sign in with OAuth. The headers entry is all Ishara needs.
  • On Team and Enterprise plans, admins can limit MCP servers to an allowlist; ask yours to add Ishara’s address.
  • Cursor’s one-click install links are for its Marketplace, so a custom server like Ishara is added this way.

What your agent can do

ToolWhat it does
list_sitesThe sites (embeds) in this account, with how many notes are open on each and what agents may see there.
list_notesNotes 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_noteOne 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_photoThe 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_noteSet 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_notesEvery open note, grouped by page, as one Markdown document (a checklist to work through).

Reviewers are people outside your team, so their words reach the agent marked as untrusted data, never as instructions. On sites where anyone can leave a note, set the site to Accepted notes only: agents see a note only after a person moves it to In progress.