Skip to main content
Glama
onesmartguy

Agentic Bits Claude Plugin

by onesmartguy
README.md
# @agentic-bits/claude-plugin

Claude Code MCP plugin that adds a **live git branch status bar** to the Claude footer.

```
⎇ payment-service:feature/PAYM-43  |  payments-ui:main  |  payments-infra:main
```

---

## Features

- **Branch status bar** — shows the current git branch for every configured repo in the Claude footer
- **Master toggle** — enable/disable the status bar entirely
- **Reference repo toggle** — show/hide read-only reference repos separately from active dev repos
- **Per-repo visibility** — show or hide individual repos without removing them from config
- **MCP tools** — manage everything via natural language in Claude chat

---

## Quick start

```bash
git clone git@gitlab.com:raptortech1/agentic-bits-claude-plugin.git
cd agentic-bits-claude-plugin
npm install && npm run build
bash scripts/setup.sh
```

Then add the MCP server to your project's `.mcp.json`:

```json
{
  "mcpServers": {
    "agentic-bits": {
      "command": "node",
      "args": ["/path/to/agentic-bits-claude-plugin/dist/index.js"]
    }
  }
}
```

See **[docs/setup-guide.md](docs/setup-guide.md)** for full instructions including payment-service workspace pre-population.

---

## MCP tools

| Tool | What it does |
|------|-------------|
| `get_branch_status` | Live branch status for all visible repos |
| `add_repo` | Add a repo to track |
| `remove_repo` | Remove a repo |
| `set_repo_visibility` | Show/hide a specific repo |
| `toggle_statusbar` | Enable/disable the status bar |
| `toggle_reference_repos` | Show/hide reference repos |
| `list_repos` | List all repos and their config |
| `get_config_info` | Dump full config + path |

---

## Config file

`~/.config/agentic-bits/plugin.json`

```json
{
  "statusbar": {
    "enabled": true,
    "showReferenceRepos": false
  },
  "repos": [
    {
      "path": "/absolute/path/to/repo",
      "label": "my-repo",
      "type": "active",
      "show": true
    }
  ]
}
```

---

## Publishing

Tag a commit to publish to npm:

```bash
git tag v1.0.0 && git push origin v1.0.0
```

Pipeline: typecheck → build → npm publish → GitLab release.

TDQS

A3.8/5.0

Scored across 10 tools

Disambiguation5/5

Each tool has a clearly distinct purpose with no overlap. For example, add_repo and remove_repo handle opposite operations, while get_branch_status and check_repo_branch provide branch information at different scopes (all repos vs. single repo). The descriptions make it easy to differentiate between configuration tools (get_config_info, toggle_statusbar), repository management tools (add_repo, remove_repo, list_repos), and status/visibility controls (set_repo_visibility, toggle_reference_repos).

Naming Consistency5/5

All tools follow a consistent verb_noun naming pattern throughout (e.g., add_repo, check_repo_branch, get_config_info). The verbs are descriptive and appropriate for their actions (add, check, get, list, remove, set, toggle, validate), and nouns clearly indicate the target resource (repo, branch, config, statusbar). There are no deviations in style or convention.

Tool Count5/5

With 10 tools, this server is well-scoped for managing git repositories in a status bar context. Each tool earns its place by covering essential operations: repository configuration (add, remove, list), status checks (branch, validation), visibility controls (toggle, set), and system settings (config, statusbar toggle). The count is neither too sparse nor bloated, fitting the domain perfectly.

Completeness5/5

The tool set provides complete coverage for the domain of managing git repositories in a status bar. It includes CRUD operations for repositories (add, remove, list), status monitoring (branch checks, path validation), configuration management (get config, toggle statusbar), and visibility controls (set visibility, toggle reference repos). There are no obvious gaps; agents can perform all expected workflows without dead ends.

Maintenance

ActivityInactive
ResponsivenessNo issues