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.
      127 npm
      MIT

    • contactapi

      kozmos-tech
      A
      license
      Not graded
      quality
      D
      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.
      64 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 25 tools

    Disambiguation4/5

    Most tools have clearly distinct resource+action purposes, and descriptions sharply delineate single vs batch variants (get_contact vs batch_get_contacts) and saved vs auto-saved contacts (list_contacts vs list_other_contacts). The only mild overlap is between the batch_* and singleton counterparts and among the auth-flow tools, but the detailed descriptions resolve these boundaries well.

    Naming Consistency4/5

    Nearly all tools follow a predictable snake_case verb_noun pattern (list_contacts, get_contact, create_contact, batch_update_contacts, modify_group_members). Minor deviations exist in the auth group where two tools are noun-phrased (setup_instructions, auth_status) rather than verb-led, but the scheme stays readable and consistent overall.

    Tool Count4/5

    At 25 tools the set sits at the heavy end of the range, but the domain legitimately spans auth onboarding, contact CRUD, batch operations, groups, other-contacts, and a raw escape hatch, so nearly every tool earns its place. It is slightly over-provisioned (six auth/setup tools) rather than bloated.

    Completeness5/5

    The surface covers the full lifecycle: auth (setup, login, status, logout), contact CRUD plus batches, group CRUD plus membership modification, other-contacts listing/copying, and a raw_request escape hatch. The only non-typed capability (contact photos) is explicitly routed through raw_request, leaving no real dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources