AgentBridge MCP Server
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., "@AgentBridge MCP ServerCheck git status and diff, then request a commit for my repo"
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.
AgentBridge MCP Server
Bridges GitHub webhooks + an AI coding agent's git actions to a mobile app, via phone-issued approve/commit/push/pull commands.
Setup
npm install cp .env.example .env # then edit ALLOWED_REPO_ROOT to point at your repo's parent dir npm run build npm start
Related MCP server: github-mcp-server
Endpoints
POST /webhooks/github — point your GitHub repo webhook here (same secret as .env)
POST /action — phone app calls this on Approve/Reject tap: { actionId, decision }
GET /health — liveness check
ALL /mcp — MCP endpoint for the AI agent (Claude Code, etc.) to call tools: git_status, get_diff, request_commit, request_push, request_pull
WS /ws — phone app connects here to receive live action notifications
Important: ALLOWED_REPO_ROOT
The server refuses to run git commands outside this directory (path-traversal
guard, tested). Set it to the folder that CONTAINS your demo repo, and pass
the repo's folder name as repoPath in tool calls / webhook payloads.
Tested end-to-end (see conversation log)
Real git status/diff/commit/push/pull against a live repo
Path-escape rejection
GitHub webhook HMAC signature verification (forged + valid cases)
Full loop: MCP tool call -> phone WebSocket notification -> phone approves via /action -> real
git pushlands on the remote test test test3 AgentBridge live demo test - 19:21:08 AgentBridge live demo test - 19:22:40 test commit A - 19:29:41 test commit B - 19:30:52 test commit C - 19:32:19 test commit D - 20:10:24 test commit - 23:16:51 test commit - 01:13:38
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
- AlicenseBqualityAmaintenanceMCP server that exposes GitHub operations as tools for AI agents, enabling code search, issue management, and PR review.12MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI assistants to interact with GitHub issues, pull requests, and Actions workflows through MCP tools.
- AlicenseBqualityBmaintenanceA security-first MCP gateway that enables AI assistants to safely inspect and interact with GitHub repositories through a controlled, auditable tool layer with policy enforcement and human approval for mutations.27MIT
- AlicenseNot gradedqualityBmaintenanceMCP server that wraps the GitHub REST API into tools for repo queries, issue/PR management, code review, search, and authentication, letting coding agents operate GitHub directly in conversations.1MIT
Related MCP Connectors
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
A Model Context Protocol (MCP) application for automated GitHub PR analysis and issue management.…
Phone, SMS & email for AI agents — one remote MCP endpoint, OAuth login, zero install.
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/atharv51-creater/MCP-server-connecting-to-github-IQOO'
If you have feedback or need assistance with the MCP directory API, please join our Discord server