Update README.md with plugin documentation
This commit is contained in:
@@ -1,3 +1,37 @@
|
||||
# git-mpm
|
||||
|
||||
Direct Gitea REST API integration for git.mpm.to — repos, issues, pull requests, releases, file contents, and webhooks.
|
||||
Gitea integration for git.mpm.to — interact with your organization's repositories, issues, pull requests, releases, file contents, and webhooks directly from Claude.
|
||||
|
||||
## What it does
|
||||
|
||||
This plugin gives Claude direct access to the MPM Gitea server via the REST API. No additional setup or MCP server required — API calls are made using curl in the shell.
|
||||
|
||||
## Capabilities
|
||||
|
||||
- **Repositories** — list, search, create, delete repos; list branches, collaborators, topics
|
||||
- **Issues** — create, list, update, close/reopen issues; add comments; manage labels
|
||||
- **Pull requests** — list, create, update, merge PRs; submit reviews; view diffs and commits
|
||||
- **Releases** — create, update, delete releases and tags; upload release assets
|
||||
- **File contents** — read, create, update, delete files in any repo; list directory trees
|
||||
- **Webhooks** — list, create, update, delete, and test webhooks at repo or org level
|
||||
|
||||
## Usage examples
|
||||
|
||||
- "Show me all open PRs in the web-app repo"
|
||||
- "Create an issue in mpm/backend titled 'Fix login bug'"
|
||||
- "What's the latest release for the mobile app?"
|
||||
- "Read the contents of src/config.yaml in mpm/api"
|
||||
- "List all webhooks on the mpm/integrations repo"
|
||||
- "Create a new repo called 'data-pipeline' under the mpm org"
|
||||
- "Merge PR #42 in mpm/frontend"
|
||||
- "Update the CHANGELOG.md in main with today's release notes"
|
||||
|
||||
## Configuration
|
||||
|
||||
- **Server**: https://git.mpm.to
|
||||
- **API version**: v1
|
||||
- **Auth**: API token (embedded in plugin)
|
||||
|
||||
## Security note
|
||||
|
||||
This plugin contains an embedded API token with access to git.mpm.to. Treat this `.plugin` file with the same care as any credential. Do not share it outside the organization.
|
||||
|
||||
Reference in New Issue
Block a user