Agent guides (16)
Connect Cline to Ishara
Connect Cline to Ishara’s MCP server from its CLI or settings file, using the Streamable HTTP transport and your token.
- Server
https://useishara.com/mcp- Where it goes
cline mcp add, or~/.cline/data/settings/cline_mcp_settings.json- Transport
- Streamable HTTP, built in
- Authentication
- A bearer token in the
Authorizationheader - Time
- About 2 minutes
Steps
In Ishara, open Agents, name a token under New token (for example “Cline on my laptop”) and click Create token. Copy it now: it won’t be shown again.
Add Ishara to Cline, with your token in place of
ishara_…:cline mcp add ishara https://useishara.com/mcp --transport http \ --header "Authorization: Bearer ishara_…" --yes
{ "mcpServers": { "ishara": { "type": "streamableHttp", "url": "https://useishara.com/mcp", "headers": { "Authorization": "Bearer ishara_…" }, "disabled": false, "autoApprove": [] } } }From the Cline panel: MCP Servers → Configure → Configure MCP Servers.
In the Cline panel, open MCP Servers: Ishara is listed with its tools. Try one tool call.
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
- Set
"type": "streamableHttp": without it, Cline uses the older SSE transport. - Cline’s MCP servers apply to every project; there’s no per-project file.
- Cline doesn’t read environment variables in headers, so the token is stored as written.
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.