Overlap

Records what you're working on so Overlap can introduce you to someone two weeks ahead of you.

我該用這個嗎

品質與安全性

A
說明品質
97%
結構描述完整度
90%
命名品質
94%
汙染風險
100%
權限相符程度
100%
協定合規性
100%

根據工具定義與協定合規性的自動化分析。

上下文成本

~1,741Token(工具定義)
~1.2 KB典型回應大小
中等的注意力影響(128k 上下文的 1.36%)

這是每次將伺服器的工具載入模型上下文時所消耗的約略 token 數量。數量越高,可用於其他工作的注意力就越少。

安裝

一鍵安裝

將以下內容加入你的 `claude_desktop_config.json` 檔案:

{
  "mcpServers": {
    "overlap": {
      "url": "https://overlap-ai.com/api/mcp"
    }
  }
}

遠端端點

https://overlap-ai.com/api/mcpstreamable-http

它能做什麼

工具清單

工具(7)

🟢 唯讀🟡 寫入🔴 刪除⚪ 未知
🟢preview_pool(description)

Count the people already in the pool whose situation is close to a description. Returns a number and nothing else, capped at 10 — never anyone's words, name or details. It saves nothing: no match request is created and nobody is contacted. This is the one tool that works without an account. Use it to answer whether anyone is going through something similar, before the user decides whether to join.

輸入結構描述

{
  "type": "object",
  "properties": {
    "description": {
      "type": "string",
      "minLength": 1,
      "maxLength": 1500,
      "description": "What the person is going through, in their own words. Two to five sentences is enough. This is only embedded and counted against — it is never stored and never shown to anyone."
    }
  },
  "required": [
    "description"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🟡create_match_request(request_text, replaces_draft_id)

Submit what the user is going through, to find someone living through something similar. Write the match request from the current conversation. Write 2–5 sentences in the third person, and 200–1500 characters. Use the words of the user, not formal or clinical words. Cover three things: the situation, where the user is in it, and what help they want. Write it so that a stranger in the same place recognizes themselves. Any situation belongs here: an illness, a company, a move, a course, a hard year. Example of a good match request: "She was diagnosed with early-stage breast cancer four months ago and is halfway through chemotherapy. The medical side goes to plan. She finds the isolation harder than the treatment. The people around her keep telling her to stay positive. She hopes to hear from someone at a similar stage who understands the day-to-day of it." Never invent a detail. Never include a name, an email address, an employer or another personal identifier. This call creates a new independent DRAFT. It replaces nothing in the pool. The draft stays saved until the user approves it, revises it or discards it. Show the stored match request back to the user VERBATIM. Then ask the user to approve it, or to tell you what to change. Call confirm_match_request with the request_id only after the user approves that exact version. If the user asks for a change, call create_match_request again. Pass the complete new draft, and set replaces_draft_id to the earlier request_id. Then show the new stored version and ask again. If the user declines, call withdraw_match_request with that request_id to discard the draft.

輸入結構描述

{
  "type": "object",
  "properties": {
    "request_text": {
      "type": "string",
      "description": "The complete text of the request. Write 2–5 sentences in the third person, and at most 1500 characters. Say what the user hopes to get from a meeting."
    },
    "replaces_draft_id": {
      "description": "The request_id of a draft the user has already seen. Pass it only for a revision. Leave it out for a new independent request.",
      "type": "string"
    }
  },
  "required": [
    "request_text"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🟡confirm_match_request(request_id)

Confirm one draft match request and add it to the matching pool. The other requests of the user do not change. It stays active until the user withdraws it. Call this ONLY after the user approves the exact stored text. Always pass its request_id.

輸入結構描述

{
  "type": "object",
  "properties": {
    "request_id": {
      "type": "string",
      "description": "The request_id from create_match_request or check_matches. Always name the exact request that the user approved, or asked you to withdraw."
    }
  },
  "required": [
    "request_id"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🟢check_matches

Where the user stands. It returns every current match request, the number of other people in the pool, and any match. Use it to answer what the user submitted, and who they matched with. A match can appear days later.

輸入結構描述

{
  "type": "object",
  "properties": {},
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🟢get_match_details(match_id)

Get the full details of one match: what the other person wrote, why the two of them matched, something to open with, and where the match stands. It only reads. To accept, decline or block the match, call respond_to_match. Never promise an address.

輸入結構描述

{
  "type": "object",
  "properties": {
    "match_id": {
      "type": "string",
      "format": "uuid",
      "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
      "description": "The match_id from check_matches."
    }
  },
  "required": [
    "match_id"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🔴respond_to_match(match_id, response)

Record the one answer the user gave about a match: accept, decline or block. Call it only after the user has said which of the three they want. When both people accept, overlap opens a private conversation in the app. It also sends each person a link by email. Never promise an address. A decline covers this one request, and a later request from that person can still match. A block is permanent and covers the person, so send block only when the user asks for exactly that.

輸入結構描述

{
  "type": "object",
  "properties": {
    "match_id": {
      "type": "string",
      "format": "uuid",
      "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
      "description": "The match_id from check_matches."
    },
    "response": {
      "type": "string",
      "enum": [
        "accept",
        "decline",
        "block"
      ],
      "description": "The one answer the user gave. Use accept when the user wants this match. Use decline to pass on it: that covers this request only, and the next request from the same person can still match. Use block to never match the user with this person again — it is permanent, so use it only when the user asks for exactly that. A plain 'no thanks' is a decline, not a block."
    }
  },
  "required": [
    "match_id",
    "response"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🔴withdraw_match_request(request_id)

Withdraw one match request, either a draft or an open one. Always pass its request_id. If it is unclear which one the user means, call check_matches first. The other requests of the user stay active. This voids a pending match from this request. It keeps a match that both people accepted.

輸入結構描述

{
  "type": "object",
  "properties": {
    "request_id": {
      "type": "string",
      "description": "The request_id from create_match_request or check_matches. Always name the exact request that the user approved, or asked you to withdraw."
    }
  },
  "required": [
    "request_id"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

社群

為此伺服器評分

證據

近期觀測

已驗證未記錄版本7 個工具
已驗證未記錄版本6 個工具