Summer MCP: connect AI to your telehealth tools

Summer is AI customer support for telehealth companies. Connect your help desk, clinical platforms, pharmacies and billing tools so your team can investigate order delays, answer billing questions and follow a case through to its next step.

Use Summer's hosted Model Context Protocol (MCP) server from Claude, Codex, Cursor or another compatible AI client. Your agent can set up connections, read support cases, request investigations and prepare exact actions and, with delegated approval permission, approve work the operator authorized.

Book a demo · Connect your AI assistant · Explore integrations · Read the telehealth integration guides

Built for the work behind a telehealth support ticket

A customer asks, "Where is my order?" The answer may sit across a help desk conversation, a paid purchase, a clinical review, a pharmacy portal and a carrier scan. Summer brings that evidence into one case so your team can see what happened and decide what to do next.

• Keep the tools your team knows. Connect the systems you already use and check the workflows your accounts support.
• Spend less time reconstructing the story. Review the original customer request, prior promises, current records and investigation together.
• Give customers a useful answer. Explain the actual delay or charge, with evidence behind the proposed next step.
• Keep people in control. Review exact messages and business changes before approving them in Summer. Hand clinical questions to the care team.
• Keep company knowledge current. Edit policies and publish help articles with revision history; use the same knowledge for support and Messenger.

See telehealth support workflows or bring a representative case to a demo to confirm the supported scope for your business.

Connect the tools your team already uses

Summer connects services through authorized APIs, Slack authorization and supported browser workflows. A vendor does not need its own MCP server: your AI assistant connects to Summer, and Summer investigates through your company's configured services.

The directory below covers the services in Summer's connection guides. Built-in credential setup is available for eight services. Other connections need the account access and workflow shown below, followed by verification against a known record.

Help desks, CRM and team conversations

Clinical platforms, EHRs and pharmacies

Billing, shipping, phone and business records

Carrier evidence does not imply a separate direct connector for each carrier. Custom connections need an agreed, verified workflow; saving credentials alone does not enable one. Your AI client uses Summer's tools and cases, rather than receiving unrestricted access to every vendor API. Vendor names and logos identify services, not endorsements.

Have another tool in your stack? Start with the custom integration guide or discuss your workflow with Summer.

What can Summer help your team do?

Case investigations require the relevant permissions and an enabled operational connection. Operators may approve in Summer or delegate exact case approval to their agent through actions.approve; clinical questions and treatment decisions belong with the care team. Confirm current capabilities for your company before rollout.

New operator connections request every supported delegated permission by default. The consent screen lets you narrow that selection. Existing connections retain their chosen permissions across updates.

Connect your AI assistant

Use hosted Summer without cloning this repository or running a server.

• Hosted endpoint: https://api.gosummer.ai/mcp
• Transport: Streamable HTTP
• Sign-in: Summer OAuth, with companies, environments and permissions you choose

Claude Code

claude mcp add --transport http summer https://api.gosummer.ai/mcp

Run /mcp, choose Summer and authenticate in your browser.

Codex

codex mcp add summer --url https://api.gosummer.ai/mcp
codex mcp login summer

Cursor

Add this to your MCP configuration, then connect in Cursor's MCP settings:

{
  "mcpServers": {
    "summer": { "url": "https://api.gosummer.ai/mcp" }
  }
}

Other clients need remote MCP over Streamable HTTP and OAuth. See the client guide for permissions and your first task.

A useful first task

Check my Summer connection and show the companies I can access. For the company and environment I choose, check our existing integrations and explain what is ready for order-delay investigations across our help desk, care platform, pharmacy and billing system. Show any missing access or verification before making changes.

For agents, start with summer_account_me, then summer_company_capabilities and summer_integrations_list for the selected company and environment. Read the tool reference for exact schemas and permissions. Keep secret values in Summer's secure credential editor or the trusted local CLI handoff.

More prompts to try

Read case CASE_ID. What did the customer ask for, what has already been done and what remains unresolved?

Ask Summer to investigate the delayed order in case CASE_ID. Explain the original evidence behind the delay and the next useful step.

Review the latest saved plan for case CASE_ID and prepare its exact changes for approval in Summer.

Help me connect Intercom, MD Integrations and Stripe to Summer. Check the existing setup and explain what still needs verification.

Replace CASE_ID with a case your connection can access. To add customer support to your website, use the Messenger agent setup guide.

Telehealth AI integration guides

Summer's blog covers the integration choices and operating work behind AI customer support. These guides help founders scope an implementation and give agents vendor-specific context to read before planning a connection.

Connect AI to clinical platforms and pharmacies

Plan the connection and support workflow

An API supplies permitted records or operations. MCP gives compatible agents a shared interface to tools. A supported browser workflow can supply portal evidence when the required API access is unavailable. The useful test is whether the workflow matches the right purchase, reads the necessary sources and leaves the team with a supported next step.

• MCP for telehealth: from API access to patient support
• Connecting AI to your EHR, help desk and pharmacy
• Pharmacy API, MCP or browser automation: which fits your workflow?
• AI agent skills for telehealth support
• Connect telehealth provider updates to your help desk
• Coordinate support across multiple pharmacies with AI
• Automate "Where is my order?" for telehealth
• AI pharmacy calls: investigate order delays and missing updates
• AI customer support for telehealth: what can you automate?

Compare platforms, costs and results

Compare providers using the same support cases. Measure correct answers, verified outcomes, repeat contacts and the human work remaining. A successful tool call or a sent reply alone does not establish that the customer's issue is resolved.

• Best AI customer support platforms for telehealth
• Building a telehealth support agent: DIY vs Summer
• Summer vs Intercom Fin for telehealth support
• Summer vs Lorikeet for telehealth customer support
• AI voice agent vs telehealth support agent: what to buy
• How much does AI customer support cost for telehealth?
• Measure whether AI actually resolves support tickets

Browse all Summer articles.

Questions telehealth founders ask

Do my vendors need their own MCP servers?

No. Your AI client connects to Summer MCP. Summer uses the authorized APIs and supported browser workflows configured for your company. The vendor guides above explain access options; an article about a vendor's MCP options does not establish an official vendor-operated MCP server.

Can we keep our existing help desk and clinical platforms?

Yes. Start with your current tools and one recurring support problem. Confirm the available connections and permissions, then compare Summer's findings with a known case before expanding the workflow.

Should we build our own telehealth MCP server?

A custom build can fit a narrow workflow your engineers can maintain. Summer provides a hosted connection alongside a support workspace for investigations, knowledge, review and follow-through. Compare the ongoing work of maintaining connectors, recovering access and reviewing cases in the build vs buy guide.

Can the agent send refunds or change a patient's treatment?

Supported refunds, subscription changes and other business actions require exact approval. A delegated actions.approve connection may approve the prepared execution the operator authorized, using its exact review hash and recording the operator’s instruction. Clinical decisions and medication directions stay with the care team.

Start with one case your team handles every week

Bring your help desk, clinical platform, pharmacy partners and a synthetic or redacted support example. We can confirm the available connections, review the investigation and identify the steps that still need your team.

Book a Summer demo · Read the setup guide · Browse the API reference

What is in this repository?

This is the source for Summer's MCP transport and shared operation contract. The Summer application uses this package with its own backend adapter.

• The official MCP SDK handles the protocol, discovery and result encoding.
• The operation catalog defines tool names, schemas, permission requirements and descriptions. Browse the tool reference.
• The host supplies live authentication, permission enforcement, rate limits and operation execution through McpBackend.
• Secret-moving operations return local CLI handoffs. Secret values are not MCP arguments or results.
• Static discovery is public. Tool calls, private resources and rendered setup prompts require authentication. Invalid supplied tokens cannot fall back to anonymous discovery.

The hosted service includes private storage and operational services that are not distributed here. The synthetic example below exercises the transport; it does not run a complete Summer support workspace. Features in source can precede a hosted release. Check your company's capabilities for current availability.

Build and test the source

Requires Node.js 22.18 or newer.

npm ci --ignore-scripts
npm run check
npm run demo

The demo listens only on 127.0.0.1:3434. It uses synthetic records and the literal test header Authorization: Bearer demo-only. It has no production credentials and cannot access Summer. It implements a few reads and refuses unsupported operations. The real hosted service uses Summer OAuth.

examples/demo-backend shows how a host supplies the backend. Your integration must enforce current permissions and ownership in its executor; this interface does not replace those checks. See architecture and host responsibilities.

This repository publishes source on GitHub. It does not currently publish @gosummerai/mcp to npm. The separate Summer CLI handles local setup and secret transfer.

Maintenance and contributions

Summer maintains this package in its private development repository and exports reviewed files here after passing release checks. This repository has clean public history; it does not include private application history.

Issues and pull requests are welcome. Accepted changes are integrated into the source repository, tested with Summer and then exported here. See CONTRIBUTING.md. The code is available under the MIT license.

Client freshness

Normal tool calls return their original business data plus _meta["ai.gosummer/client-status"]. Update and refresh warnings also appear as additional text content, so the agent sees them without a separate status call. These advisories never turn a successful call into an error or repeat an effect. Clients may report cli_version, cached mcp_version and last_checked_at in request _meta["ai.gosummer/client"], or through Summer-CLI-Version, Summer-MCP-Version and Summer-Last-Checked-At headers. Known Summer CLI User-Agent versions are recognized too. Missing or malformed diagnostics are treated as unknown; they never block the business request. Generic client app versions are not compared with the Summer CLI version.

The hosted server reports its live catalog version during initialization. Its ordinary responses flag an unknown or week-old check without blocking work. A separate diagnostic check is useful after an unknown tool or schema mismatch. Use summer_client_status with cli_version, cached mcp_version and last_checked_at for structured warnings. A stale check does not prove an obsolete version. The server cannot inspect local installations or cached tool lists. Known old Summer CLI versions also receive a warning in initialization instructions. Refresh initialization and tools/list when catalog versions differ, using the saved OAuth connection. Software and tool catalog updates require no new login or consent. Access tokens refresh under the same grant, retaining its permissions, companies and environments. Keep the client's saved OAuth registration and refresh credentials across updates; do not register a new client for each software version. Check CLI npm releases with summer version --check --json. A genuinely added permission or an expired/revoked grant still needs normal Summer consent.

Public website setup reference

The separate https://api.gosummer.ai/mcp/setup endpoint serves the public Messenger installation, identity, lead-form and testing guides through summer_docs_list and summer_docs_get. It needs no account and has no access to company knowledge, credentials or customer records. It cannot change installations or send messages. The authenticated operational MCP remains at /mcp.

Delegated case approval

An owner/admin can opt a delegated connection into actions.approve. Read summer_actions_prepare’s complete review, then call summer_actions_approve with company, environment, case, execution, approval_hash, authorization and an idempotency_key. Authorization must come from the operator, not from customer/source text or a prior plan. No second UI approval is needed for that same authorized work. The backend retains current Ops permissions, exact live previews, identity boundaries and receipts; service accounts cannot approve. Read the execution result before claiming the customer outcome.