github-assistant-mcp
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., "@github-assistant-mcpwhat files are in my workspace?"
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.
GitHub Assistant MCP
A small, self-contained Model Context Protocol (MCP) server that exposes five read-focused tools to an AI coding assistant (e.g. OpenCode). It lets the assistant inspect a local workspace and pull a public GitHub profile over a clean, sandboxed stdio transport.
"A simple GitHub MCP server for OpenCode."
Table of Contents
Related MCP server: chatgpt-codex-local-mcp
Overview
The server is a local MCP server started by OpenCode as a child process. It speaks the MCP protocol over stdio (stdin/stdout) and registers five tools. The assistant calls those tools; the server performs the work (filesystem reads, a git diff, or a GitHub API call) and returns structured text results.
Everything that touches the filesystem is confined to a single WORKSPACE_ROOT directory, so the assistant can never read or escape outside the project folder.
How It Works (Architecture)
┌─────────────────────────┐ stdio (MCP/JSON-RPC) ┌──────────────────────────────┐
│ │ ───────────────────────────────▶ │ github-assistant (this) │
│ OpenCode / AI │ tool call: get_github_profile │ │
│ Assistant │ │ ┌────────────────────────┐ │
│ │ ◀─────────────────────────────── │ │ McpServer │ │
│ - sees 5 tools │ result (JSON text) │ │ (server.ts) │ │
│ - calls them │ │ └───────────┬────────────┘ │
│ - sandbox enforced │ │ │ registerTools │
└─────────────────────────┘ └──────────────┼──────────────┘
▼
┌────────────────────────────────┐
│ tools.ts (5 tool handlers) │
└───┬──────┬──────┬──────┬─────┬──┘
┌───────────────┘ │ │ │ │
▼ ▼ ▼ ▼ ▼
┌────────────┐ ┌────────────┐ ┌─────────┐ ┌────────────┐
│ github.ts │ │ workspace.ts│ │ git.ts │ │ paths.ts │
│ GitHub API │ │ list/read/ │ │ git diff│ │ resolve │
│ (fetch) │ │ search │ │ │ │ sandbox │
└─────┬──────┘ └─────┬──────┘ └────┬────┘ └─────┬──────┘
│ │ │ │
▼ ▼ ▼ ▼
api.github.com WORKSPACE_ROOT/* git CLI config.ts
(files only) (cwd=root) WORKSPACE_ROOTData flow for a single tool call:
Assistant ──JSON-RPC request──▶ McpServer
│
▼
tool handler (tools.ts)
│ validates args with zod
▼
business logic (github / workspace / git / paths)
│ resolveWorkspacePath() enforces sandbox
▼
result helper (result.ts) → { content: [{ type:"text", text }] }
│
▼
Assistant ◀──JSON-RPC response── McpServerTransport & Lifecycle
Type:
local— OpenCode launches the server as a child process.Transport:
stdioviaserveStdio()from@modelcontextprotocol/server/stdio.Startup sequence:
node dist/server.jsis executed (declared inopencode.json) withcwd = ".".createServer()builds anMcpServernamedgithub-assistant(v1.0.0).registerTools(server)wires up the five tools.serveStdio(createServer)begins reading JSON-RPC messages from stdin and writing results to stdout.
Shutdown: OpenCode terminates the process when the session ends.
Because the process inherits OpenCode's working directory, WORKSPACE_ROOT resolves to the project directory (path.resolve(process.cwd())).
Tools Reference
All tools are registered in src/tools.ts and return MCP text results (JSON or plain text).
1. get_github_profile
Fetches the public GitHub profile of the hardcoded user (imshashwatsingh).
Inputs: none
Backend:
fetch()tohttps://api.github.com/users/imshashwatsinghwithAccept: application/vnd.github+jsonand aUser-Agentheader.Returns: username, name, company, location, bio, public repos/gists, followers, following, profile URL, created/updated timestamps.
File:
src/github.ts
2. list_files
Lists files under a workspace directory up to a depth.
Inputs:
path(default"."),maxDepth(0–10, default 3)Backend: recursive
collectFiles()insrc/workspace.ts— skips symlinks (no loops) and ignores configured directories (node_modules,.git,dist,.next,coverage,.cache). Capped atMAX_RESULTS(500).Returns: workspace root, file count, and relative file paths.
File:
src/workspace.ts
3. read_file
Reads a UTF-8 text file with optional line range.
Inputs:
path(required),startLine(optional),endLine(optional)Backend:
readWorkspaceFile()— enforces sandbox, rejects non-files, refuses files larger thanMAX_FILE_SIZE(1 MB), and refuses binary extensions. Returns numbered lines.Returns: file content with
line: textprefixes.File:
src/workspace.ts
4. search_context
Keyword search across the workspace with surrounding context.
Inputs:
query(required),path(default"."),maxResults(1–100, default 50),contextLines(0–10, default 2)Backend:
searchContext()collects files, filters text-only and size-bounded files, then scans each line (case-insensitive) and capturescontextLinesabove/below every match.Returns: query, search path, match count, and matches with file/line/context.
File:
src/workspace.ts
5. summarize_diff
Inspects the current Git diff and returns a structured summary.
Inputs:
staged(defaultfalse),base(optional git ref),path(optional file/dir),maxDiffChars(1000–200000, default 50000)Backend:
summarizeDiff()runsgit diff --no-ext-diff --unified=3(with--cached/ base ref / path filters) fromWORKSPACE_ROOT. Stats are parsed from the unified diff itself (no secondgitcall). Diff is truncated if it exceedsmaxDiffChars.Returns: files changed, insertions, deletions, per-file stats, and the raw diff — or
{ empty: true }when there are no changes.File:
src/git.ts
Security Model
The server is intentionally read-only and sandboxed:
Concern | Protection |
Path traversal ( |
|
Binary file reads |
|
Oversized files |
|
Symlink loops |
|
Directory blow-up | Listing/searching capped at |
Write / delete / exec | None. The server has no write, delete, or arbitrary shell-exec tools. The only spawned process is |
Network | Only one outbound call: the read-only GitHub public API for a fixed user. |
The sandbox boundary lives entirely in
paths.ts. Any new tool that touches the filesystem must route paths throughresolveWorkspacePath().
Project Walkthrough
Entry point —
src/server.tscreateServer()instantiatesMcpServerand callsregisterTools().serveStdio()bridges it to stdin/stdout.Tool registration —
src/tools.tsFiveserver.registerTool(...)calls. Each declares a description, a zod-validatedinputSchema, and an async handler. Handlers delegate to the modules below and wrap output withresult.tshelpers.Configuration —
src/config.tsCentral constants:WORKSPACE_ROOT(resolved fromprocess.cwd()), size/result limits, the GitHub username/URL, and ignore/binary sets.Path safety —
src/paths.tsresolveWorkspacePath()is the sandbox gate.toWorkspaceRelative()turns absolute paths back into workspace-relative strings for display.isProbablyTextFile()classifies files by extension.Workspace I/O —
src/workspace.tscollectFiles()(recursive listing),readWorkspaceFile()(safe read), andsearchContext()(keyword scan). All go throughresolveWorkspacePath().GitHub —
src/github.tsfetchGitHubProfile()calls the public API and maps the rawGitHubUserto the friendlierGitHubProfileshape.Git —
src/git.tssummarizeDiff()builds and runs thegit diffcommand;parseDiffStats()derives per-file insert/delete counts straight from the diff text.Results —
src/result.tsSmall helpers (textResult,errorResult,errorWithContext) standardize the MCPcontentenvelope and error flagging.
Configuration
opencode.json (project root) declares the server:
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"github-assistant": {
"type": "local",
"command": ["node", "dist/server.js"],
"cwd": ".",
"enabled": true
}
}
}Inside the server, behavior is tuned via constants in src/config.ts:
Constant | Default | Meaning |
|
| Sandbox root (project dir) |
|
| Max readable file size |
|
| Max files from list/search |
|
| Profile target |
|
| Skipped while walking |
|
| Treated as non-text |
Building & Running
# install dependencies
npm install
# compile TypeScript -> dist/
npm run build
# start the server (used by opencode.json)
npm start
# run directly from source (no build step)
npm run dev
# the workspace must be a git repo for summarize_diff to work
git initOpenCode picks up the server automatically from opencode.json once built (dist/server.js).
File Structure
github_assistant_mcp/
├── opencode.json # MCP server declaration for OpenCode
├── package.json # scripts + dependencies
├── tsconfig.json # TypeScript config
├── src/
│ ├── server.ts # Entry point: create + serve McpServer
│ ├── tools.ts # Registers the 5 tools + handlers
│ ├── config.ts # Constants, limits, GitHub target
│ ├── paths.ts # Sandbox path resolution + helpers
│ ├── workspace.ts # list / read / search filesystem
│ ├── github.ts # GitHub profile fetch
│ ├── git.ts # git diff summary + stat parsing
│ └── result.ts # MCP result/error helpers
└── dist/ # Compiled output (npm run build)Limitations
get_github_profiletargets a single hardcoded user; it is not parameterized.summarize_diffreports working-tree changes only — untracked files are not shown bygit diff.Filesystem tools are confined to
WORKSPACE_ROOT; there is no cross-project access.All tools are read-only by design — no edits, deletions, or shell execution.
No authentication: the GitHub call uses the unauthenticated public API (rate-limited to 60 req/hr per IP).
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
- AlicenseNot gradedqualityCmaintenanceA read-only MCP server for AI coding agents to inspect repositories, audit code quality, route engineering skills, and plan safe issue/PR workflows.1MIT
- FlicenseAqualityCmaintenanceA secure MCP server that exposes local repository context to ChatGPT/Codex with read-only access, path validation, and no generic shell.17
- AlicenseNot gradedqualityAmaintenanceA read-only MCP server that provides AI agents with live, structured workspace awareness, including project listing, git status, and budgeted context packing, minimizing token usage.62MIT
- FlicenseBqualityCmaintenanceA read-only MCP server that exposes a local code workspace to AI clients via stdio, providing file browsing and text search capabilities with path safety rules.1
Related MCP Connectors
An MCP server that gives your AI access to the source code and docs of all public github repos
Agent-native MCP server over the public saagarpatel.dev corpus. Read-only, stateless.
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
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/imshashwatsingh/github-assitant-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server