Summer Connect your AI client to Summer MCP at https://api.gosummer.ai/mcp to set up company integrations and work with Summer's cases. Summer connects the underlying services through your company's authorized APIs, Slack connection and supported browser workflows. You can keep your existing help desk, care systems and billing tools.
Start with the MCP client instructions, then choose a service below. The same setup is available in Summer's workspace and CLI. A connection belongs to your company and environment; its permissions and verified workflows determine the work Summer can perform.
Which services can I connect to Summer?
| Service or workflow | Connection and setup guide |
|---|---|
| Intercom | Built-in credential setup and conversation checks |
| Zendesk, Freshdesk, Gorgias, Front, Help Scout | Help-desk connections using an agreed API or permitted browser workflow |
| HubSpot, Salesforce | CRM records and support cases, with a custom connection for the required account |
| Slack | Authorize a workspace and choose channels |
| MD Integrations, Beluga Health, GEN Health | Built-in clinical-provider credential setup |
| Bask Health, OpenLoop | Clinical-platform workflow setup, scoped to your account's access |
| Healthie, Practice Better, SimplePractice | Health-record connections through the access available for your practice |
| Strive Pharmacy, Empower Pharmacy, The Pharmacy Hub | Pharmacy workflow setup, using partner access and verified order references |
| Stripe | Restricted billing reads, with separate approval for supported changes |
| EasyPost, FedEx, UPS, USPS | Shipment and carrier evidence |
| Quo | Phone and text records |
| GitHub | Customer-reported software problems |
| Supabase | Operational database reads |
The logos on Summer's homepage link to these guides. The built-in credential catalog includes GEN Health, MD Integrations, Beluga Health, EasyPost, Intercom, Quo, Supabase and Stripe. Slack has its own authorization flow. Other services use a custom connection whose access and intended workflow must be configured and checked.
How do I connect a service using Summer MCP?
- Add the Summer server in your MCP client and approve your company, environment and setup permissions in the browser.
- Ask the agent to call
summer_account_me, thensummer_company_capabilitiesandsummer_integrations_listfor the company and environment you selected. - Choose the built-in provider or describe a custom integration. Tell the agent what you need done and provide the service's documentation and a safe example record reference.
- Save secrets through Settings → Integrations → Store in Summer, or the local CLI command returned by the MCP tool. Keep API keys and passwords out of chat.
- Check one known record and compare it with the original service. Use the capability checks to record what works and what still needs access or setup.
For example, ask: "Help me connect Intercom and Stripe to Summer for billing questions. Check my company's current connections, explain the permissions needed, and identify anything we still need to verify."
summer_capability_checks_list shows the workflow checklist. Supported checks can run through summer_capability_checks_test; an agent can record its findings through summer_capability_checks_report. An agent's report remains visible for review and does not count as independent verification or approval of a business action. See the tool reference.
What does a Summer MCP connection give my agent?
Your agent can inspect company capabilities, configure integrations, manage knowledge and set up Messenger within the permissions you grant. With case permissions and an enabled operational connection, it can read Summer cases and request investigations. Summer's investigator uses the company's configured services to gather evidence and prepare the next step.
The public MCP tools follow the Summer operation catalog. Connecting to Summer does not expose an unrestricted copy of each vendor's API to your local agent. For example, a Summer case can contain verified Stripe or pharmacy evidence without a public tool named after every vendor operation.
Billing, shipping and business tools
Stripe
Use the built-in Stripe setup to connect billing evidence to a support case. Save a restricted read key using the Stripe credential guide. Check the Stripe account, test/live mode and one known payment or subscription before relying on the connection.
A useful first workflow is a billing inquiry that needs the original purchase and its current subscription status. Refunds and subscription changes require the supported execution connection and exact human approval in Summer.
Shipping and carriers
Use EasyPost when your shipment or tracker lives there. Match the tracking reference to the exact purchase and read the latest carrier event. Summer can use an agreed, permitted carrier workflow when a necessary detail is available only in the carrier's tracking page.
FedEx, UPS and USPS are carrier evidence sources. An EasyPost connection can provide their tracking events without a separate direct integration for each carrier. A created label establishes a tracking reference; carrier acceptance and delivery need their own recorded events. Start with an order whose tracking page your team can compare with Summer's findings.
Quo
The Quo setup guide covers the built-in credential field for phone and text records. Verify the right account, phone number and a known conversation. Inbound call routing and outgoing calls or texts require their own configured workflow; saving the key alone does not enable them.
GitHub
Connect GitHub for a specific engineering handoff, such as a broken tracking link reported in a support case. Agree the repository access and repair process with Summer, then configure the required custom connection. Verify that a test issue reaches the intended repository and retains its source case.
An issue, a proposed fix and a deployed repair are separate steps. Track the repair back to the customer case and verify the result before telling the customer it is fixed. This connection does not grant the MCP client permission to merge or deploy code.
Supabase
Use a dedicated operational reader for the database records your support workflow needs. The Supabase setup guide lists the read key, database role and administrator attestation fields. Verify the actual database permissions and a known record with your administrator.
The read connection should expose only the records needed for the agreed work. A role name saved in Summer does not change the database's grants.
Can Summer work with a service that has no MCP server?
Yes. A service can connect to Summer through its authorized API or a supported browser workflow. Your AI client connects to Summer's MCP server; the vendor does not need to run an MCP server of its own.
If the necessary API or portal access is unavailable, Summer records that gap. Use a custom integration to define the credentials and arrange the workflow. For the design choices, read API, MCP or browser automation.
Can I use my own secret manager?
Summer includes a secrets manager. You can save credentials in the workspace or through a local CLI handoff. If your team already uses Doppler, you can instead connect a read-only vault and reference selected secrets. Doppler is optional.
Where can I learn about complete support workflows?
The docs explain configuration and checks. The blog walks through the work across systems:
- Connect an EHR, help desk and pharmacy.
- Connect provider updates to your help desk.
- Coordinate support across multiple pharmacies.
- Use MCP for telehealth support.
Bring one representative case to a Summer demo to confirm the connections, approval steps and result your team needs.