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。

  • 授權條款不適用

    託管服務按其提供方的條款使用，因此這裡不要求授權條款。此檢查項不計入百分比。