list-repositoriesLABSCO SUMMARY
GitHub work without the tab.
The everyday loop — find the repository, read the file, open the issue, raise the pull request — happens in one place, with what it is allowed to do decided by the token's scopes rather than by the tool.
What it is
A GitHub server written in TypeScript, sitting in a workspace alongside Workiva IGAM reporting scripts. It lists and searches repositories, reads files and directory listings, and covers issues and pull requests from listing through creation and updates.
What you get
- Repositories listed for a user or organization, searched across GitHub, and read in detail
- File contents and directory listings pulled out of a repository without cloning it
- Issues listed with filters, created with labels and assignees, and updated afterwards
- Issues and pull requests searched across GitHub
- Pull requests listed and created, drafts included
- User profiles read
Requirements
Node.js 16 or higher and a GitHub personal access token. The scopes decide what it can do: repo for private repositories and writes, public_repo for public ones, read:user and read:org for profile and organization data.
Setup effort
Build from source — git clone https://github.com/golwalak/workiva-igam.git
USE CASES
01
Filing an issue while the detail is still fresh
Find the repository it belongs to and open the issue with its labels and assignee attached, instead of writing it down to file later.
02
Reading code you have not cloned
Pull the file or the directory listing straight from the repository — enough to answer a question about someone else's project without checking it out.
03
Triaging what is open
List issues filtered by state, label or assignee, then update the ones whose title, state or ownership is wrong.
04
Opening a pull request from work already pushed
Check what is already open on the branch, then raise the pull request — as a draft if it is not ready for review.
05
Finding where something was already discussed
Search issues and pull requests across GitHub before opening a duplicate, and read up on whoever raised the original.
06
Taking stock of what an organization owns
List the repositories under a user or an org and read the ones that matter in detail, which is where an audit usually starts.
11 tools
Listed in project docs. Your client may show a different list.
get-repositorysearch-repositorieslist-issuescreate-issueupdate-issuelist-pull-requestscreate-pull-requestget-file-contentssearch-issuesget-userBEFORE YOU INSTALL
What to know first
Tools you get
11 tools named in the project's documentation.
Requires
- Node.js 16 or later
- GITHUB_TOKEN in your environment
INSTALLATION
Connect your client
You clone and build this one yourself.
Server setup
TERMINAL
git clone https://github.com/golwalak/workiva-igam.git
cd workiva-igam
npm install
npm run buildMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"github": {
"command": "node",
"args": [
"<YOUR_PATH_TO_WORKIVA_IGAM>/build/index.js"
],
"env": {
"GITHUB_TOKEN": "<YOUR_GITHUB_TOKEN>"
}
}
}
}VS Code
The project includes a .vscode/mcp.json configuration file. Update the GITHUB_TOKEN value and use the MCP extension for VS Code.
