IsharaBeta
Agent guides (16)

Connect any other MCP client to Ishara

Connect any MCP client that only speaks stdio, or can’t send request headers, to Ishara through the mcp-remote bridge.

Server
https://useishara.com/mcp
Where it goes
Your client’s MCP configuration (as a local command)
Transport
stdio, through mcp-remote
Authentication
A bearer token in the Authorization header
Time
About 3 minutes

Steps

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

  2. Add Ishara to any other MCP client, with your token in place of ishara_…:

    mcp.json
    {
      "mcpServers": {
        "ishara": {
          "command": "npx",
          "args": ["-y", "mcp-remote", "https://useishara.com/mcp", "--header", "Authorization:${AUTH_HEADER}", "--transport", "http-only"],
          "env": { "AUTH_HEADER": "Bearer ishara_…" }
        }
      }
    }

    Most clients take this shape. Needs Node.js 18 or later.

    Terminal (test)
    AUTH_HEADER="Bearer ishara_…" npx -y mcp-remote https://useishara.com/mcp \
      --header "Authorization:${AUTH_HEADER}" --transport http-only

    Runs the bridge by hand, to check the token works before you configure a client.

  3. Restart your client and check that Ishara’s tools are listed.

  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

  • If your client supports remote servers and custom headers, give it the URL and the Authorization header directly instead: one less moving part.
  • --transport http-only matches Ishara’s server: Streamable HTTP, with no SSE stream.
  • Authorization:${AUTH_HEADER} has no space after the colon on purpose: some clients split arguments on spaces.

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.