My Claude Code setup: the tooling I build for it, and the configuration I carry between machines. This repo doubles as a plugin marketplace, so anything here that ships as a plugin can be installed directly.
Formerly walkerhughes/mcps, back when it only held MCP servers.
Model Context Protocol servers that give agents direct access to external services. Each lives in its own subdirectory with its own setup, tests, and docs.
| Server | What it connects to | Plugin |
|---|---|---|
harbor-mcp |
The Harbor hub: evaluation jobs, trials, uploads, and published packages. | yes |
tastytrade-mcp |
The TastyTrade Open API: brokerage account, market data, and order management (12 tools). | not yet |
They follow Honeycomb's MCP, easy as 1-2-3 guidance: a few curated tools built around real questions rather than raw API endpoints, responses shaped for a model instead of a UI, and typed schemas that steer the model toward valid calls.
Run these as two separate commands, not as one paste: the first opens a prompt that expects only the owner/repo.
/plugin marketplace add walkerhughes/claude
/plugin install harbor-mcp
The non-interactive equivalents are more reliable, and are the only way to move an existing install to a new version, since claude plugin install no-ops when the plugin is already present:
claude plugin marketplace update walkerhughes && claude plugin update harbor-mcp@walkerhughesPlugins require uv on your PATH. The first launch builds the server's environment, so give it a moment before the tools appear. A plugin update needs a Claude Code restart, not just an /mcp reconnect. See each server's README for credentials.
Bump version in the plugin's .claude-plugin/plugin.json in the same PR. Claude Code extracts an installed plugin to a cache path keyed by that version, so if it does not change, the cache is never refreshed and users keep running the old code however many times they update or reinstall. The change is invisible rather than broken. The plugin version workflow enforces this.
claude/
├── .claude-plugin/ # marketplace manifest
├── harbor-mcp/
└── tastytrade-mcp/
Each subdirectory is self-contained: its own README.md covers install, credentials, tests, and tools. CI runs per subdirectory via paths filters, so a change to one never runs another's suite.