@mohammadhprp/system-prompt 0.10.1

package/framework/mcps/github-mcp/capabilities.md

@@ -0,0 +1,83 @@
+# GitHub MCP Capabilities
+
+## What It Can Do
+
+The server provides toolsets across the following categories:
+
+### Context
+
+Tools that provide information about the authenticated user and organization membership.
+
+### Repositories
+
+Browse repository code, files, directory trees, commits, and branches. Search code across repositories.
+
+### Issues
+
+Create, read, update issues. Add comments, manage labels, assignees, and milestones.
+
+### Pull Requests
+
+Create, review, update, and merge pull requests. Add review comments, request changes, approve. List changed files and review diffs.
+
+### Actions
+
+List workflows, trigger workflow runs. Get workflow run details, job logs, and artifacts.
+
+### Code Security
+
+List and read code scanning alerts, Dependabot alerts.
+
+### Discussions
+
+Read and create discussions, manage comments.
+
+### Gists
+
+Create, read, update gists.
+
+### Users & Organizations
+
+Read user profiles, list teams, list organization members.
+
+### Additional Toolsets (remote server)
+
+- Copilot — assign Copilot to issues, request Copilot review.
+- Copilot Spaces — manage Copilot spaces.
+- GitHub Support Docs Search — answer GitHub product and support questions.
+
+## What It Cannot Do
+
+- It cannot operate without a valid GitHub token or OAuth session.
+- It cannot access repositories the token does not have permissions for.
+- It cannot directly execute code or deploy to production.
+- It does not provide real-time notifications or webhook management.
+- Some toolsets are only available on the remote server (Copilot, Support Docs Search).
+
+## Best Practices
+
+- Use a fine-grained PAT scoped to the minimum repositories and permissions needed.
+- Store the PAT in `.env` (under `.opencode/`) and never commit it to version control.
+- Use `GITHUB_TOOLSETS` environment variable (when running locally) to enable only the tool groups needed.
+- For read-only workflows, limit the PAT to read-only scopes.
+- Prefer the remote HTTP server for simplicity; use the local Docker server only when remote HTTP is not supported.
+
+## Common Workflows
+
+### Review a pull request
+
+1. Let the agent browse the PR diff and changed files.
+2. The agent can post review comments, approve, or request changes.
+3. Merge when ready.
+
+### Investigate a CI failure
+
+1. Ask the agent to list recent Actions workflow runs.
+2. The agent can read job logs to find the failure.
+3. Use the findings to propose a fix.
+
+### Manage issues
+
+1. List open issues with filtering by label, assignee, or state.
+2. Read issue details and comments.
+3. Create or update issues with labels, assignees, and milestones.

package/framework/mcps/github-mcp/configs/.env.example

@@ -0,0 +1 @@
+GITHUB_TOKEN=

package/framework/mcps/github-mcp/configs/opencode.json

@@ -0,0 +1,13 @@
+{
+  "mcp": {
+    "github": {
+      "type": "remote",
+      "enabled": true,
+      "oauth": false,
+      "url": "https://api.githubcopilot.com/mcp/",
+      "headers": {
+        "Authorization": "Bearer {env:GITHUB_PERSONAL_ACCESS_TOKEN}"
+      }
+    }
+  }
+}

package/framework/mcps/github-mcp/install.md

@@ -0,0 +1,60 @@
+# GitHub MCP Installation
+
+## Requirements
+
+- A GitHub account with API access.
+- A GitHub Personal Access Token (classic or fine-grained) with the following scopes:
+  - `repo` — full control of private repositories.
+  - `read:org` — read organization membership.
+- An MCP-compatible AI client that supports remote HTTP MCP servers.
+
+## Authentication
+
+This MCP uses the **remote GitHub MCP Server** hosted by GitHub at `https://api.githubcopilot.com/mcp/`. Authentication is handled via a `Bearer` token in the `Authorization` header.
+
+| Method | Best for |
+| --- | --- |
+| Personal Access Token (PAT) | Simplest local setup |
+| OAuth (via host support) | Better security when host supports it |
+
+## Configuration
+
+| Field | Value |
+| --- | --- |
+| Server name | `github` |
+| Type | `http` |
+| URL | `https://api.githubcopilot.com/mcp/` |
+| Auth header | `Authorization: Bearer {env:GITHUB_PERSONAL_ACCESS_TOKEN}` |
+
+### Config file examples
+
+Use the examples in [`configs/`](./configs/) as client-specific starting points:
+
+| Client | Example | Typical location |
+| --- | --- | --- |
+| OpenCode | [`configs/opencode.json`](./configs/opencode.json) | OpenCode MCP configuration. |
+
+### OpenCode
+
+Copy [`configs/opencode.json`](./configs/opencode.json) into your OpenCode project root or user config directory, ensure `GITHUB_PERSONAL_ACCESS_TOKEN` is set in your `.env` file, and restart the OpenCode agent.
+
+## Verification
+
+From your AI client:
+
+- The `github` MCP server is listed.
+- The server starts without errors.
+- Tools are visible to the agent.
+
+Recommended first prompt:
+
+```
+List my GitHub repositories and show me recent pull requests.
+```
+
+## Common Issues
+
+- **Server does not start**: confirm your client supports remote HTTP MCP servers.
+- **Authentication errors**: confirm the PAT has the required scopes and `GITHUB_PERSONAL_ACCESS_TOKEN` is set in your `.env` or environment.
+- **401 Unauthorized**: regenerate the token in GitHub **Settings → Developer settings → Personal access tokens**.
+- **Rate limiting**: GitHub API has rate limits; reduce the frequency of tool calls if you encounter 429 errors.

package/framework/mcps/github-mcp/troubleshooting.md

@@ -0,0 +1,79 @@
+# GitHub MCP Troubleshooting
+
+## Server won't start
+
+**Problem**
+
+The AI client reports that `github` failed to start.
+
+**Cause**
+
+The client does not support remote HTTP MCP servers, or the URL is misconfigured.
+
+**Solution**
+
+- Verify the `type` is `http` and `url` is `https://api.githubcopilot.com/mcp/`.
+- Check that your client supports remote MCP servers (VS Code 1.101+, Claude Desktop, Cursor, Windsurf, OpenCode).
+- If remote HTTP is not supported, use the local Docker version instead (see upstream docs).
+
+## Authentication errors
+
+**Problem**
+
+The server starts but returns 401 Unauthorized on tool calls.
+
+**Cause**
+
+The `GITHUB_PERSONAL_ACCESS_TOKEN` is missing, expired, or invalid.
+
+**Solution**
+
+- Verify `GITHUB_PERSONAL_ACCESS_TOKEN` is set: check your `.env` file or environment variables.
+- Confirm the token is a valid GitHub Personal Access Token with the required scopes.
+- Generate a new token in GitHub: **Settings → Developer settings → Personal access tokens → Fine-grained tokens**.
+- Ensure the token is not expired.
+
+## Rate limiting
+
+**Problem**
+
+Tools return 429 Too Many Requests errors.
+
+**Cause**
+
+GitHub API rate limits have been exceeded.
+
+**Solution**
+
+- Reduce the frequency of tool calls.
+- Wait for the rate limit window (typically 1 hour) to reset before retrying.
+- For higher limits, authenticate with a PAT that has the necessary scopes.
+
+## Token in version control
+
+**Problem**
+
+Risk of leaking the GitHub token to version control.
+
+**Solution**
+
+- Never hardcode the token in `opencode.json` or any config file.
+- Use `{env:GITHUB_PERSONAL_ACCESS_TOKEN}` in config files and store the actual value in `.env`.
+- Add `.env` to `.gitignore`.
+- Restrict `.env` file permissions: `chmod 600 .opencode/.env`.
+
+## Permission errors
+
+**Problem**
+
+Tools return 403 Forbidden or insufficient permissions.
+
+**Cause**
+
+The authenticated token does not have the required scopes or repository access.
+
+**Solution**
+
+- Verify the token has `repo` scope for private repositories.
+- For organization access, ensure `read:org` scope is included.
+- For fine-grained tokens, ensure the token has access to the target repository.

package/framework/mcps/gitlab-mcp/README.md

@@ -0,0 +1,54 @@
+# GitLab MCP
+
+## Overview
+
+GitLab MCP is a comprehensive GitLab MCP server for AI clients. Manage projects, merge requests, issues, pipelines, wiki, releases, tags, milestones, and more through stdio, SSE, and Streamable HTTP transports. Supports PAT, OAuth, read-only mode, dynamic API URLs, and remote authorization.
+
+Official source:
+
+- [GitHub: zereight/gitlab-mcp](https://github.com/zereight/gitlab-mcp)
+- [Documentation](https://zereight.github.io/gitlab-mcp/)
+
+## Features
+
+- Broad GitLab coverage — 117+ tools for projects, repository browsing, merge requests, issues, pipelines, wiki, releases, tags, labels, milestones, and more.
+- Flexible auth — Personal Access Token, local OAuth2 browser flow, MCP OAuth proxy, and per-request remote authorization.
+- Multiple transports — stdio for local clients, SSE for legacy clients, and Streamable HTTP for modern remote deployments.
+- Client-friendly setup — examples for Claude Code, Codex, OpenCode, Copilot, Cline, Roo Code, Cursor, and more.
+- Self-hosted ready — works with custom GitLab instances, proxy settings, and dynamic API URL routing.
+- Permission modes — `readonly`, `modify` (no delete), or `full`; tool filtering by toolset groups, allow-list, and deny-list.
+
+## Supported AI Clients
+
+GitLab MCP officially documents setup for Claude Code, VS Code, GitHub Copilot, Codex, Cursor, and JSON-based MCP clients.
+
+- OpenCode
+
+## When to Use
+
+Use GitLab MCP when an AI coding agent needs to interact with a GitLab instance.
+
+Good fits:
+
+- Reviewing, approving, and merging merge requests.
+- Browsing repositories, files, and commit history.
+- Creating and managing issues and to-do items.
+- Inspecting CI/CD pipelines and job logs.
+- Managing wiki pages, milestones, labels, and releases.
+- Automating GitLab workflows from an AI agent.
+
+Avoid using it outside of GitLab-related workflows.
+
+## Requirements
+
+- Node.js >= 18 and npm (for `npx` or global install), or Homebrew (for `brew install`).
+- A GitLab account with API access.
+- A Personal Access Token with appropriate scopes, or OAuth2 credentials.
+
+## Related Skills
+
+Relevant skills in this repository:
+
+- [`backend-engineer`](../../skills/backend-engineer/SKILL.md): feature work in projects hosted on GitLab.
+- [`backend-best-practices`](../../skills/backend-best-practices/SKILL.md): backend best practices for API design, testing, debugging, performance, and security.
+- [`code-review`](../../skills/code-review/SKILL.md): reviewing merge request diffs.

package/framework/mcps/gitlab-mcp/capabilities.md

@@ -0,0 +1,216 @@
+# GitLab MCP Capabilities
+
+## What It Can Do
+
+117+ tools across projects, merge requests, issues, pipelines, wiki, milestones, labels, and more.
+
+### Merge Requests
+
+| Tool | Description |
+| --- | --- |
+| `list_merge_requests` | List merge requests with filtering |
+| `get_merge_request` | Get merge request details |
+| `create_merge_request` | Create a new merge request |
+| `update_merge_request` | Update a merge request |
+| `merge_merge_request` | Merge a merge request |
+| `approve_merge_request` | Approve a merge request |
+| `unapprove_merge_request` | Unapprove a merge request |
+| `get_merge_request_approval_state` | Get approval details including approvers |
+| `get_merge_request_diffs` | Get the changes/diffs of a merge request |
+| `list_merge_request_diffs` | List diffs with pagination |
+| `get_merge_request_conflicts` | Get merge request conflicts |
+| `list_merge_request_changed_files` | List changed file paths (without diff) |
+| `get_merge_request_file_diff` | Get diffs for specific files |
+| `list_merge_request_versions` | List all versions of a merge request |
+| `get_merge_request_version` | Get a specific version |
+| `get_branch_diffs` | Get diffs between two branches or commits |
+| `mr_discussions` | List discussion items for a merge request |
+| `resolve_merge_request_thread` | Resolve a thread |
+| `create_merge_request_thread` | Create a new thread |
+| `create_merge_request_note` | Add a note to an existing thread |
+| `create_merge_request_discussion_note` | Add a discussion note |
+| `update_merge_request_note` | Modify a merge request note |
+| `update_merge_request_discussion_note` | Update a discussion note |
+| `delete_merge_request_note` | Delete a merge request note |
+| `delete_merge_request_discussion_note` | Delete a discussion note |
+| `get_merge_request_note` | Get a specific note |
+| `get_merge_request_notes` | List notes for a merge request |
+| `create_note` | Create a comment on an issue or MR |
+| `get_draft_note` | Get a single draft note |
+| `list_draft_notes` | List draft notes |
+| `create_draft_note` | Create a draft note |
+| `update_draft_note` | Update a draft note |
+| `delete_draft_note` | Delete a draft note |
+| `publish_draft_note` | Publish a single draft note |
+| `bulk_publish_draft_notes` | Publish all draft notes |
+
+### Issues
+
+| Tool | Description |
+| --- | --- |
+| `list_issues` | List issues with filtering |
+| `my_issues` | List issues assigned to the current user |
+| `get_issue` | Get issue details |
+| `create_issue` | Create a new issue |
+| `update_issue` | Update an issue |
+| `update_issue_description_patch` | Apply a patch to an issue description |
+| `delete_issue` | Delete an issue |
+| `create_issue_note` | Add a note to an issue thread |
+| `update_issue_note` | Modify an issue thread note |
+| `list_issue_discussions` | List discussions for an issue |
+| `list_issue_links` | List issue links |
+| `get_issue_link` | Get a specific issue link |
+| `create_issue_link` | Link two issues |
+| `delete_issue_link` | Delete an issue link |
+
+### Projects & Repositories
+
+| Tool | Description |
+| --- | --- |
+| `search_repositories` | Search for GitLab projects |
+| `create_repository` | Create a new GitLab project |
+| `get_project` | Get project details |
+| `list_projects` | List accessible projects |
+| `list_project_members` | List project members |
+| `fork_repository` | Fork a project |
+| `list_group_projects` | List projects in a group |
+| `list_namespaces` | List available namespaces |
+| `get_namespace` | Get namespace details |
+| `verify_namespace` | Verify a namespace path exists |
+| `create_group` | Create a new group or subgroup |
+| `list_group_iterations` | List group iterations |
+
+### Files & Commits
+
+| Tool | Description |
+| --- | --- |
+| `get_file_contents` | Get file or directory contents |
+| `create_or_update_file` | Create or update a single file |
+| `push_files` | Push multiple files in a single commit |
+| `create_branch` | Create a new branch |
+| `get_repository_tree` | List repository files and directories |
+| `list_commits` | List commits with filtering |
+| `get_commit` | Get commit details |
+| `get_commit_diff` | Get commit changes/diffs |
+
+### CI/CD Pipelines
+
+| Tool | Description |
+| --- | --- |
+| `list_pipelines` | List pipelines with filtering |
+| `get_pipeline` | Get pipeline details |
+| `create_pipeline` | Create a pipeline for a branch or tag |
+| `retry_pipeline` | Retry a failed or canceled pipeline |
+| `cancel_pipeline` | Cancel a running pipeline |
+| `list_pipeline_jobs` | List all jobs in a pipeline |
+| `list_pipeline_trigger_jobs` | List trigger jobs (bridges) |
+| `get_pipeline_job` | Get job details |
+| `get_pipeline_job_output` | Get job output/trace with pagination |
+| `play_pipeline_job` | Run a manual pipeline job |
+| `retry_pipeline_job` | Retry a failed job |
+| `cancel_pipeline_job` | Cancel a running job |
+| `validate_ci_lint` | Validate CI/CD YAML content |
+| `validate_project_ci_lint` | Validate existing `.gitlab-ci.yml` |
+| `list_job_artifacts` | List artifact files in a job |
+| `download_job_artifacts` | Download artifact archive (zip) |
+| `get_job_artifact_file` | Get content of a single artifact file |
+| `list_deployments` | List deployments |
+| `get_deployment` | Get deployment details |
+| `list_environments` | List environments |
+| `get_environment` | Get environment details |
+
+### Wiki
+
+| Tool | Description |
+| --- | --- |
+| `list_wiki_pages` | List project wiki pages |
+| `get_wiki_page` | Get wiki page details |
+| `create_wiki_page` | Create a new wiki page |
+| `update_wiki_page` | Update a wiki page |
+| `delete_wiki_page` | Delete a wiki page |
+| `list_group_wiki_pages` | List group wiki pages |
+| `get_group_wiki_page` | Get group wiki page details |
+| `create_group_wiki_page` | Create a group wiki page |
+| `update_group_wiki_page` | Update a group wiki page |
+| `delete_group_wiki_page` | Delete a group wiki page |
+
+### Milestones
+
+| Tool | Description |
+| --- | --- |
+| `list_milestones` | List milestones with filtering |
+| `get_milestone` | Get milestone details |
+| `create_milestone` | Create a new milestone |
+| `edit_milestone` | Edit an existing milestone |
+| `delete_milestone` | Delete a milestone |
+| `get_milestone_issue` | Get issues for a milestone |
+| `get_milestone_merge_requests` | Get MRs for a milestone |
+| `get_milestone_burndown_events` | Get burndown events |
+| `promote_milestone` | Promote a milestone |
+
+### Labels & To-Dos
+
+| Tool | Description |
+| --- | --- |
+| `list_labels` | List project labels |
+| `get_label` | Get a single label |
+| `create_label` | Create a new label |
+| `update_label` | Update an existing label |
+| `delete_label` | Delete a label |
+| `list_todos` | List to-do items |
+| `mark_todo_done` | Mark a to-do item as done |
+| `mark_all_todos_done` | Mark all to-do items as done |
+
+### Releases (not listed in README tools, but mentioned in features)
+
+The server may expose additional release and tag management tools depending on the installed version. Refer to the official [documentation](https://zereight.github.io/gitlab-mcp/) for the full tool list.
+
+## What It Cannot Do
+
+- It cannot operate without a GitLab account and API token or OAuth credentials.
+- It cannot access GitLab features outside the authenticated user's permissions.
+- It does not support SSE transport when using `REMOTE_AUTHORIZATION` mode (Streamable HTTP required).
+- It cannot safely infer production intent; agents still need explicit instructions before destructive operations.
+- Read-only mode (`GITLAB_PERMISSION_MODE=readonly`) blocks all write, update, and delete tools but does not prevent the agent from reading sensitive project data that the token has access to.
+
+## Best Practices
+
+- Use a Personal Access Token with the minimum required scopes (`read_api` for read-only workflows, `api` for write workflows).
+- Use `GITLAB_PERMISSION_MODE=readonly` or `modify` to restrict agent capabilities.
+- Use `GITLAB_TOOLSETS` to enable only the tool groups needed (e.g., `wiki,milestones,pipelines`).
+- Use `GITLAB_TOOLS` allow-list to enable individual tools, and `GITLAB_DENIED_TOOLS_REGEX` to block by pattern.
+- Prefer OAuth2 over PAT for better security in desktop workflows.
+- For multi-user deployments, use `REMOTE_AUTHORIZATION` so each caller provides their own token.
+- Use `list_merge_request_changed_files` first, then `get_merge_request_file_diff` on selected files, to reduce token usage during code review.
+- Validate CI/CD changes with `validate_ci_lint` before committing.
+
+## Common Workflows
+
+### Review a merge request
+
+1. Call `list_merge_request_changed_files` to see which files changed.
+2. Call `get_merge_request_file_diff` on 3-5 files at a time to review diffs.
+3. Call `get_merge_request_approval_state` to check approvers.
+4. Use `create_merge_request_thread` or `create_note` to leave feedback.
+5. Call `approve_merge_request` and `merge_merge_request` when ready.
+
+### Investigate a pipeline failure
+
+1. Call `list_pipelines` to find the failed pipeline.
+2. Call `list_pipeline_jobs` to see which jobs failed.
+3. Call `get_pipeline_job_output` to read the failing job's logs.
+4. Use the logs to diagnose the issue and propose a fix.
+
+### Manage issues
+
+1. Call `list_issues` or `my_issues` to see open issues.
+2. Call `get_issue` to read details of a specific issue.
+3. Call `create_issue_note` to comment or request clarification.
+4. Call `update_issue` to change status, assignee, or labels.
+
+### Browse and edit repository files
+
+1. Call `get_repository_tree` to list files in a directory.
+2. Call `get_file_contents` to read specific files.
+3. Call `create_or_update_file` or `push_files` to make changes.
+4. Call `create_branch` and `create_merge_request` to propose changes.

package/framework/mcps/gitlab-mcp/configs/.env.example

@@ -0,0 +1,2 @@
+GITLAB_API_URL=
+GITLAB_PERSONAL_ACCESS_TOKEN=

package/framework/mcps/gitlab-mcp/configs/opencode.json

@@ -0,0 +1,13 @@
+{
+  "mcp": {
+    "gitlab": {
+        "type": "local",
+        "enabled": true,
+        "command": ["bun", "x", "@zereight/mcp-gitlab"],
+        "environment": {
+            "GITLAB_PERSONAL_ACCESS_TOKEN": "{env:GITLAB_PERSONAL_ACCESS_TOKEN}",
+            "GITLAB_API_URL": "{env:GITLAB_API_URL}"
+        }
+    }
+  }
+}

package/framework/mcps/gitlab-mcp/install.md

@@ -0,0 +1,99 @@
+# GitLab MCP Installation
+
+## Requirements
+
+- Node.js >= 18 and npm available on `PATH`, or Homebrew.
+- A GitLab account with API access.
+- A GitLab Personal Access Token with `api` scope (or `read_api` for read-only mode).
+- An MCP-compatible AI client.
+
+## Authentication
+
+The server supports four authentication methods:
+
+| Method | Best for |
+| --- | --- |
+| Personal Access Token (PAT) | Simplest local setup |
+| OAuth2 — Local Browser | Better security for desktop use |
+| OAuth2 — MCP Proxy | Remote deployments (Claude.ai, etc.) |
+| Remote Authorization | Multi-user deployments with per-request tokens |
+
+## Installation
+
+Install globally via npm or Homebrew:
+
+```bash
+npm install -g @zereight/mcp-gitlab
+```
+
+Or with Homebrew:
+
+```bash
+brew install zereight/gitlab-mcp/zereight-mcp-gitlab
+```
+
+No global install? Use `npx` pinned to a specific version:
+
+```bash
+npx -y @zereight/mcp-gitlab@latest
+```
+
+## Configuration
+
+| Field | Value |
+| --- | --- |
+| Server name | `gitlab` |
+| Command | `zereight-mcp-gitlab` |
+| Env | `GITLAB_PERSONAL_ACCESS_TOKEN`, `GITLAB_API_URL` |
+| Alt command (no global install) | `npx` with args `-y`, `@zereight/mcp-gitlab@latest` |
+| CLI args | `--token`, `--api-url`, `--permission-mode` |
+
+### Config file examples
+
+Use the examples in [`configs/`](./configs/) as client-specific starting points:
+
+| Client | Example | Typical location |
+| --- | --- | --- |
+| OpenCode | [`configs/opencode.json`](./configs/opencode.json) | OpenCode MCP configuration. |
+
+### OpenCode
+
+Copy [`configs/opencode.json`](./configs/opencode.json) into your OpenCode project root or user config directory, replace the placeholder token and API URL, and restart the OpenCode agent.
+
+## Verification
+
+Run the MCP server command directly:
+
+```bash
+zereight-mcp-gitlab
+```
+
+Then verify from your AI client:
+
+- The `gitlab` MCP server is listed.
+- The server starts without errors.
+- Tools are visible to the agent.
+
+Recommended first prompt:
+
+```
+List my GitLab projects and show me recent merge requests.
+```
+
+## Updating
+
+```bash
+npm update -g @zereight/mcp-gitlab
+```
+
+## Uninstalling
+
+1. Remove the MCP entry from AI client configuration files.
+2. Uninstall the package: `npm uninstall -g @zereight/mcp-gitlab`.
+
+## Common Issues
+
+- **Server does not start**: run `zereight-mcp-gitlab` manually and fix the first error shown. Ensure Node.js >= 18 is installed.
+- **Authentication errors**: confirm the PAT has the correct scopes and the API URL is `https://gitlab.com/api/v4` (not the web URL).
+- **Client cannot find the server**: use the absolute path from `which zereight-mcp-gitlab`, or use `npx` as the command instead.
+- **Wrong API URL**: use `https://gitlab.com/api/v4` for GitLab SaaS, or `https://your-instance/api/v4` for self-hosted.