Agent guides (16)
Connect Claude (desktop and web) to Ishara
Add Ishara to the Claude apps as a custom connector with a request header, or through a local bridge, and work through notes in chat.
- Server
https://useishara.com/mcp- Where it goes
- Customize → Connectors in Claude
- Transport
- Streamable HTTP, from Anthropic’s servers
- Authentication
- A bearer token in the
Authorizationheader - Time
- About 3 minutes
Steps
In Ishara, open Agents, name a token under New token (for example “Claude desktop and web on my laptop”) and click Create token. Copy it now: it won’t be shown again.
Add Ishara to Claude (desktop and web), with your token in place of
ishara_…:Name Ishara MCP server URL https://useishara.com/mcp Authentication No sign-in Request header authorization = Bearer ishara_… (Required)
Claude sends the header exactly as typed, so include “Bearer ” before the token.
{ "mcpServers": { "ishara": { "command": "npx", "args": ["-y", "mcp-remote", "https://useishara.com/mcp", "--header", "Authorization:${AUTH_HEADER}", "--transport", "http-only"], "env": { "AUTH_HEADER": "Bearer ishara_…" } } } }Only if Request headers is missing: in Claude Desktop, Settings → Developer → Edit Config, then restart. Needs Node.js 18 or later;
mcp-remoteis a community bridge, not an Anthropic feature.In Claude, go to Customize → Connectors, choose Add, then Add custom connector. Enter the name and URL above and click Continue.
Under Authentication, choose No sign-in. Open Request headers, choose
authorization, enterBearerand your token, mark it Required, and click Add.In a chat, open + → Connectors and turn Ishara on. 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
- Request headers are in beta for a limited set of organisations. If you don’t see Request headers, use the bridge above, or set Ishara up in the desktop app’s Code tab the way you would in Claude Code.
- You can’t edit a connector’s header after adding it: to change the token, remove the connector and add it again.
- On the Free plan you can add one custom connector.
What your agent can do
| Tool | 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 | 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 | 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 | 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 | 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 | Every 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.