Claude-Code
My Claude Code Setup, From Zero
Installing Claude Code and wiring it up the way I actually use it: CodeGraph for code intelligence, MCP servers, plugin marketplaces, LSP, GitHub Spec Kit, and Herdr to keep the agents running.
A fresh Claude Code install is useful. A configured one is a different tool entirely. The gap between the two is maybe fifteen minutes of setup — a code index, a handful of MCP servers, two plugin marketplaces, a spec workflow, and a runtime to keep it all alive — and I keep re-doing it every time I move to a new machine. So here it is written down, in the order I run it.
cartographer-mcp: give Claude Code a map of your GitLab architecture
An MCP server that crawls GitLab groups to build a service catalog with dependency graphs, queryable from Claude Code
Every Claude Code session that involves more than one repo starts with the same monologue: “we have a payment service that calls user-service via REST, which publishes events that notification-service consumes, and oh by the way the platform team owns auth-service…” By the time I’ve finished the briefing, I’ve burned tokens and patience.
cartographer-mcp is my attempt at fixing that. It crawls your GitLab organization, builds a service catalog with a dependency graph, and exposes it as MCP tools so Claude Code already knows the shape of your architecture.
claude-plugins: a personal Claude Code marketplace for DevOps and Go
A curated set of Claude Code plugins — agents, commands, and skills — covering DevOps, software engineering, and modern Go development.
Once you start using Claude Code seriously, you accumulate prompts. A snippet that always produces the right golangci.yml. A spell that turns “I need a GitLab CI pipeline” into a working .gitlab-ci.yml. A code-review checklist you keep pasting in. After enough copy-paste, the obvious move is to package those into proper Claude Code plugins. That’s what claude-plugins is.
gitlab-mcp: drive GitLab from Claude Code without leaving the terminal
An MCP server that exposes GitLab issues, labels, epics, and CI/CD pipelines as tools Claude Code can call directly
I spend a lot of time in Claude Code, and a lot of time in GitLab. The constant tab-switching between the two — copy an issue ID, paste it into a prompt, jump back to read a job log, paste that too — got tiresome. So I wrote gitlab-mcp, a Model Context Protocol server that lets Claude Code talk to GitLab directly.
postgresql-mcp: a read-only PostgreSQL bridge for Claude Code
An MCP server that lets Claude Code inspect schemas, run SELECT queries, and explain plans against your PostgreSQL databases — safely
A surprising amount of debugging boils down to “let me check the database.” Schema lookups, sample row counts, “is this index actually being used,” EXPLAIN plans. None of that is hard to do in psql, but pulling Claude Code into the loop means copy-pasting schemas and query results back and forth, which gets old.
postgresql-mcp is an MCP server that gives Claude Code direct, read-only access to PostgreSQL. Claude does the inspection, you keep the conversation flowing.