M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionClaspCommand-line tool for developing Google Apps Script projects locallyGitHub MCP ServerGitHub's official MCP server for managing repos, issues, PRs, and workflows via natural language
FMRS63 / 100 · C76 / 100 · B
Reliability8 / 2013 / 20
Security and permissions13 / 2014 / 20
Maintenance15 / 2018 / 20
Documentation15 / 2017 / 20
Setup experience12 / 2014 / 20
Best for
  • Developers who want to develop Google Apps Script locally with their own editor and Git workflow
  • Teams that need version control and collaboration for Apps Script projects
  • Users who want an AI coding agent (Claude Code, Gemini CLI) to manage Apps Script projects directly
  • Teams that want an AI assistant to directly operate on GitHub repos and collaboration workflows
  • Users already in the GitHub Copilot ecosystem who want a zero-deployment remote option
Not for
  • General cloud storage or database integrations unrelated to Apps Script
  • Scenarios requiring vendor-backed official support SLAs (the README explicitly states it is not an officially supported Google product)
  • Projects relying on clasp 2.x's built-in TypeScript transpilation (removed in 3.x — use a bundler like Rollup instead)
  • Non-interactive service-account authentication (README marks this as experimental/not currently working)
  • Scenarios where you don't want the assistant to have write access to repos (enable only read-only toolsets)
  • Environments with strict network isolation for private repos that can't reach the official remote endpoint
Required permissions
  • Google OAuth access to read/write the user's Apps Script projects (script.projects, script.deployments, script.webapp.deploy, etc.)
  • Google Drive read-only metadata and file access (drive.metadata.readonly, drive.file) to list and create bound scripts
  • Google Cloud Service Usage API access to list/enable/disable advanced services
  • Cloud Logging read access to fetch script execution logs
  • Local credential storage in `.clasprc.json` (containing OAuth tokens) in the home or working directory
  • A personal access token (PAT) or OAuth App token; effective scope depends on the token's own permissions
  • Enabling toolsets like actions/issues/pull_requests grants write access — request tokens on a least-privilege basis
Risks and side effects
  • `clasp push` always replaces the entire remote project content (the Apps Script API has no atomic or per-file operations), so mistakes can overwrite remote code
  • OAuth scopes are broad — covering scripts, Drive files, logging, and API management — so leaked credentials (especially custom ones saved via `--creds`) carry meaningful exposure
  • MCP mode is explicitly experimental; the README states it currently offers only a limited tool subset and behavior may change
  • Service-account / application-default-credentials support is explicitly marked experimental and 'NOT WORKING,' and should not be relied on for production automation
  • Write toolsets (creating/merging PRs, triggering workflows) can cause accidental changes if the token is overscoped — try a read-only toolset first
  • In hosted mode, credentials travel via the Authorization header — make sure the client-to-api.githubcopilot.com connection is trusted
Supported clientsClaude Code, Gemini CLIClaude Desktop, Claude Code, VS Code, Cursor, Windsurf, JetBrains IDEs, Zed, Amp
Tools015