mcp-oss-onramp
README.md
# mcp-oss-onramp
**AI Scout for truly available, beginner-friendly OSS issues.**
[日本語版はこちら](./docs/README_ja.md) | [Full Documentation](./docs/README_full.md)
## Quick Start
Run directly via `npx`:
```bash
npx mcp-oss-onramp
```
### Direct Execution (CLI)
You can also run the server with a token directly in your terminal:
```bash
MCP_OSS_ONRAMP_GITHUB_TOKEN="your_token_here" npx mcp-oss-onramp
```
## MCP Configuration
Add this to your AI agent's configuration:
```json
{
"mcpServers": {
"oss-onramp": {
"command": "npx",
"args": ["-y", "mcp-oss-onramp"]
}
}
}
```
## Features
- **True Availability**: Checks linked PRs via GraphQL to filter out issues already being worked on.
- **AI-Optimized**: Summarizes issue bodies for efficient LLM consumption.
- **High Precision**: Targets beginner-friendly tasks even without explicit labels.
## Prerequisites
- **GitHub Authentication (Recommended)**:
- Set `MCP_OSS_ONRAMP_GITHUB_TOKEN` environment variable, OR
- Install [GitHub CLI (gh)](https://cli.github.com/) and authenticate via `gh auth login`.
- **Node.js**: Version 18 or higher.
*Note: The server works without authentication but will be rate-limited and provide lower precision (no PR cross-referencing).*
## License
MIT
TDQS
A3.9/5.0
Scored across 1 tool
Disambiguation5/5
With only one tool, there is no possibility of confusion or overlap. The tool's purpose is distinct and well-defined.
Naming Consistency5/5
The single tool name 'scout_issues' follows a clear verb_noun pattern. Consistency is inherently maintained with one tool.
Tool Count2/5
Having only one tool is too few for the apparent scope of an OSS onboarding server. It feels thin and limits functionality.
Completeness2/5
The server covers only scouting for issues, missing other essential operations like fetching issue details or interacting with issues. This leaves significant gaps for a comprehensive tool set.
Maintenance
ActivityInactive
ResponsivenessResponsive