Spruce Health MCP by usefulapi

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

• 连接方式: 在云端运行
• 传输方式: Streamable HTTP
• 分类: 诊所与健康

安装

选择你使用的 AI 应用，然后复制设置。

你需要

• 在云端运行无需安装任何东西，通过互联网连接

你用的是哪个应用？

https://spruce-health.usefulapi.io/mcp

claude mcp add --transport http spruce-health https://spruce-health.usefulapi.io/mcp

{
  "mcpServers": {
    "spruce-health": {
      "url": "https://spruce-health.usefulapi.io/mcp"
    }
  }
}

{
  "servers": {
    "spruce-health": {
      "type": "http",
      "url": "https://spruce-health.usefulapi.io/mcp"
    }
  }
}

https://spruce-health.usefulapi.io/mcp

你的选择通过 Cookie 保存在这台设备上，无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

工具名称和描述与服务器在 2026年11月7日 报告的完全一致。这些内容由作者撰写，不是我们写的；我们以纯文本形式显示。

• sprucehealth_get_organization

  Your Spruce organization (id and name). The id is the owner/member id used by other objects. Good first call. GET /organization.

• sprucehealth_list_members

  All members of the organization: teammates (name, email, admin, suspended), teams and the organization itself. Paged with hasMore/paginationToken; totalCount included. GET /organization/members.

• sprucehealth_get_member

  One organization member (teammate, team or the organization) by id. GET /organization/members/{memberId}.

• sprucehealth_list_team_members

  The members of one team (team ids come from sprucehealth_list_members, type 'team'). Paged. GET /teams/{teamId}/members.

• sprucehealth_list_contacts

  Contacts of the organization (patients, professionals, clinics): name, date of birth, phones, emails, tags, custom fields, integration links. Paged with hasMore/paginationToken; totalCount included. Use sprucehealth_search_contacts to find someone. GET /contacts.

• sprucehealth_search_contacts

  Find contacts by free text and/or filters (category, tags, name, phone, email, invite state, created time). Filters combine with AND; values inside one filter match ANY (tags can use all/none). Paged; totalCount with totalCountRelation (eq = exact, gte = lower bound). A read: POS

• sprucehealth_get_contact

  One contact by Spruce contact id (entity_…): demographics, phones, emails, tags, custom and organization fields, integration links. GET /contacts/{contactId}.

• sprucehealth_list_contact_conversations

  The conversations (secure, SMS/phone, email, fax…) associated with one contact. GET /contacts/{contactId}/conversations.

• sprucehealth_list_contact_integration_links

  Links between a contact and external systems (Elation, Hint, athena, custom): type, external id, url. GET /contacts/{contactId}/integrationlinks.

• sprucehealth_list_contact_tags

  All contact tags of the organization. Paged with hasMore/paginationToken; totalCount included. GET /contacts/tags.

• sprucehealth_list_contact_fields

  The organization-wide contact fields shown on every contact. Paged; totalCount included. GET /contacts/fields.

• sprucehealth_list_conversations

  Conversations of the organization (title, type, tags, archived, assignee, participants, last message time), ordered by creation or last message. With start_from, only conversations whose ordering time is at or after it (useful for 'what changed since…'). Eventually consistent. Pa

• sprucehealth_get_conversation

  One conversation by id (t_…). GET /conversations/{conversationId}.

• sprucehealth_list_conversation_items

  The items (messages, internal notes, calls, voicemails, faxes, attachments with short-lived signed URLs) in one conversation. Order newest_first (default) or oldest_first; start_from = only items created after that time. Paged with hasMore/paginationToken; totalCount is a best-ef

• sprucehealth_get_conversation_item

  One conversation item (message, note, call, voicemail…) by id (ti_…). GET /conversationItems/{conversationItemId}.

• sprucehealth_list_read_receipts

  Who has read one conversation item and when they first read it (oldest first). GET /conversationItems/{conversationItemId}/readReceipts.

• sprucehealth_get_transcription

  The full transcription text and its summary (if any) for a transcription id (the transcriptionId on a call/voicemail attachment). Status pending/completed/failed/noSpeech. GET /transcriptions/{transcriptionId}.

• sprucehealth_list_conversation_tags

  All conversation tags of the organization. Paged; totalCount included. GET /conversations/tags.

• sprucehealth_list_conversation_scheduled_messages

  Messages scheduled to be sent later in one conversation (read only; nothing is sent or cancelled). GET /conversations/{conversationId}/scheduledmessages.

• sprucehealth_list_scheduled_messages

  All messages scheduled to be sent from the organization (read only). Paged with hasMore/paginationToken; totalCount included. GET /scheduledmessages.

• sprucehealth_list_saved_messages

  Saved message templates (private and organization-wide): title, text, internal/shared flags. Paged with hasMore/paginationToken. GET /savedmessages.

• sprucehealth_list_internal_endpoints

  The organization's own channels: Spruce phone and fax numbers, email addresses and Spruce Links, with their owner and members. GET /internalendpoints.

• sprucehealth_list_phone_lines

  All phone lines of the organization (id, name); totalCount included. GET /phonelines.

• sprucehealth_get_phone_line

  One phone line by id (pd_…). GET /phonelines/{phonelineId}.

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日

• ✓ 通过

  作者与仓库一致

  注册名称已通过域名 usefulapi.io 验证（注册中心会核实域名所有权）

• … 尚未检查

  仍在维护

  我们还没有从 GitHub 读取这个仓库

• … 尚未检查

  有许可证

  我们还没有从 GitHub 读取这个仓库

• ✓ 通过

  端点有响应

  在 168 毫秒内响应（HTTP 200）

• – 不适用

  使用 OAuth 登录

  无需登录

• ✓ 通过

  工具描述中没有隐藏指令

  已读取 24 个工具描述，未发现针对 AI 的隐藏指令

与“诊所与健康”中的其他服务器比较i

• 星标数多于此分类中其他 871 个服务器的 0%
• 发布到注册中心的时间比此分类中其他 871 个服务器的 98% 更新
• 基础检查结果等于或优于此分类中其他 871 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

作者的 README

{