GitHub Service

Description: Repository management, issues, and PRs via GitHub API

Configuration

1. Personal Access Token (classic) with required scopes
2. Owner: username or org
3. Repository: optional default

Detailed Configuration Instructions

1. Create GitHub Access Token:
   • GitHub Settings → Developer settings → Personal access tokens (classic)
   • Click "Generate new token (classic)"
   • Select required scopes (repo, workflow, read:org, etc. as needed)
   • Generate and copy the token
2. Set Owner: Use your username or organization name
3. Set Repository (optional): Default repo name, or specify per request
4. Configure in plemeo MCP: Enter token, owner, repository

Important Notes

• The token must have permissions for the target repositories
• Owner is the namespace for repositories (user or org)
• You can leave repository empty and provide it in each request

Main Commands

• List issues and PRs
• Create issue
• Get issue details
• List PRs
• Create PR
• Merge PR
• List branches
• Repository traffic data

Examples

Create a GitHub issue in my-project with title 'Bug in login form'

Show me all open pull requests in the main branch

Merge pull request #123 with commit message 'Fix login bug'

List all branches in the repository

Show me the traffic data for my repository

Get details of issue #456 in the frontend repository

Create a pull request from feature-branch to main with title 'Add new feature'