Skip to content

fix: update Google Workspace MCP catalog entry to use original repo#369

Draft
Aqil-Ahmad wants to merge 9 commits intoarchestra-ai:mainfrom
Aqil-Ahmad:googleWorkspaceMCP
Draft

fix: update Google Workspace MCP catalog entry to use original repo#369
Aqil-Ahmad wants to merge 9 commits intoarchestra-ai:mainfrom
Aqil-Ahmad:googleWorkspaceMCP

Conversation

@Aqil-Ahmad
Copy link
Contributor

@Aqil-Ahmad Aqil-Ahmad commented Feb 16, 2026

fixes #archestra-ai/archestra#2717

Summary

  • update Google Workspace MCP catalog entry from forked iskhakov/google_workspace_mcp to original taylorwilsdon/google_workspace_mcp
  • remove problematic env vars and --transport streamable-http flag

unrelated changes:

  • fix McpbManifestSchema.shape crash in schemas.ts by unwrapping ZodEffects to inner ZodObject
  • fix link.. and rename
image image

/claim #archestra-ai/archestra#2717

Copilot AI review requested due to automatic review settings February 16, 2026 21:11
@vercel
Copy link

vercel bot commented Feb 16, 2026

@Aqil-Ahmad is attempting to deploy a commit to the Archestra projects Team on Vercel.

A member of the Team first needs to authorize it.

Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates MCP catalog data to reference the original Google Workspace MCP repository, and adjusts catalog tooling/schema handling to avoid a Zod schema shape access crash.

Changes:

  • Switch Google Workspace MCP catalog references from iskhakov/google_workspace_mcp to taylorwilsdon/google_workspace_mcp and simplify its server invocation/env.
  • Fix McpbManifestSchema.shape crash by unwrapping the inner schema before building the derived manifest schema.
  • Rename the Archestra coding agent catalog entry and update the catalog server list accordingly.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 2 comments.

File Description
app/app/mcp-catalog/schemas.ts Unwraps refined McpbManifestSchema to access object shape for derived schema construction.
app/app/mcp-catalog/data/mcp-servers.json Updates catalog server URL entries (Google Workspace + Archestra coding agent).
app/app/mcp-catalog/data/mcp-evaluations/taylorwilsdon__google_workspace_mcp.json Updates evaluation metadata/installation args to match the original upstream repo.
app/app/mcp-catalog/data/mcp-evaluations/archestra-ai__archestra-coding-agent.json Renames the evaluation name to the canonical owner__repo form.

@Aqil-Ahmad
Copy link
Contributor Author

@joeyorlando please review!

also i've made some unrelated changes but those were needed.

@Aqil-Ahmad
Copy link
Contributor Author

Recording.2026-02-17.022831.mp4
Recording.2026-02-17.023001.mp4

@joeyorlando joeyorlando changed the title Fix: update Google Workspace MCP catalog entry to use original repo fix: update Google Workspace MCP catalog entry to use original repo Feb 16, 2026
Copy link
Contributor

@joeyorlando joeyorlando left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for tackling this @Aqil-Ahmad! The core fix (switching to the original taylorwilsdon repo and removing the problematic flags/env vars) looks correct and should resolve #2717. A few things to address though:

schemas.ts change is breaking CI

All three CI jobs are failing with TypeError: Right-hand side of 'instanceof' is not an object. This project uses Zod v4 (^4.3.6), which doesn't export ZodEffects or ZodObject as classes — so instanceof z.ZodEffects / instanceof z.ZodObject doesn't work. That's a Zod v3 pattern.

Since McpbManifestSchema.shape works fine on main today, I'd recommend dropping this change entirely from this PR. If it does become a problem in the future (e.g. after a @anthropic-ai/mcpb upgrade), we can address it in a separate PR with a Zod v4-compatible approach.

Unrelated changes

The coding agent rename ("coding" → full GitHub URL) and the evaluation name field change are unrelated to the Google Workspace fix. Could you split those into a separate PR to keep this one focused on the bug fix?

Evaluation data

The evaluation file was renamed from iskhakov__* to taylorwilsdon__*, but the GitHub metrics inside (stars, contributors, etc.) still reflect the old fork's data. Worth re-running pnpm catalog:evaluate against the taylorwilsdon repo to get accurate numbers.

TL;DR — to get this mergeable:

  1. Revert the schemas.ts changes
  2. Split out the coding agent rename into its own PR
  3. Consider re-running evaluation for the new repo

joeyorlando

This comment was marked as duplicate.

Copy link
Contributor

@joeyorlando joeyorlando left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great now! All previous feedback addressed:

  • schemas.ts and coding agent changes reverted — PR is focused on the Google Workspace fix only
  • Evaluation re-run with fresh metrics from the taylorwilsdon repo (1418 stars, 67 contributors — much more accurate)
  • CI is all green

Thanks for iterating on this @Aqil-Ahmad!

@joeyorlando joeyorlando marked this pull request as draft February 19, 2026 23:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

Comments