A collection of frameworks, plugins, and MCP servers for building and deploying personal productivity tools powered by AI agents.
Everything here follows an MCP-first design — tools are self-documenting, agent-discoverable, and work with Claude, Gemini, and any MCP-compatible client. CLI is optional.
| Repo | What it does |
|---|---|
| gapp | Deploy Python MCP servers to Google Cloud Run with auth, secrets, and credential mediation. CLI + MCP + Claude plugin. |
| app-user | Auth and user data management for multi-user web apps. JWT auth, admin endpoints, per-user data storage. |
| claude-plugin-creator | Scaffold Claude Code plugins with self-installing dependencies, MCP server config, and hooks. |
| claude-plugins | Plugin marketplace for Claude Code. Install community and personal plugins with claude plugin install. |
| Repo | What it does |
|---|---|
| food-agent | Food logging with nutrition tracking. Timezone-aware daily logs, food catalog, voice-friendly via MCP. |
| notes | Note-taking backed by Google Sheets. SDK, CLI, and MCP server with optional AppSheet integration. |
| bills-agent | Bill tracking with Monarch Money cross-reference. Claude Code plugin. |
| pay-calc | Pay and tax projection tools. |
| Repo | What it does |
|---|---|
| monarch-access | Monarch Money financial data — accounts, transactions, budgets. SDK, CLI, and MCP server. |
| ticktick-mcp | TickTick task management — projects, tasks, completion. MCP server. |
| gworkspace-access | Google Workspace — Gmail, Drive, Docs, Calendar, Chat. MCP server. |
| dotfiles-manager | Dotfile management using a bare git repo backed by GitHub. CLI and MCP server. |
| Repo | What it does |
|---|---|
| agentic-consult | Developer workstation management — git repo status, Drive backups, Gemini API with local file context, security scanning. |
All MCP servers follow a common pattern:
my-app/
sdk/ # Business logic — all behavior lives here
mcp/ # Thin MCP layer — tool schemas, calls SDK
cli/ # Optional thin CLI — calls SDK, formats output
SDK-first: Every feature is implemented in the SDK layer, ensuring consistency whether accessed via MCP, CLI, or direct import.
Deployment: Servers run locally via stdio for low-latency agent integration, or deploy to Cloud Run via gapp for remote/mobile access.
Plugins: Claude Code plugins bundle MCP servers with auto-installing dependencies via the self-installing pattern. Install from the marketplace or point Claude at any plugin repo directly.
All servers follow an SDK-first pattern: business logic lives in an
importable sdk/ package, with thin MCP and CLI wrappers that call into
it. This ensures consistent behavior across all interfaces and enables
cross-repo SDK consumption (e.g., gworkspace-access's SDK is imported
by agentic-consult). Local tools run via stdio and pipx; cloud tools
add mcp-app for HTTP auth and
gapp for Cloud Run deployment.
See framework/ for the full architecture guide — foundations, the SDK-first pattern, constraints, examples, and solution repo conventions.
Design references:
- docs/mcp-framework.md — why we use the official MCP Python SDK over standalone FastMCP
- docs/mcp-proxy.md — MCP tool proxying and server-to-server orchestration