# 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

## Steps

1. In Ishara, open **Agents**, create a token under **New token** and copy it (it’s shown once).
2. Add Ishara to any other MCP client, with your token in place of `ishara_…`:

   mcp.json:

```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):

```sh
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.

Checked against the official docs on 2026-11-12: [mcp-remote](https://github.com/punkpeye/mcp-remote), [mcp-remote on npm](https://www.npmjs.com/package/mcp-remote).
