ContactZapp

app.contactz由 contactz.app 发布官方发布者v1.0.5更新于 Nov 7, 2026

Keeps your contacts in sync across Google, Microsoft, Apple and CardDAV, and cleans up duplicates.

已验证Streamable HTTP可网页运行效率与工作流文件与存储沟通与协作

概览

AI 生成的概览

ContactZapp 在 Google、Microsoft、Apple 和 CardDAV 之间同步联系人，并让助手查找、读取、新建和修改联系人、轮询联系人事件。

可以做什么
  • 按邮箱、电话号码或文本搜索查找联系人
  • 按 id 或 publicId 读取单个联系人
  • 新建联系人，当用户的 Auto-Merge 级别匹配时自动合并到已有联系人
  • 修改联系人字段，改动会同步到该联系人所在的每个双向账户
  • 启动同步，等同于 ContactZapp 中的“立即同步”
  • 按类型列出事件（最新在前），供自动化轮询
适用场景
适合让助手在跨多个服务商的通讯录中查找、新增或更新联系人，也适合需要轮询联系人新建、更新、删除事件来触发自动化的场景。
运行要求
远程 MCP 端点，位于 app.contactz.app，使用 streamable HTTP。需要 ContactZapp API 密钥，在“设置 › 高级”中创建，通过 Authorization 请求头发送，值以 Bearer 开头。无需环境变量或本地安装包。
安装前请注意
API 密钥是敏感凭据，通过 Authorization 请求头发送，并带有签发时授予的权限范围。新建和修改联系人会写入真实数据：改动会传播到每个双向同步账户，新建时可能合并进已有联系人。同步和编辑会以用户名义及所用密钥或应用记录在历史中。联系人数据会与已连接的 Google、Microsoft、Apple 和 CardDAV 账户交换。

安装

在 SourceWeft 中

  1. 打开 控制台中的 ContactZapp，将其添加到工作区。
  2. 连接 Authorization token 凭据。它们会被私密存储，绝不会在公开页面上展示。
  3. 为需要使用其工具的对话启用该服务。

Web executable，通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体，或 SourceWeft 对话中。智能体会读取该服务器的安装指南，先向你展示发布者、端点和登录方式，经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/app.contactz%2Fcontactzapp/install.md，并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前，先告诉我它的发布者、端点和登录方式，等我确认。不要把 API 密钥写进命令或我会提交的文件；问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。

{
  "mcpServers": {
    "contactzapp": {
      "type": "http",
      "url": "https://app.contactz.app/api/v1/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

README

该仓库没有 README。

工具

7

api_key_check

API key – Check

Returns the user the request acts for, the user's plan and the scopes of the API key or connected app that made it. Any live key or access token can call it, so call it to test one.

无需输入参数。

contact_find

Contact – Find

Finds the user's contacts by email address, phone number or text. Give at most one of `email`, `phone` and `query`: - `email` finds the contacts with that address. Case does not matter. - `phone` finds the contacts with that number, however it is formatted. - `query` searches the way the Contacts screen's search does. - With none of them, every contact is listed, newest first. Deleted and merged contacts are never returned. For the next page, send the `nextCursor` you got as `cursor`, with the same filter. The last page has no `nextCursor`.

输入参数emaillimitphonequerycursor

contact_create

Contact – Create

Adds a contact. If the user already has this person, the values may go to that contact instead: - If the user's Auto-Merge level covers the match, the values are added to the existing contact: 200, `merged`. - Otherwise a new contact is created: 201, `created`. If it may be a duplicate, it also waits in Review duplicates: 201, `needs_review`. ContactZapp saves the contact in one two-way account: the first one the user linked that keeps an address book and is not paused. The next sync copies it to the user's other two-way accounts, never to a read-only one. A create is never refused for the plan's contact limit. Over the limit, the contact is created frozen and `contact.frozen` is true. ContactZapp keeps a frozen contact but does not sync it until the user upgrades or frees a place. Send an `Idempotency-Key` header to make a retry safe.

输入参数body必填Idempotency-Key

contact_read

Contact – Read

Returns one contact. `id` is the contact's `id` or its `publicId`, such as `CS-0042`. A deleted or merged contact is a 404, and so is another user's contact.

输入参数id必填

contact_change

Contact – Change

Changes a contact, as editing it in ContactZapp does. Only the fields you send change. A field you leave out keeps its value. The change goes to every two-way account the contact is in, never to a read-only one. History records it as the user's change and names the API key or the connected app that made it. A contact waiting in Review duplicates cannot be changed until the review is decided: 409, `contact_pending_review`. Send an `Idempotency-Key` header to make a retry safe.

输入参数id必填body必填Idempotency-Key

sync_start

Sync – Start

Starts a sync, the same as Sync now in ContactZapp. History shows it as a manual run. The answer is 202 with the sync's state, `queued` or `running`. If a sync is already going, you get that one back and no second one starts.

无需输入参数。

event_list

Event – List

Lists the events of one type, newest first. Zapier, Make and n8n poll this to start an automation. Each item's `id` never changes. Poll again and the items you already have come back with the same ids, with new ones on top. Skip the ids you have seen. - `contact.created`, `contact.updated`, `contacts.merged` and `account.needs_attention` come from History, and are kept as long as History keeps them. - `match.needs_review` lists each contact flagged as a possible duplicate and not yet merged. Its `id` changes when the flag is raised again. Each item carries what an automation needs, with no second call: - the contact's fields, or null once the contact is deleted or merged - for a merge, the ids of the contacts it absorbed - for an account, the account and why it needs attention

输入参数event必填limitcursor

版本历史

4
  1. v1.0.5最新Nov 5, 2026
  2. v1.0.4Nov 4, 2026
  3. v1.0.2Nov 3, 2026
  4. v1.0.1Nov 3, 2026

评分

已满足适用检查项的 83%

该评分衡量此收录条目的完整程度，依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价，也不表示服务器安全或当前可用：可连通性是带日期的检查结果，评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 图标10 分
  • 文档15 分

    请声明包含 README 的 GitHub 仓库，或在 OAuth 受保护资源元数据中提供 resource_documentation。

  • 许可证不适用

    托管服务按其提供方的条款使用，因此这里不要求许可证。此检查项不计入百分比。