Repo Context Mcp

by pablo-peek

340 downloads

Not rated

GitHub

About

Repo Context MCP provides programmatic access to repository contents for integrations and automation. It can list directories/files, read any file, return the README, perform TypeScript type analysis (via ts-morph), and search for OpenAPI/Swagger spec files. Supports local repo p

Details

Author: pablo-peek
Downloads: 340
Categories: Developer Tools, API, Knowledge Base

- Set active repository path via setRepoPath
- List files and folders with getFiles
- Read file contents using getFileContent
- Return root README.md with getReadme
- Analyze TypeScript types with analyzeFileTypes (simple) and analyzeFileTypesAdvanced (ts-morph)
- Fetch files from GitHub using getGithubFileContent (requires GITHUB_TOKEN)
- Search for OpenAPI/Swagger specs with getSwaggerSpec

Setting up with Highlight

This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:

Download and install Highlight from highlightai.com/download
Navigate to the plugins tab and select "Add Custom Plugin"
Configure the plugin with the settings below

Plugin Name Repo Context Mcp

Command (node, npx, python, etc.)

Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
Enable "Start Automatically" if you want the plugin to start when Highlight launches

Setting up with Cursor

Open Cursor's settings
Navigate to the MCP section
Click "Add new Global MCP server"
Copy and paste the configuration below based on your operating system

JSON

{
    "mcpServers": {
        "repo context mcp": {
            "repo-context": {
                "type": "stdio",
                "command": "npx",
                "args": [
                    "@pablopeek/repo-context-mcp"
                ],
                "env": {
                    "ENVIRONMENT": "local",
                    "GITHUB_TOKEN": "<SET_GITHUB_TOKEN>",
                    "GITHUB_NAME": "<SET_GITHUB_NAME>"
                }
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "repo context mcp": {
            "repo-context": {
                "type": "stdio",
                "command": "npx",
                "args": [
                    "@pablopeek/repo-context-mcp"
                ],
                "env": {
                    "ENVIRONMENT": "local",
                    "GITHUB_TOKEN": "<SET_GITHUB_TOKEN>",
                    "GITHUB_NAME": "<SET_GITHUB_NAME>"
                }
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "repo context mcp": {
            "repo-context": {
                "type": "stdio",
                "command": "npx",
                "args": [
                    "@pablopeek/repo-context-mcp"
                ],
                "env": {
                    "ENVIRONMENT": "local",
                    "GITHUB_TOKEN": "<SET_GITHUB_TOKEN>",
                    "GITHUB_NAME": "<SET_GITHUB_NAME>"
                }
            }
        }
    }
}

Setting up with Claude Desktop

Open Claude Desktop's settings
Go to the Integrations tab
Click "Add MCP Server"
Use the configuration below based on your operating system

Note: Make sure Claude Desktop is running before attempting to connect.

JSON

{
    "mcpServers": {
        "repo context mcp": {
            "repo-context": {
                "type": "stdio",
                "command": "npx",
                "args": [
                    "@pablopeek/repo-context-mcp"
                ],
                "env": {
                    "ENVIRONMENT": "local",
                    "GITHUB_TOKEN": "<SET_GITHUB_TOKEN>",
                    "GITHUB_NAME": "<SET_GITHUB_NAME>"
                }
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "repo context mcp": {
            "repo-context": {
                "type": "stdio",
                "command": "npx",
                "args": [
                    "@pablopeek/repo-context-mcp"
                ],
                "env": {
                    "ENVIRONMENT": "local",
                    "GITHUB_TOKEN": "<SET_GITHUB_TOKEN>",
                    "GITHUB_NAME": "<SET_GITHUB_NAME>"
                }
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "repo context mcp": {
            "repo-context": {
                "type": "stdio",
                "command": "npx",
                "args": [
                    "@pablopeek/repo-context-mcp"
                ],
                "env": {
                    "ENVIRONMENT": "local",
                    "GITHUB_TOKEN": "<SET_GITHUB_TOKEN>",
                    "GITHUB_NAME": "<SET_GITHUB_NAME>"
                }
            }
        }
    }
}

Setting up with Windsurf

Open Windsurf's preferences
Go to the Integrations section
Click "Add MCP Integration"
Use the configuration below based on your operating system

JSON

{
    "mcpServers": {
        "repo context mcp": {
            "repo-context": {
                "type": "stdio",
                "command": "npx",
                "args": [
                    "@pablopeek/repo-context-mcp"
                ],
                "env": {
                    "ENVIRONMENT": "local",
                    "GITHUB_TOKEN": "<SET_GITHUB_TOKEN>",
                    "GITHUB_NAME": "<SET_GITHUB_NAME>"
                }
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "repo context mcp": {
            "repo-context": {
                "type": "stdio",
                "command": "npx",
                "args": [
                    "@pablopeek/repo-context-mcp"
                ],
                "env": {
                    "ENVIRONMENT": "local",
                    "GITHUB_TOKEN": "<SET_GITHUB_TOKEN>",
                    "GITHUB_NAME": "<SET_GITHUB_NAME>"
                }
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "repo context mcp": {
            "repo-context": {
                "type": "stdio",
                "command": "npx",
                "args": [
                    "@pablopeek/repo-context-mcp"
                ],
                "env": {
                    "ENVIRONMENT": "local",
                    "GITHUB_TOKEN": "<SET_GITHUB_TOKEN>",
                    "GITHUB_NAME": "<SET_GITHUB_NAME>"
                }
            }
        }
    }
}

Setting up with Cline

Open Cline's settings
Navigate to the Integrations section
Click "Add MCP Server"
Copy and paste the configuration below based on your operating system

Note: Make sure to restart Cline after adding the configuration.

JSON

{
    "mcpServers": {
        "repo context mcp": {
            "repo-context": {
                "type": "stdio",
                "command": "npx",
                "args": [
                    "@pablopeek/repo-context-mcp"
                ],
                "env": {
                    "ENVIRONMENT": "local",
                    "GITHUB_TOKEN": "<SET_GITHUB_TOKEN>",
                    "GITHUB_NAME": "<SET_GITHUB_NAME>"
                }
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "repo context mcp": {
            "repo-context": {
                "type": "stdio",
                "command": "npx",
                "args": [
                    "@pablopeek/repo-context-mcp"
                ],
                "env": {
                    "ENVIRONMENT": "local",
                    "GITHUB_TOKEN": "<SET_GITHUB_TOKEN>",
                    "GITHUB_NAME": "<SET_GITHUB_NAME>"
                }
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "repo context mcp": {
            "repo-context": {
                "type": "stdio",
                "command": "npx",
                "args": [
                    "@pablopeek/repo-context-mcp"
                ],
                "env": {
                    "ENVIRONMENT": "local",
                    "GITHUB_TOKEN": "<SET_GITHUB_TOKEN>",
                    "GITHUB_NAME": "<SET_GITHUB_NAME>"
                }
            }
        }
    }
}

Setting up with Goose

Open Goose's preferences
Go to the Integrations tab
Select "MCP Servers"
Click "Add New Server"
Use the configuration below based on your operating system

JSON

{
    "mcpServers": {
        "repo context mcp": {
            "repo-context": {
                "type": "stdio",
                "command": "npx",
                "args": [
                    "@pablopeek/repo-context-mcp"
                ],
                "env": {
                    "ENVIRONMENT": "local",
                    "GITHUB_TOKEN": "<SET_GITHUB_TOKEN>",
                    "GITHUB_NAME": "<SET_GITHUB_NAME>"
                }
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "repo context mcp": {
            "repo-context": {
                "type": "stdio",
                "command": "npx",
                "args": [
                    "@pablopeek/repo-context-mcp"
                ],
                "env": {
                    "ENVIRONMENT": "local",
                    "GITHUB_TOKEN": "<SET_GITHUB_TOKEN>",
                    "GITHUB_NAME": "<SET_GITHUB_NAME>"
                }
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "repo context mcp": {
            "repo-context": {
                "type": "stdio",
                "command": "npx",
                "args": [
                    "@pablopeek/repo-context-mcp"
                ],
                "env": {
                    "ENVIRONMENT": "local",
                    "GITHUB_TOKEN": "<SET_GITHUB_TOKEN>",
                    "GITHUB_NAME": "<SET_GITHUB_NAME>"
                }
            }
        }
    }
}

From the repository

Set environment variables GITHUB_TOKEN and GITHUB_NAME (do not store tokens in config files). Then invoke the server and use its tools such as setRepoPath, getFiles, getFileContent, getReadme, analyzeFileTypes, analyzeFileTypesAdvanced, getGithubFileContent, and getSwaggerSpec.

`setRepoPath`

Change the active repository path

`getFiles`

List files and folders at the given path in the active repo

`getFileContent`

Read the content of a file in the active repo

`getReadme`

Read the README.md file from the active repo

`analyzeFileTypes`

Analyze a file and return exported functions and the type of their parameters (if available)

`analyzeFileTypesAdvanced`

Analyze a file using ts-morph and return exported functions and the type of their parameters (resolving local and imported types)

`getGithubFileContent`

Read the content of a file from a (private) GitHub repository using the GitHub API.

`getSwaggerSpec`

Read the Swagger/OpenAPI specification file (swagger.json, openapi.json, openapi.yaml, etc.) from the active repo.

Claude Desktop / Cursor

Paste into your MCP client config file to install this server.

{
    "mcpServers": {
        "repo context mcp": {
            "repo-context": {
                "type": "stdio",
                "command": "npx",
                "args": [
                    "@pablopeek/repo-context-mcp"
                ],
                "env": {
                    "ENVIRONMENT": "local",
                    "GITHUB_TOKEN": "<SET_GITHUB_TOKEN>",
                    "GITHUB_NAME": "<SET_GITHUB_NAME>"
                }
            }
        }
    }
}

McpServers

{
    "repo-context": {
        "type": "stdio",
        "command": "npx",
        "args": [
            "@pablopeek/repo-context-mcp"
        ],
        "env": {
            "ENVIRONMENT": "local",
            "GITHUB_TOKEN": "<SET_GITHUB_TOKEN>",
            "GITHUB_NAME": "<SET_GITHUB_NAME>"
        }
    }
}

Repo Context MCP

--- A programmatic MCP server to explore repositories (local or GitHub). List files, read files, return README, analyze TypeScript types (ts-morph) and locate OpenAPI/Swagger specs.

Quick start

- Set env var (never store tokens in config): export GITHUB_TOKEN="<SET_YOUR_TOKEN>" export GITHUB_NAME="<SET_YOUR_NAME>"

Available tools

setRepoPath — set active repo path Payload: { "path": "/absolute/path/to/repo" } --- getFiles — list files/folders Payload: { "path": "optional/relative/path" } --- getFileContent — read file contents Payload: { "file": "relative/path/to/file.ext" } --- getReadme — return README.md (root) --- analyzeFileTypes — simple exported function scan Payload: { "file": "src/foo.ts" } --- analyzeFileTypesAdvanced — ts-morph resolution (may require project deps) --- getGithubFileContent — read file from GitHub (uses GITHUB_TOKEN) Payload: { "owner":"org","repo":"name","path":"path/to/file","ref":"branch?" } --- getSwaggerSpec — search common locations for OpenAPI/Swagger specs --- Contact Author: pablo-peek — repo: Repo Context MCP

No reviews yet — be the first

Use Google, GitHub, or an email account so ratings stay tied to real people.

Email sign in

No reviews posted yet.

Repo Context Mcp

About

Details

Jump to

Setting up with Highlight

Setting up with Cursor

JSON

JSON

JSON

Setting up with Claude Desktop

JSON

JSON

JSON

Setting up with Windsurf

JSON

JSON

JSON

Setting up with Cline

JSON

JSON

JSON

Setting up with Goose

JSON

JSON

JSON

From the repository

`setRepoPath`

`getFiles`

`getFileContent`

`getReadme`

`analyzeFileTypes`

`analyzeFileTypesAdvanced`

`getGithubFileContent`

`getSwaggerSpec`

Claude Desktop / Cursor

McpServers

Repo Context MCP

Quick start

Available tools

Install

About

Details

Jump to

Setting up with Highlight

From the repository

setRepoPath

getFiles

getFileContent

getReadme

analyzeFileTypes

analyzeFileTypesAdvanced

getGithubFileContent

getSwaggerSpec

Claude Desktop / Cursor

McpServers

Repo Context MCP

Quick start

Available tools

Install

More like this

Aws Kb Retrieval Server

Memory

Sentry

Github

Git

GitLab

`setRepoPath`

`getFiles`

`getFileContent`

`getReadme`

`analyzeFileTypes`

`analyzeFileTypesAdvanced`

`getGithubFileContent`

`getSwaggerSpec`