Agent guides (16)
Connect the GitHub Copilot coding agent to Ishara
Let the GitHub Copilot coding agent read Ishara notes in a repository, apply the edits in a pull request and reply to reviewers.
- Server
https://useishara.com/mcp- Where it goes
- Repository Settings → Copilot → MCP servers on github.com
- Transport
- Streamable HTTP, built in
- Authentication
- A bearer token in the
Authorizationheader - Time
- About 4 minutes
Steps
In Ishara, open Agents, name a token under New token (for example “Copilot coding agent on my laptop”) and click Create token. Copy it now: it won’t be shown again.
Add Ishara to the GitHub Copilot coding agent, with your token in place of
ishara_…:{ "mcpServers": { "ishara": { "type": "http", "url": "https://useishara.com/mcp", "tools": ["*"], "headers": { "Authorization": "Bearer $COPILOT_MCP_ISHARA_TOKEN" } } } }Paste it under MCP configuration and click Save MCP configuration. The token comes from the secret below, never from this text.
In the same repository, go to Settings → Secrets and variables → Agents and add a repository secret named
COPILOT_MCP_ISHARA_TOKEN, with your token as its value.Assign an issue to Copilot, such as “Apply the open Ishara notes for this site and reply to each one.” When it opens a pull request, click View session and expand Start MCP Servers: Ishara’s tools are listed at the end of the log.
Good to know
- Secret names must start with
COPILOT_MCP_, and they live under Agents secrets, not Actions secrets. - The coding agent uses MCP tools on its own, without asking. On sites where anyone can leave a note, set the site to Accepted notes only so a person approves each note first.
- Copilot code review uses only tools marked read-only; in Ishara those are the tools that read notes.
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.