Appearance
Configuration
Pipeline Doctor works with any MCP-compatible client. You'll need a GitHub Personal Access Token with repo and actions:read scopes.
Pipeline Doctor supports two transports:
- stdio — local process, each client spawns its own server (recommended for individual use)
- HTTP — remote hosted server with OAuth 2.1 authentication (for teams and marketplace)
Claude Desktop
Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
json
{
"mcpServers": {
"pipeline-doctor": {
"command": "npx",
"args": ["-y", "pipeline-doctor"],
"env": {
"GITHUB_TOKEN": "ghp_your_token_here"
}
}
}
}json
{
"mcpServers": {
"pipeline-doctor": {
"type": "http",
"url": "https://pipeline-doctor.example.com/mcp"
}
}
}Claude Code
bash
claude mcp add pipeline-doctor -- npx -y pipeline-doctorjson
{
"mcpServers": {
"pipeline-doctor": {
"command": "npx",
"args": ["-y", "pipeline-doctor"],
"env": {
"GITHUB_TOKEN": "ghp_your_token_here"
}
}
}
}json
{
"mcpServers": {
"pipeline-doctor": {
"type": "http",
"url": "https://pipeline-doctor.example.com/mcp"
}
}
}Cursor
Add to .cursor/mcp.json in your project root:
json
{
"mcpServers": {
"pipeline-doctor": {
"command": "npx",
"args": ["-y", "pipeline-doctor"],
"env": {
"GITHUB_TOKEN": "ghp_your_token_here"
}
}
}
}json
{
"mcpServers": {
"pipeline-doctor": {
"type": "http",
"url": "https://pipeline-doctor.example.com/mcp"
}
}
}VS Code (GitHub Copilot)
Add to .vscode/mcp.json in your project root:
json
{
"servers": {
"pipeline-doctor": {
"command": "npx",
"args": ["-y", "pipeline-doctor"],
"env": {
"GITHUB_TOKEN": "ghp_your_token_here"
}
}
}
}json
{
"servers": {
"pipeline-doctor": {
"type": "http",
"url": "https://pipeline-doctor.example.com/mcp"
}
}
}Default Repository
Pipeline Doctor auto-detects the repository from your git remote. You can also set it explicitly:
json
{
"args": ["-y", "pipeline-doctor", "--repo", "owner/repo"]
}When using HTTP transport, the MCP client infers the repository from your working directory context — no server-side configuration needed.
