taylorwilsdon/google_workspace_mcp - Open Source PR Review Scorecard

Control Gmail, Google Calendar, Docs, Sheets, Slides, Chat, Forms, Tasks, Search & Drive with AI - Comprehensive Google Workspace MCP Server & CLI Tool

C-Rank Grade: B (Solid) - 53/100

External PR Merge Rate: 43%

Response Time: 2d

First Timer Success: 42%

Frequently Asked Questions

Is taylorwilsdon/google_workspace_mcp welcoming to first-time open-source contributors?

taylorwilsdon/google_workspace_mcp has a recorded first-timer success rate of 41.7%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.

How fast can I expect code review feedback on my pull request?

Maintainers in taylorwilsdon/google_workspace_mcp respond to incoming external pull requests in approximately 47.6 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 53.4 C-Rank™ score (B Tier) represent?

The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 53.4 places taylorwilsdon/google_workspace_mcp in the B tier.

What is the external contributor pull request merge rate for taylorwilsdon/google_workspace_mcp?

The external contributor pull request merge rate for taylorwilsdon/google_workspace_mcp is 43.3%, based on public PR activity from non-core contributors.

Are there Good First Issues available in taylorwilsdon/google_workspace_mcp?

taylorwilsdon/google_workspace_mcp currently has 4 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".

taylorwilsdon
taylorwilsdon/google_workspace_mcpB•Solid3.3k
GitHub
Back to Explorer
taylorwilsdon

taylorwilsdon/google_workspace_mcp

3,281
InactiveB•Solid(53/100)Python

Control Gmail, Google Calendar, Docs, Sheets, Slides, Chat, Forms, Tasks, Search & Drive with AI - Comprehensive Google Workspace MCP Server & CLI Tool

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Constructive Code Reviewer

Warmth Score
8.2/10
Patience Score
8.4/10
Nitpick Rate
22%

Balanced & professional review environment in taylorwilsdon/google_workspace_mcp. Maintains strict focus on technical quality and test standards.

Top PR Submission Do's

  • •Add unit tests with >80% coverage for modified code paths
  • •Use conventional commit messages and clean branch names
  • •Link relevant GitHub issue ID in PR description pre-flight checklist

Top PR Friction Pitfalls (Don'ts)

  • •Do not submit unlinked PRs without referencing an existing issue
  • •Do not mix refactoring and feature logic into a single commit
  • •Do not ping maintainers repeatedly within 24 hours of opening
Response Velocity
1 days+
Standard maintainer review cycle

Average Response Latency

Tracks hours until a maintainer leaves a review, comment, or PR response.

Merge Efficiency
43.3%
Moderate PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
41.7%
Accepts new contributor PRs

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
55 core
Highly collaborative maintainer core
Diagnostic Health HUD
43.3%
Merge Gauge
41.7%
1st-Timer
Community Vibe30/100

Embed C-Rank Badge

Show contributors that your repository actively reviews and merges external pull requests.

GetMerged C-Rank badge for taylorwilsdon/google_workspace_mcp
[![GetMerged C-Rank](https://getmerged.abhishekco.de/api/badge/taylorwilsdon/google_workspace_mcp)](https://getmerged.abhishekco.de/taylorwilsdon/google_workspace_mcp?utm_source=github&utm_medium=badge)

Active Good First Issues (4)

View on GitHub

Is your feature request related to a problem? Please describe. Since I can't use git with Google Docs, I need a way of reviewing the agent changes before accepting them. Or at least to see clearly what changed. I find the suggestion mode in Docs would be adequate for this. Describe the solution you'd like Being able to use the Docs API to do edits in suggestion mode, instead of direct edits. That way we can see what changed in the file before accepting the change. Describe alternatives you've considered Git doesn't work for Google Docs, AFAIK. Tell the agent to add the changes in comments, and then copy pasting them myself. Direct edits, but then I lose track of what's changed and forces me to re-read everything looking for anything that might have been wrong. Additional context Docs API supports Suggestions. PS. There is no community/Discord to ask questions about this project, is it?

📅 Opened Jun 18, 2026💬 4 comments
Quality: 55/100Contribute

Use case Surfacing one Drive file in more than one folder — without duplicating its bytes — is done with a shortcut. Since Drive removed multi-parenting (Sept 2020) a file has a single parent, so a shortcut is the supported "appears here too / live pointer to the canonical file" mechanism. It's the natural primitive for "publish this Doc into a shared/output folder while the original stays the source of truth." Gap (verified at v1.21.0 and on main) gdrive/drive_tools.py can resolve / chase existing shortcuts (resolve_drive_item, and shortcut as a file_type filter value), but no @server.tool creates one. create_drive_file always uploads media with the upload mime == body.mimeType, so it can't create a metadata-only shortcut file. Drive API supports it files.create( body={ "name": shortcut_name, "mimeType": "application/vnd.google-apps.shortcut", "parents": [parent_folder_id], "shortcutDetails": {"targetId": target_id}, }, supportsAllDrives

📅 Opened May 29, 2026💬 0 comments
Quality: 30/100Contribute

Is your feature request related to a problem? Please describe. I am planning to run it on web where I will have multiple sites using single instance of this server. Different sites will have different subsets of tools available to them. The issue is there is no way to configure toolsets once the server is running. Describe the solution you'd like Accept toolsets in either query params (like posthog) or headers (like github) Ref: https://github.com/github/github-mcp-server/blob/main/docs/remote-server.md#optional-headers https://github.com/PostHog/posthog/tree/master/services/mcp#feature-filtering Describe alternatives you've considered Additional context

📅 Opened Feb 25, 2026💬 5 comments
Quality: 45/100Contribute

Summary Google Docs, Slides, and Forms all have their batch_update_* tools (batch_update_doc, batch_update_presentation, batch_update_form), but Google Sheets has no equivalent batch_update_spreadsheet tool. This means there is currently no way to copy a row (or range) with formulas and formatting preserved — a fundamental Sheets operation. Use Case I track daily work data in a Google Sheet with ~40 columns per row. Many columns contain formulas (calculated totals, percentages, verification checks) and custom formatting (currency, colors, borders). My workflow: Copy the previous day's row to get all formulas and formatting Fill in only the manual input cells (date, hours, payments, etc.) Currently, step 1 is impossible through the MCP. modify_sheet_values can only write raw values or formulas as strings — it cannot copy a range while preserving both formulas and formatting in one operation. I have to manually copy the row in the Google Sheets UI, then use the MCP for step 2. Prop

📅 Opened Feb 20, 2026💬 0 comments
Quality: 30/100Contribute
Looking for more Python beginner tasks?Explore Python GFI

Contributor Community Vibe Feedback

Rate what actually matters after opening a pull request here.

Have you contributed to this repo?

Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.

3 ratings required
Maintainer helpfulness
Review speed
Beginner friendliness

Contributor Compatibility & Review Speed Analysis for taylorwilsdon/google_workspace_mcp

When evaluating whether to contribute to taylorwilsdon/google_workspace_mcp, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.

Currently, maintainers of taylorwilsdon/google_workspace_mcp acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 43.3% were successfully merged into the primary branch.

Frequently Asked Questions - Contributing to taylorwilsdon/google_workspace_mcp

01

Is taylorwilsdon/google_workspace_mcp welcoming to first-time open-source contributors?

taylorwilsdon/google_workspace_mcp has a recorded first-timer success rate of 41.7%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.

02

How fast can I expect code review feedback on my pull request?

The initial maintainer response time averages ~1 days+. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 53.4 C-Rank™ score represent?

The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 53.4 places taylorwilsdon/google_workspace_mcp in the Solid tier.

04

What is the external contributor pull request merge rate for taylorwilsdon/google_workspace_mcp?

The external pull request merge rate is 43.3%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.

05

Are there beginner Good First Issues open in taylorwilsdon/google_workspace_mcp?

Yes, taylorwilsdon/google_workspace_mcp currently has 4 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.

GetMerged C-Rank™ Indexing Standard

All metrics displayed for taylorwilsdon/google_workspace_mcp are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.