Skip to main content
Glama
sam-ent

Apps Script MCP

by sam-ent
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Apps Script MCP

No user-submitted related servers found.

    Related Servers

    • claude-appsscript-pro

      overdozer1124
      A
      license
      D
      quality
      C
      maintenance
      Enables AI-driven development and management of Google Apps Script projects, including autonomous system construction, real-time debugging, and spreadsheet operations through natural language.
      76
      6
      MIT

    • GAS MCP

      BingHong-Xu
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to directly read and write Google Apps Script projects, manage versions and deployments, inspect execution logs and failures, and run functions through natural language, with user-owned OAuth authorization and self-hosted deployment.
      -

    • GAS MCP

      jychun2005
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to directly read and write Google Apps Script projects, manage versions, deployments, and inspect execution logs to debug triggers.
      -

    • Google Apps Script MCP Server

      Utakata
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables comprehensive management of Google Apps Script projects, including project creation, file operations, and web app deployments. It features a security-first design with encrypted property management and automated security auditing for GAS environments.
      1
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 50 tools

    Disambiguation4/5

    Most tools are clearly distinct by resource type (Docs, Sheets, Drive, Calendar, Gmail, Scripts) and action (create, get, update, delete, list, search). However, some overlap exists: append_doc_text_tool and modify_doc_text_tool both modify Docs, and append_sheet_values_tool and update_sheet_values_tool both write to Sheets, which could cause confusion without careful reading of descriptions.

    Naming Consistency5/5

    Tool names follow a highly consistent verb_noun pattern throughout (e.g., create_doc, get_doc_content, update_sheet_values, list_script_projects). All use snake_case with clear, descriptive verbs aligned to CRUD operations, making the set predictable and easy to navigate.

    Tool Count2/5

    With 50 tools, the count is excessive for a single server, making it overwhelming and difficult for agents to navigate efficiently. While the scope covers multiple Google services (Docs, Sheets, Drive, Calendar, Gmail, Apps Script), the sheer volume suggests poor scoping—many tools could be consolidated or split into focused sub-servers.

    Completeness5/5

    The tool set provides comprehensive coverage across Google services, including full CRUD operations for Docs, Sheets, Drive files, Calendar events, and Script projects, plus search, listing, and specialized actions like authentication and trigger generation. No obvious gaps exist; agents can perform end-to-end workflows without dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources