josephjerryrhule

josephjerryrhule/google-workspace-mcp

Agent

Stand up the repo, tooling, and an MCP server skeleton with both transports stubbed, so every other agent has a place to register tools.

josephjerryrhule/google-workspace-mcp

Agent

Implement Google OAuth 2.0 user consent, scope management, and encrypted per-user token storage, then complete the getGoogleClient factory so tool agents get authed API clients.

josephjerryrhule/google-workspace-mcp

Agent

Implement the Google Sheets tool set. sheetsappendrows is the single most important deliverable in the project (it is what lets the daily lead task write to the CRM). Prioritize it.

josephjerryrhule/google-workspace-mcp

Agent

Implement Google Docs tools for creating and template-filling documents (proposals, contracts, briefs).

josephjerryrhule/google-workspace-mcp

Agent

Implement Google Slides tools for creating decks and template-filling slides (pitch decks, the agency profile).

josephjerryrhule/google-workspace-mcp

Agent

Provide file discovery (name to fileId), file creation/copy, and sharing, so the Sheets/Docs/Slides tools can target files by name and hand results to teammates.

josephjerryrhule/google-workspace-mcp

Agent

Wrap the finished stdio server as a remote MCP server with an OAuth 2.1 authorization layer so it appears as a custom connector in claude.ai and Cowork and can be shared with the team.

josephjerryrhule/google-workspace-mcp

Agent

Own the safety and quality layer that every other agent writes into: write guardrails, the audit log, the test harness, and an eval set. Stand the harness up early so other agents integrate against it from day one.