Skip to main content
Glama
A1-x-Tech

A1 Google Contacts MCP

by A1-x-Tech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to A1 Google Contacts MCP

No user-submitted related servers found.

    Related Servers

    • MCP Google Contacts Server

      puzne2000
      A
      license
      Not graded
      quality
      D
      maintenance
      Gives AI assistants access to Google Contacts, supporting listing, searching, creating, updating, and deleting contacts, as well as searching Google Workspace directories.
      MIT

    • contacts-mcp

      Bluesun-Networks
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to manage contacts with full CRUD, dedup, merge, import/export, sync with Google/Apple/CardDAV, and git-backed rollback.
      5 npm
      AGPL 3.0

    • MCP Google Workspace

      199-mcp
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables comprehensive management of Google Calendar, Contacts, and Gmail through AI systems. Supports full CRUD operations including creating/updating/deleting events, managing contacts, sending emails, organizing with labels, and batch operations with OAuth2 authentication.
      106 npm
      MIT

    • contactapi

      kozmos-tech
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI clients to manage contacts through CRUD operations (list, get, create/upsert by email, update, delete) with OAuth 2.1 authentication.
      1
      MIT

    • Google Contacts MCP Server

      OffleashXYZ
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to access and search Google Contacts through per-user OAuth authentication on serverless AWS Lambda. Provides read-only access to personal contacts with zero data storage and real-time API queries.
      60 npm
      2
      MIT
    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

    A4.4/5.0

    Scored across 19 tools

    Disambiguation5/5

    Every tool targets a distinct resource and action: contact CRUD, group CRUD, member management, and other-contacts handling are clearly separated. Batch variants are explicitly prefixed with batch_, and raw_request is framed as an escape hatch rather than a competing operation.

    Naming Consistency4/5

    The vast majority follow a consistent verb_noun pattern: list_contacts, create_contact, update_contact_group, batch_delete_contacts. raw_request is the lone naming outlier, but it is clearly an escape-hatch utility and does not create real confusion.

    Tool Count4/5

    Nineteen tools is above the ideal 3-15 range, but the number is justified by splitting single and batch operations plus covering groups and other contacts. It feels slightly heavy rather than bloated, and each typed tool has a distinguishable purpose.

    Completeness4/5

    Contacts, contact groups, member management, search, list, and batch operations are all covered. Minor gaps remain: contact photos are only reachable through raw_request, and other-contacts are intentionally limited to list/copy, but there are no dead ends for the core domain.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources