Skip to main content
Glama
Sign In
Infomaniak

Infomaniak Contact MCP Server

Official
by Infomaniak
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to Infomaniak Contact MCP Server

No user-submitted related servers found.

    Related Servers

    • contacts-mcp

      atfinke
      A
      license
      A
      quality
      D
      maintenance
      Local MCP server that exposes Apple Contacts data, enabling phone, email, and name lookups via a helper app.
      5
      4 npm
      MIT

    • carddav-mcp

      dominik1001
      A
      license
      Not graded
      quality
      D
      maintenance
      A CardDAV MCP server that exposes contacts and address books as tools for AI assistants.
      10 npm
      1
      MIT

    • Google Contacts MCP

      medeiroz
      A
      license
      Not graded
      quality
      C
      maintenance
      A local MCP server that enables managing Google Contacts via the People API through tools for listing, searching, getting, creating, updating, deleting, and counting contacts. It requires an externally stored OAuth token and confirms all write operations.
      113 npm
      MIT

    • MCP Google Contacts Server

      RayanZaki
      A
      license
      A
      quality
      D
      maintenance
      A Machine Conversation Protocol server that enables AI assistants to manage Google Contacts and search Google Workspace directories, providing tools for listing, creating, updating, and deleting contacts within your Google account.
      9
      33
      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

    B3.3/5.0

    Scored across 2 tools

    Disambiguation4/5

    contact_list and contact_search are mostly distinct: one enumerates all contacts, the other filters by query. There is minor overlap since listing all contacts is a degenerate search, but an agent can reasonably choose between them.

    Naming Consistency5/5

    Both tools follow a clear and consistent contact_verb pattern (contact_list, contact_search). The naming is predictable and easy to generalize.

    Tool Count3/5

    Two tools is thin for a contact management server, which typically needs more operations. The count is not extreme, but it feels under-scoped for the domain.

    Completeness2/5

    The surface only supports reading and searching; there is no create, update, delete, or get-by-ID operation. This leaves significant gaps for any contact lifecycle workflow.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources