IsharaBeta
Agent guides (16)

Connect Claude Code to Ishara

Connect Claude Code to Ishara’s MCP server with one command, so it can read your reviewers’ notes, apply the edits and reply.

Server
https://useishara.com/mcp
Where it goes
claude mcp add, or .mcp.json in your 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 “Claude Code on my laptop”) and click Create token. Copy it now: it won’t be shown again.

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

    Terminal
    claude mcp add --transport http ishara https://useishara.com/mcp \
      --header "Authorization: Bearer ishara_…"

    Adds Ishara for this project only. Add --scope user for every project on this computer.

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

    Or share it with your team through git: this file reads the token from each person’s ISHARA_TOKEN environment variable.

  3. Start Claude Code and type /mcp: ishara should show ✔ Connected. From the shell, claude mcp list says the same.

  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

  • Claude Code reads .mcp.json when a session starts, so restart the session after editing the file by hand.
  • With an Authorization header set, Claude Code sends it and doesn’t try to sign in with OAuth.
  • Use a variable name like ISHARA_TOKEN: Claude Code deliberately reads some credential names, such as ANTHROPIC_API_KEY, as empty.

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.