What Summer does
Summer provides MCP tools for telehealth support and company administration. Agents can read and save onboarding policies, search an owned customer store, inspect provider account configuration, review runtime readiness, and read the effective knowledge used by agents. The customer tools support discovery by name, UUID, provider identifier, exact email, or E.164 phone number, while retaining source evidence and distinguishing ambiguous candidates.
Knowledge management includes company-specific revisions and versioned shared guidance. Company administrators can adopt an exact shared publication, review differences, and publish reviewed policy drafts. Platform-admin authority is required for publishing shared guidance. Public articles, billing, operating hours, integrations, and customer effects are outside the policy publication operation.
Summer also supports bounded engineering and action workflows. It can connect a company environment to selected GitHub repositories and folders, cache source code, read cached files, and inspect original issues. Separate tools catalog available actions, identify recurring uncovered work, create company-action drafts from approved work, and test actions without sending requests or changing state.
How it works
Administrative changes generally use expected revisions or versions. Policy and action tools separate saving a draft from publishing it; runtime configuration likewise uses readiness evidence before production activation. Publishing records history, while adoption preserves local company policies and earlier agent snapshots.
GitHub access follows a staged flow: an administrator authorizes the Summer GitHub App, repositories and folders are selected, and the selected code is synchronized into a cache. Source reads use that cache rather than making live GitHub requests. Reusing an unchanged commit avoids another synchronization, and disconnecting removes the cached archives.
Action definitions can describe either an HTTP request or work performed by an agent. HTTP actions specify an HTTPS host, method, path, body, and saved credential name. Task actions describe procedures or website work. Testing renders the request or task with example inputs but sends nothing.
Tools and capabilities
- Read and save onboarding policy answers, employee selection, destination choices, and launch-related facts.
- Publish reviewed company policy drafts with company-admin authority.
- Save and search administrative customer and contact discovery records with evidence.
- Read runtime settings, pilot cases, readiness, capability switches, and configuration history.
- Inspect provider connection metadata and verified capabilities without exposing credential values.
- Review, adopt, and publish versioned shared knowledge and inspect effective document provenance.
- Start GitHub authorization, select repositories and folders, synchronize cached code, read files, inspect issues, and disconnect access.
- Catalog built-in, connector, and company actions; draft actions from approved work; and test them without execution.
Limitations and notes
Customer discovery does not verify account access, search Rebody Auth, verify a patient, link a sign-in session, enable a provider, or authorize a customer effect. Saving a Bask providerPatient ID is an atomic association, not patient verification.
Provider metadata changes invalidate previous checks and disable affected capabilities; saving credentials does not prove that a Bask API works. Saved keys and templates do not establish readiness, and unfinished optional providers do not block unrelated capabilities.
GitHub access is limited to company-selected repositories and folders. Cached source reads do not perform live GitHub calls, and issue closure does not resolve a customer case. Automatic investigations prepare plans rather than enabling automatic actions. Exact effect approval and saved budgets remain preserved during runtime configuration.
