RepoMind Bridge
Uses GitHub issues as the task store for captured tasks, allowing the agent to list, retrieve, start, comment on, ask questions on, and complete the issues, including accessing raw input and context.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@RepoMind BridgeCheck for new voice-captured tasks and start the first one"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
RepoMind Bridge
An MCP server that hands your coding agent the tasks you dictated — in the words you actually said, not a tidied-up title.
You find a bug on your phone, away from the keyboard. You say it out loud. Later you open the repository and Claude Code, Cursor or Codex already knows what you asked for, picks it up, and closes it when the work is done.
phone (dictate) ──► RepoMind ──► GitHub issue ──► this bridge ──► your agentTasks travel as GitHub issues labelled repomind-task. There is no server to deploy and
nothing to pay for: GitHub is the postbox.
Install
git clone https://github.com/idanidev/repomind-bridge.git
cd repomind-bridge
npm install
npm run buildAuthentication
No token needs to be written into a config file. If you are already signed in with the GitHub CLI, the bridge uses those credentials:
gh auth loginOtherwise set GITHUB_TOKEN to a token with repo scope:
export GITHUB_TOKEN=...GITHUB_TOKEN wins when both are present. If GitHub rejects it, the bridge resolves it again and
retries once — an MCP server stays up for days, and gh rotates its token underneath it.
Point your agent at it
Claude Code — add to ~/.claude.json:
{
"mcpServers": {
"repomind": {
"command": "node",
"args": ["/absolute/path/to/repomind-bridge/dist/index.js"]
}
}
}Cursor — the same block in .cursor/mcp.json. Codex — in .codex/config.toml.
Related MCP server: Agentic MCP Server
Tools
Tool | What it does |
| Everything captured for this repository. Call it before asking what to work on. |
| One task in full, including |
| Marks it in progress — visible on the phone — and returns the full context. |
| Posts a note to the thread, which reaches the developer's phone. |
| Marks it blocked and asks one specific question. Do not wait for the answer. |
| Closes the issue. Attach a PR url if there is one. |
| The screenshot attached when the task was captured. |
rawInput is the specification
title is a cleaned-up label. rawInput is what the developer dictated. When the two seem to
disagree, rawInput wins — it is the only record of what they meant.
Screenshots never leave the machine
get_task_image reads the image from the RepoMind app's local database, not from GitHub.
Committing screenshots into the repository would grow it permanently, and in a private repo the image would not even render: GitHub does not authenticate image URLs on the reader's behalf. Making the repo public to fix that would publish bug screenshots, which routinely contain personal data.
So nothing is uploaded anywhere. The image is already on the machine, synced by iCloud; the bridge reads it and hands it over. It follows that this tool only works where the Mac app is installed.
Session briefing
src/brief.ts can run as a SessionStart hook so the agent opens already knowing what is waiting.
It stays silent when there is no token, no network, or no tasks — a hook that fails loudly on a
plane is worse than no hook.
Requires
The RepoMind iOS/macOS app to capture the tasks, and a GitHub account. Node 18+.
License
MIT
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- AlicenseBqualityFmaintenanceEnables LLMs to interact with GitHub issues by providing details as tasks, allowing for seamless integration and task management through GitHub's platform.11614MIT
- -licenseBqualityNot gradedmaintenanceEnables AI-driven orchestration of GitHub development workflows including automated issue analysis, code generation, code review, and PR creation through multiple specialized agents. Integrates with GitHub Actions to automate the complete development process from issue to pull request.7
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to manage GitHub repositories, branches, issues, pull requests, releases, and actions through natural language.1155MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to interact with GitHub via natural language, supporting repository management, issue tracking, file commits, and more.
Related MCP Connectors
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
Pull change requests from your Amendor board into your coding agent to build and open PRs.
One shared brain for your AI coding agents: team memory, agent Q&A, tasks, and file claims.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/idanidev/repomind-bridge'
If you have feedback or need assistance with the MCP directory API, please join our Discord server