Summer

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