Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Summer

REMOTE · API.GOSUMMER.AI

Telehealth support for Claude, Codex and Cursor: investigate cases and connect your tools.

Available components

80 Trust /100

Last scanned (12 hours ago)

Scores higher than 84% of remote servers

Reachable. Last reached 24 Oct 2026.

Category CRM and Sales

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security97
Transport & Reachability100
Schema Quality & AI Usability74
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 15099 tokens (~93/item across 161 items; 161 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
  • Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage79
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 37% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 5 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 162 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 24 Oct 26 +1
    • New tool “summer_account_photo_remove”, which the server declares destructive security
    • New tool “summer_investigations_plan_edit”, which the server declares destructive security
    • New tool “summer_reports_themes_generate”, which the server declares destructive security
    • New tool “summer_reports_themes_review”, which the server declares destructive security
    • New tool “summer_slack_account_disconnect”, which the server declares destructive security
    • New tool “summer_workflows_save”, which the server declares destructive security
    • Tool “summer_account_me” rewrote its description, which is the text the model reads security
    • Tool “summer_github_connection_start” rewrote its description, which is the text the model reads security
    • Tool “summer_integrations_list” rewrote its description, which is the text the model reads security
    • Tool “summer_reports_service_metrics” rewrote its description, which is the text the model reads security
    • Tool “summer_slack_sender_update” rewrote its description, which is the text the model reads security
    • Schema quality: 12176 → 15099 ▼ functional
    • New tool “summer_cases_discussions_list” functional
    • New tool “summer_cases_discussions_read” functional
    • New tool “summer_cases_engineering_list” functional
    • New tool “summer_cases_similar_list” functional
    • New tool “summer_github_issues_read” functional
    • New tool “summer_messenger_sms_create” functional
    • New tool “summer_messenger_sms_read” functional
    • New tool “summer_messenger_sms_update” functional
    • New tool “summer_plans_list” functional
    • New tool “summer_reports_agent_timing” functional
    • New tool “summer_reports_samples_list” functional
    • New tool “summer_reports_themes_get” functional
    • New tool “summer_reports_themes_list” functional
    • New tool “summer_slack_account_read” functional
    • New tool “summer_slack_discussions_channels” functional
    • New tool “summer_slack_reader_read” functional
    • New tool “summer_slack_reader_update” functional
    • New tool “summer_teammates_slack_dms_list” functional
    • New tool “summer_teammates_slack_dms_update” functional
    • New tool “summer_teammates_slack_link_create” functional
    • New tool “summer_workflows_history” functional
    • New tool “summer_workflows_list” functional
    • New tool “summer_workflows_request_text” functional
    • “summer_slack_sender_update” added an optional parameter “sender” cosmetic
    • “summer_slack_sender_update” reworded the description of “teammate_id” cosmetic
    • Tool “summer_account_me” changed its title: Show the signed-in person, Summer access status and this connection's grant → Show the signed-in person, Summer access status, profile photo path and this connection's grant cosmetic
    • Tool “summer_github_connection_start” changed its title: Get the Summer browser URL for a company administrator to install and authorize the read-only GitHub App → Get the Summer browser URL for a company administrator to install and authorize the Summer GitHub App cosmetic
    • Tool “summer_integrations_list” changed its title: List provider integrations, their categories, required fields and saved metadata → List provider integrations, their categories, required fields, alternative credential sets and saved metadata cosmetic
    • Tool “summer_reports_service_metrics” changed its title: Read current response and resolution metrics in the company timezone → Read response and resolution metrics, 90-day daily issue/message and timing trends, and weekday/hour incoming-message heatmaps in the company timezone cosmetic
    • Tool “summer_slack_sender_update” changed its title: Choose who posts approved vendor Slack replies: the Summer Ellis app (null) or a Summer Teammate, which then posts from its own Slack account → Choose who posts approved vendor Slack replies: the Summer Ellis app, a Summer Teammate (AI employee) from its own Slack account, or the person who approves each reply, from their own connected Slack account cosmetic
  • 23 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • New tool “summer_actions_approve”, which the server declares destructive security
    • New tool “summer_github_connection_disconnect”, which the server declares destructive security
    • New tool “summer_github_sources_save”, which the server declares destructive security
    • New tool “summer_github_sources_sync”, which the server declares destructive security
    • New tool “summer_human_tasks_update”, which the server declares destructive security
    • New tool “summer_imports_intercom_control”, which the server declares destructive security
    • New tool “summer_imports_intercom_preview”, which the server declares destructive security
    • New tool “summer_teammates_slack_disconnect”, which the server declares destructive security
    • Tool “summer_actions_prepare” rewrote its description, which is the text the model reads security
    • Tool “summer_assets_uploads_create” rewrote its description, which is the text the model reads security
    • Tool “summer_cases_get” rewrote its description, which is the text the model reads security
    • Tool “summer_cases_list” rewrote its description, which is the text the model reads security
    • Tool “summer_cases_search” rewrote its description, which is the text the model reads security
    • Tool “summer_client_status” rewrote its description, which is the text the model reads security
    • Tool “summer_company_settings_read” rewrote its description, which is the text the model reads security
    • Tool “summer_events_list” rewrote its description, which is the text the model reads security
    • Tool “summer_guides_authoring” rewrote its description, which is the text the model reads security
    • Tool “summer_integrations_save” rewrote its description, which is the text the model reads security
    • Tool “summer_investigations_list” rewrote its description, which is the text the model reads security
    • Tool “summer_knowledge_create” rewrote its description, which is the text the model reads security
    • Tool “summer_knowledge_list” rewrote its description, which is the text the model reads security
    • Tool “summer_runs_list” rewrote its description, which is the text the model reads security
    • Tool “summer_saved_replies_save” rewrote its description, which is the text the model reads security
    • Schema quality: 9319 → 12176 ▼ functional
    • Server version: 0.2.2 → 0.2.4 functional
    • New tool “summer_github_connection_read” functional
    • New tool “summer_github_connection_start” functional
    • New tool “summer_github_folders_list” functional
    • New tool “summer_github_repositories_list” functional
    • New tool “summer_github_sources_read” functional
    • New tool “summer_human_tasks_list” functional
    • New tool “summer_imports_intercom_list” functional
    • New tool “summer_imports_intercom_profiles” functional
    • New tool “summer_slack_channels_describe” functional
    • New tool “summer_slack_channels_list” functional
    • New tool “summer_slack_channels_posting_update” functional
    • New tool “summer_slack_sender_update” functional
    • New tool “summer_teammates_create” functional
    • New tool “summer_teammates_list” functional
    • New tool “summer_teammates_mailbox_get” functional
    • New tool “summer_teammates_mailbox_list” functional
    • New tool “summer_teammates_names_list” functional
    • New tool “summer_teammates_setup_status” functional
    • New tool “summer_teammates_slack_channels_join” functional
    • New tool “summer_teammates_update” functional
    • “summer_actions_prepare” added an optional parameter “replaces_execution” cosmetic
    • “summer_cases_list” added an optional parameter “sentiment” cosmetic
    • “summer_company_settings_update” added an optional parameter “email_subject” cosmetic
    • “summer_knowledge_list” added an optional parameter “tag” cosmetic
    • Tool “summer_actions_prepare” changed its title: Prepare the exact work in the current saved plan for human approval in Summer → Prepare the exact current plan and return its execution ID, approval hash and reviewed work cosmetic
    • Tool “summer_cases_list” changed its title: List company-owned cases or conversations with filters, ordering, page size, coverage and a cursor → List company-owned cases or conversations with emotion filters (sentiment: happy, neutral, upset, angry, sad, mixed or unknown), ordering, page size, coverage and a cursor cosmetic
    • Tool “summer_company_settings_read” changed its title: Read company-wide settings → Read company-wide settings, including the email subject customers see on new support emails cosmetic
    • Tool “summer_guides_authoring” changed its title: Get the reviewed company-specific guide-building instructions for your native coding agent → Read the company's reviewed guide-authoring brief, draft article references and publication state cosmetic
    • Tool “summer_integrations_save” changed its title: Save a custom integration's description, setup instructions and credential names → Save a custom integration's description, setup instructions and credential field names cosmetic
    • Tool “summer_investigations_list” changed its title: Read investigation runs, saved plans, approval state and execution receipts for a case → Read shared investigation runs, saved plans, approval state and execution receipts across the verified customer’s cases, including historical issues cosmetic
  • 22 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • New tool “summer_cases_assignment_update”, which the server declares destructive security
    • New tool “summer_pharmacy_calls_settings_update”, which the server declares destructive security
    • New tool “summer_privacy_requests_create”, which the server declares destructive security
    • New tool “summer_quality_assessments_save”, which the server declares destructive security
    • New tool “summer_quality_scenarios_save”, which the server declares destructive security
    • New tool “summer_saved_replies_save”, which the server declares destructive security
    • New tool “summer_saved_views_delete”, which the server declares destructive security
    • New tool “summer_saved_views_save”, which the server declares destructive security
    • New tool “summer_support_policy_update”, which the server declares destructive security
    • New tool “summer_work_routing_update”, which the server declares destructive security
    • Tool “summer_cases_list” rewrote its description, which is the text the model reads security
    • Tool “summer_integrations_list” rewrote its description, which is the text the model reads security
    • Tool “summer_integrations_save” rewrote its description, which is the text the model reads security
    • Tool coverage: 52% → 41% ▼ functional
    • Schema quality: 5322 → 9319 ▼ functional
    • Stability: unverified → 0.03 ▲ functional
    • Server version: 0.2.0 → 0.2.2 functional
    • New tool “summer_agent_exclusions_list” functional
    • New tool “summer_cases_assignment_read” functional
    • New tool “summer_cases_customer_profile” functional
    • New tool “summer_cases_search” functional
    • New tool “summer_client_status” functional
    • New tool “summer_integrations_setup_prompt” functional
    • New tool “summer_messenger_conversations_get” functional
    • New tool “summer_messenger_conversations_list” functional
    • New tool “summer_messenger_email_check” functional
    • New tool “summer_messenger_email_create” functional
    • New tool “summer_messenger_email_read” functional
    • New tool “summer_messenger_email_update” functional
    • New tool “summer_messenger_leads_list” functional
    • New tool “summer_messenger_voice_read” functional
    • New tool “summer_messenger_voice_update” functional
    • New tool “summer_pharmacy_calls_settings_read” functional
    • New tool “summer_privacy_requests_list” functional
    • New tool “summer_quality_corrections_list” functional
    • New tool “summer_quality_scenarios_get” functional
    • New tool “summer_quality_scenarios_list” functional
    • New tool “summer_reports_commitments” functional
    • New tool “summer_reports_credits” functional
    • New tool “summer_reports_delivery” functional
    • New tool “summer_reports_service_metrics” functional
    • New tool “summer_runs_list” functional
    • New tool “summer_saved_replies_history” functional
    • New tool “summer_saved_replies_list” functional
    • New tool “summer_saved_views_list” functional
    • New tool “summer_slack_identity_read” functional
    • New tool “summer_slack_identity_update” functional
    • New tool “summer_support_policy_read” functional
    • New tool “summer_work_routing_read” functional
    • “summer_cases_list” added an optional parameter “autonomy” cosmetic
    • “summer_cases_list” added an optional parameter “category” cosmetic
    • “summer_cases_list” added an optional parameter “dismissals” cosmetic
    • “summer_cases_list” added an optional parameter “escalations” cosmetic
    • “summer_cases_list” added an optional parameter “followUps” cosmetic
    • “summer_cases_list” added an optional parameter “internal” cosmetic
    • “summer_cases_list” added an optional parameter “lane” cosmetic
    • “summer_cases_list” added an optional parameter “language” cosmetic
    • “summer_cases_list” added an optional parameter “mine” cosmetic
    • “summer_cases_list” added an optional parameter “pastSla” cosmetic
    • “summer_cases_list” added an optional parameter “plan” cosmetic
    • “summer_cases_list” added an optional parameter “responseDue” cosmetic
    • “summer_cases_list” added an optional parameter “reviewMine” cosmetic
    • “summer_cases_list” added an optional parameter “sandbox” cosmetic
    • “summer_cases_list” added an optional parameter “severity” cosmetic
    • “summer_cases_list” added an optional parameter “sort” cosmetic
    • “summer_cases_list” added an optional parameter “unmatched” cosmetic
    • “summer_cases_list” added an optional parameter “workstream” cosmetic
    • “summer_integrations_list” added an optional parameter “category” cosmetic
    • “summer_integrations_list” added an optional parameter “connection” cosmetic
    • “summer_integrations_list” added an optional parameter “search” cosmetic
    • “summer_integrations_save” added an optional parameter “description” cosmetic
    • “summer_integrations_save” added an optional parameter “instructions” cosmetic
    • Tool “summer_cases_list” changed its title: List company-owned cases or conversations, newest first, with coverage and a cursor → List company-owned cases or conversations with filters, ordering, page size, coverage and a cursor cosmetic
    • Tool “summer_integrations_list” changed its title: List provider integrations, their required fields and saved metadata → List provider integrations, their categories, required fields and saved metadata cosmetic
    • Tool “summer_integrations_save” changed its title: Define a custom integration's credential names and labels → Save a custom integration's description, setup instructions and credential names cosmetic
  • 21 Oct 26 79

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 24 Oct 2026 · Probed https://api.gosummer.ai/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=api.gosummer.ai CN=YR2,O=Let's Encrypt,C=US 20 Oct 2026 18 Jan 2027 RSA 2048 SHA256-RSA 5b02d6e401a0f6a72fbadf52f538e4cda66
SANs: api.gosummer.ai
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.gosummer.ai. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
ai. present 3799 8 Verified
gosummer.ai. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer realm="summer", error="invalid_token", resource_metadata="https://api.gosummer.ai/.well-known/oauth-protected-resource/mcp", scope="setup cases.read investigations.request actions.prepare actions.approve workspace.write credentials.replace messaging.activate guides.publish automation.manage"

Bearer realm="summer", error="invalid_token", resource_metadata="https://api.gosummer.ai/.well-known/oauth-protected-resource/mcp", scope="setup cases.read investigations.request actions.prepare actions.approve workspace.write credentials.replace messaging.activate guides.publish automation.manage"
Header Value
strict-transport-security max-age=63072000
x-content-type-options nosniff

Protected resource metadata

Document https://api.gosummer.ai/.well-known/oauth-protected-resource/mcp
Retrieved Yes
Resource https://api.gosummer.ai/mcp
Authorisation server https://gosummer.ai

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.gosummer.ai/mcp Verified 200
http (plaintext) http://api.gosummer.ai/mcp HTTPS enforced 308 https://api.gosummer.ai/mcp
MCP tools · 161 exposed · ~13,767 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
summer_privacy_requests_create ~112

File an export or deletion request for human review. Cannot approve, perform or attest completion of the work.

NameTypeReqDescription
companystringyes–
idstringyes–
idempotency_keystring–Reuse the same key when retrying the same change
kindstringyes–
reasonstringyes–
requestKindstringyes–
scopearrayyes–
subjectKindstringyes–
subjectLabelstringyes–

No output schema declared.

No examples provided.

summer_privacy_requests_list ~38

Read privacy export/deletion requests, status and original event history. Does not export or delete data.

NameTypeReqDescription
companystringyes–

No output schema declared.

No examples provided.

summer_quality_assessments_save ~122

Record an evidence-backed assessment or correction. Does not approve a plan or customer action.

NameTypeReqDescription
checksobjectyes–
companystringyes–
corrects–yes–
idstringyes–
idempotency_keystring–Reuse the same key when retrying the same change
kindstringyes–
notesstringyes–
outcomestringyes–
runKindstringyes–
runReferencestringyes–
scenarioIdstringyes–

No output schema declared.

No examples provided.

summer_quality_corrections_list ~28

Read evidence-backed corrections to previous quality assessments.

NameTypeReqDescription
companystringyes–

No output schema declared.

No examples provided.

summer_quality_scenarios_get ~34

Read one scenario and its saved assessments.

NameTypeReqDescription
companystringyes–
scenariostringyes–

No output schema declared.

No examples provided.

summer_quality_scenarios_list ~28

Read quality scenarios, assessments and current outcomes.

NameTypeReqDescription
companystringyes–

No output schema declared.

No examples provided.

summer_quality_scenarios_save ~98

Create, revise or retire a quality scenario, with expected revision and reason.

NameTypeReqDescription
companystringyes–
expectedRevisionintegeryes–
fieldsobjectyes–
idstringyes–
idempotency_keystring–Reuse the same key when retrying the same change
kindstringyes–
reasonstringyes–
retiredbooleanyes–

No output schema declared.

No examples provided.

summer_reports_agent_timing ~84

Read how long approved agent runs take: approval to start, each startup and work phase, and each step by action and category, with medians, 90th percentiles and recent runs. Phases that were not recorded stay unmeasured. Starts no work.

NameTypeReqDescription
companystringyes–
days–––
environmentstringyes–

No output schema declared.

No examples provided.

summer_reports_commitments ~32

Read outstanding customer promises and unfinished work.

NameTypeReqDescription
companystringyes–
environmentstringyes–

No output schema declared.

No examples provided.

summer_reports_credits ~43

Read all-time and month-to-date credits, pending reservations and monthly usage in the company timezone.

NameTypeReqDescription
companystringyes–
environmentstringyes–

No output schema declared.

No examples provided.

summer_reports_delivery ~38

Read delivery attempts, failures and recorded results. Does not retry a delivery.

NameTypeReqDescription
companystringyes–
environmentstringyes–

No output schema declared.

No examples provided.

summer_reports_samples_list ~120

Read paginated original issue/message references behind service counts and timing samples, with date/channel/hour filters in the company timezone. No messages are sent or marked read.

NameTypeReqDescription
channelstring––
companystringyes–
environmentstringyes–
fromstring––
hourinteger––
limitinteger––
measurestringyes–
observedAtstring––
offsetinteger––
throughstring––
weekdayinteger––

No output schema declared.

No examples provided.

summer_reports_service_metrics ~59

Read response and resolution metrics, 90-day daily issue/message and timing trends, and weekday/hour incoming-message heatmaps in the company timezone. Missing timings stay unmeasured.

NameTypeReqDescription
companystringyes–
environmentstringyes–

No output schema declared.

No examples provided.

summer_reports_themes_generate ~98

Generate a private recurring-issue report from the admitted case-summary cohort. One immutable request ID prevents duplicate inference. No customer, knowledge or publication effect.

NameTypeReqDescription
companystringyes–
environmentstringyes–
fromstringyes–
idempotency_keystring–Reuse the same key when retrying the same change
request_idstringyes–
tostringyes–

No output schema declared.

No examples provided.

summer_reports_themes_get ~58

Read one saved recurring-issue report and its source snapshot, including reports older than the latest list. Requires current operational company access.

NameTypeReqDescription
companystringyes–
environmentstringyes–
reportstringyes–

No output schema declared.

No examples provided.

summer_reports_themes_list ~56

Read the latest private recurring-issue reports, original case references, source coverage, generation status and human review. Generated themes are suggestions, not verified causes.

NameTypeReqDescription
companystringyes–
environmentstringyes–

No output schema declared.

No examples provided.

summer_reports_themes_review ~115

Record a human disposition on a saved recurring-issue theme at its expected revision. Retains the original analysis and source references; does not change cases or company knowledge.

NameTypeReqDescription
companystringyes–
dispositionstringyes–
environmentstringyes–
expected_revisionintegeryes–
idempotency_keystring–Reuse the same key when retrying the same change
reasonstringyes–
reportstringyes–
themeintegeryes–

No output schema declared.

No examples provided.

summer_runs_list ~175

List investigation and execution runs across cases, newest first, with status, plan approval and date filters.

NameTypeReqDescription
companystringyesSummer company ID
created_afterstring–ISO 8601 time with an offset, for example 2026-10-01T00:00:00Z
created_beforestring–ISO 8601 time with an offset, for example 2026-10-01T00:00:00Z
cursorstring––
environmentstringyesEnvironment that owns the resource
executed––Only approved executions, with their effects
kindstring––
sortstring––
statusstring–approval: plans waiting for human approval; review: runs that need a person to check them

No output schema declared.

No examples provided.

summer_saved_replies_history ~33

Read original revisions of a saved reply.

NameTypeReqDescription
companystringyes–
replystringyes–

No output schema declared.

No examples provided.

summer_saved_replies_list ~33

Read company saved replies, optionally including retired replies.

NameTypeReqDescription
companystringyes–
retired–––

No output schema declared.

No examples provided.

summer_saved_replies_save ~118

Create, edit, retire or restore a saved reply with its expected revision and reason. Sends nothing. API reference: https://api.gosummer.ai/v1/openapi.json

NameTypeReqDescription
bodystringyes–
companystringyes–
expectedRevisionintegeryes–
idstringyes–
idempotency_keystring–Reuse the same key when retrying the same change
namestringyes–
reasonstringyes–
retiredbooleanyes–

No output schema declared.

No examples provided.

summer_saved_views_delete ~65

Remove an owned inbox view, retaining the database's ownership checks.

NameTypeReqDescription
companystringyes–
idstringyes–
idempotency_keystring–Reuse the same key when retrying the same change
kindstringyes–

No output schema declared.

No examples provided.

summer_saved_views_list ~28

Read this person's saved inbox views and shared company views.

NameTypeReqDescription
companystringyes–

No output schema declared.

No examples provided.

summer_saved_views_save ~94

Save a personal or shared inbox view. Known case filters are normalized by the same service as the UI.

NameTypeReqDescription
companystringyes–
idstringyes–
idempotency_keystring–Reuse the same key when retrying the same change
kindstringyes–
namestringyes–
querystringyes–
sharedbooleanyes–

No output schema declared.

No examples provided.

summer_service_accounts_list ~26

List the company's service accounts.

NameTypeReqDescription
companystringyesSummer company ID

No output schema declared.

No examples provided.

summer_service_accounts_save ~139

Create, update, rotate or disable a service account. A new secret goes to the trusted local helper only. Returns a local CLI command when a secret is involved.

NameTypeReqDescription
accountstringyes–
companystringyesSummer company ID
disableboolean––
environmentsarrayyes–
expected_versionintegeryesCurrent version you expect; 0 when the resource does not exist yet
idempotency_keystring–Reuse the same key when retrying the same change
namestringyes–
rotate_secretboolean––
scopesarrayyes–

No output schema declared.

No examples provided.

summer_slack_account_disconnect ~83

Disconnect the caller's own Slack account from Summer in this company and delete its saved token. Replies set to post as the approver are then blocked for the caller, and Summer stops reading as the caller.

NameTypeReqDescription
companystringyesSummer company ID
idempotency_keystring–Reuse the same key when retrying the same change

No output schema declared.

No examples provided.

summer_slack_account_read ~54

Read whether the caller's own Slack account is connected to Summer in this company, and the settings link to connect it. Connecting uses Slack sign-in in a browser.

NameTypeReqDescription
companystringyesSummer company ID

No output schema declared.

No examples provided.

summer_slack_channels_describe ~155

Set which vendor a selected Slack channel is for and what it is used for, with a reason. Null clears a field. Changes guidance for agents and people; sends no message and changes no channel access.

NameTypeReqDescription
channelstringyesSlack channel ID from slack.channels.list
companystringyesSummer company ID
idempotency_keystring–Reuse the same key when retrying the same change
installation_idstringyesThe Slack connection from slack.channels.list.
purpose–yesWhat the channel is used for, in one or two plain sentences.
reasonstringyes–
vendor–yesThe vendor this channel is with, such as Beluga Health.

No output schema declared.

No examples provided.

summer_slack_channels_list ~56

List the Slack channels the company selected for Summer, with read and post access and each channel's vendor and purpose. Agents see the vendor and purpose with every vendor Slack read.

NameTypeReqDescription
companystringyesSummer company ID

No output schema declared.

No examples provided.

summer_slack_channels_posting_update ~133

Allow or stop approved agent replies in one vendor Slack channel, with the expected version from teammates.setup.status and a reason. Each reply still needs a person to approve its exact text. Sends no message.

NameTypeReqDescription
allowedbooleanyes–
channelstringyesSlack channel ID from teammates.setup.status
companystringyesSummer company ID
expected_versionintegeryespostingVersion from teammates.setup.status; 0 before the first change.
idempotency_keystring–Reuse the same key when retrying the same change
reasonstringyes–

No output schema declared.

No examples provided.

summer_slack_discussions_channels ~61

Read connected Slack posting channels, or inspect the current internal channel name/privacy, posting revision and authenticated sender. Enables no grant and posts nothing.

NameTypeReqDescription
channelstring––
companystringyes–
environmentstringyes–

No output schema declared.

No examples provided.

summer_slack_identity_read ~47

Read the support name and avatar shown on Summer's approved Slack replies, whether the Slack install allows them, and the change history.

NameTypeReqDescription
companystringyesSummer company ID

No output schema declared.

No examples provided.

summer_slack_identity_update ~145

Set the support name and avatar on Summer's approved Slack replies, with the expected revision and a reason. Null values use the plain Summer Ellis identity. Sends no message.

NameTypeReqDescription
avatar_url–yesPublic https image link for the reply avatar.
companystringyesSummer company ID
display_name–yesSupport name shown on replies, such as the company's support team name. Slack still marks the post as an app.
idempotency_keystring–Reuse the same key when retrying the same change
reasonstringyes–
revisionintegeryesCurrent revision from slack.identity.read; 0 before the first save.

No output schema declared.

No examples provided.

summer_slack_reader_read ~68

Read who Summer reads Slack as: the connection itself (the Summer app or the installer's personal read access), an AI employee, or an admin's own Slack account, whether that account is connected, the revision and the change history.

NameTypeReqDescription
companystringyesSummer company ID

No output schema declared.

No examples provided.

summer_slack_reader_update ~147

Choose who Summer reads Slack as, with the revision from slack.reader.read and a reason. 'me' uses the caller's own connected Slack account; nobody can choose another person's account. Summer reads only the selected channels that account can see. Sends no message.

NameTypeReqDescription
companystringyesSummer company ID
idempotency_keystring–Reuse the same key when retrying the same change
readerstringyes–
reasonstringyes–
revisionintegeryesCurrent revision from slack.reader.read; 0 before the first save.
teammate_id––An active teammate from teammates.list when reader is 'teammate'.

No output schema declared.

No examples provided.

summer_slack_sender_update ~192

Choose who posts approved vendor Slack replies: the Summer Ellis app, a Summer Teammate (AI employee) from its own Slack account, or the person who approves each reply, from their own connected Slack account. Uses the revision from slack.identity.read and a reason. Sends no message.

NameTypeReqDescription
companystringyesSummer company ID
idempotency_keystring–Reuse the same key when retrying the same change
reasonstringyes–
revisionintegeryesCurrent revision from slack.identity.read; 0 before the first save.
senderstring–Who posts. Leave out to choose from teammate_id alone. 'approver' posts as whoever approves each reply; that person needs their own Slack account connected (slack.account.read).
teammate_id–yesAn active teammate from teammates.list when sender is 'teammate', otherwise null.

No output schema declared.

No examples provided.

summer_support_policy_read ~30

Read business hours, holidays, response commitments and scheduled policy revisions.

NameTypeReqDescription
companystringyes–

No output schema declared.

No examples provided.

summer_support_policy_update ~98

Save business hours and response commitments with the expected revision and an effective date.

NameTypeReqDescription
calendarobjectyes–
commitmentsarrayyes–
companystringyes–
effectiveAt–yes–
expectedRevisionintegeryes–
idempotency_keystring–Reuse the same key when retrying the same change
pauseOnCustomerWaitbooleanyes–
reasonstringyes–

No output schema declared.

No examples provided.

summer_teammates_create ~86

Add a teammate. A managed teammate gets first.last@gosummer.ai, unique across Summer. A company-managed teammate uses the company's own address. Invites no one, joins no Slack workspace and sends nothing.

NameTypeReqDescription
companystringyes–
idempotency_keystring–Reuse the same key when retrying the same change
request–yes–

No output schema declared.

No examples provided.

summer_teammates_list ~37

List the company's teammates with their address, photo, status, unread mail count and Slack connection.

NameTypeReqDescription
companystringyes–

No output schema declared.

No examples provided.

summer_teammates_mailbox_get ~56

Read one message in a Summer-managed teammate's mailbox, including its text. Marks it read for the team.

NameTypeReqDescription
companystringyes–
messagestringyes–
teammatestringyes–

No output schema declared.

No examples provided.

summer_teammates_mailbox_list ~76

List mail received by a Summer-managed teammate, newest first, with sender, subject and a short preview. Company-managed teammates have no mailbox in Summer.

NameTypeReqDescription
beforestring–Messages received before this time
companystringyes–
limitinteger––
teammatestringyes–

No output schema declared.

No examples provided.

summer_teammates_names_list ~73

List suggested female and gender-neutral teammate names whose gosummer.ai address is still free. Each has a suggested photo_url to show; create with use_suggested_photo: true to add that name, address and photo together. Any typed first and last name also works.

NameTypeReqDescription
companystringyes–

No output schema declared.

No examples provided.

summer_teammates_setup_status ~73

Live status of each step to get a teammate posting approved replies in vendor Slack channels: Slack connected, teammate added, Slack invitation received, teammate connected, chosen as sender, in each vendor channel, and agent replies allowed there. Unreadable sources are reported as unknown.

NameTypeReqDescription
companystringyes–

No output schema declared.

No examples provided.

summer_teammates_slack_channels_join ~95

Join a public Slack channel as the connected teammate. Sends no message. A private or shared channel needs someone in it to /invite the teammate in Slack.

NameTypeReqDescription
channelstringyesPublic Slack channel ID from teammates.setup.status
companystringyes–
idempotency_keystring–Reuse the same key when retrying the same change
teammatestringyes–

No output schema declared.

No examples provided.

summer_teammates_slack_disconnect ~88

Disconnect a teammate's Slack account from Summer and delete its saved token. The Slack account itself stays in the workspace. Connecting needs the Slack sign-in in Summer settings.

NameTypeReqDescription
companystringyes–
idempotency_keystring–Reuse the same key when retrying the same change
reasonstringyes–
teammatestringyes–

No output schema declared.

No examples provided.

summer_teammates_slack_dms_list ~77

List the people who can DM this AI employee in Slack, with the list revision. Each DM from one of them opens an Ops case; a person approves the exact reply before the AI employee posts it. Needs a company owner or administrator.

NameTypeReqDescription
companystringyes–
teammatestringyes–

No output schema declared.

No examples provided.

summer_teammates_slack_dms_update ~167

Add or remove one person who can DM this AI employee, with the expected list revision and a reason. Summer reads only DMs from people on the list. Removing someone stops Summer reading and posting in that DM. Sends nothing.

NameTypeReqDescription
allowedbooleanyestrue adds the person; false removes them.
companystringyes–
idempotency_keystring–Reuse the same key when retrying the same change
reasonstringyes–
revisionintegeryesCurrent list revision from teammates.slack.dms.list (0 for an empty list).
slack_user_idstringyesThe person's Slack member ID in the company's workspace, such as U012AB3CD.
teammatestringyes–

No output schema declared.

No examples provided.

summer_teammates_slack_link_create ~117

Make a one-time link that connects the teammate's Slack account. Open it in the browser signed in to Slack as the teammate and select Allow; no Summer sign-in is needed there. It works once, for 15 minutes, and the connection is recorded as yours. Treat the link like a password. Needs a company owner or administrator.

NameTypeReqDescription
companystringyes–
idempotency_keystring–Reuse the same key when retrying the same change
teammatestringyes–

No output schema declared.

No examples provided.

Install

How do I install the Summer MCP server?

Summer is a hosted endpoint at https://api.gosummer.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · api.gosummer.ai

# add to Claude Code
claude mcp add --transport http ai-gosummer-summer 'https://api.gosummer.ai/mcp'
Common questions

What is the Summer MCP server?

Summer is an MCP server listed in the public MCP registry as ai.gosummer/summer. Telehealth support for Claude, Codex and Cursor: investigate cases and connect your tools. This page covers its hosted endpoint (https://api.gosummer.ai/mcp).

Is the Summer MCP server safe to use?

Summer scores 80 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Summer MCP server expose?

Summer exposes 161 tools: summer_github_issues_read, summer_github_connection_read, summer_github_connection_start, summer_github_repositories_list, summer_github_folders_list, and 156 more. Their descriptions and schemas cost roughly 13,767 tokens of context every time the server is loaded.

Does the Summer MCP server require authentication?

Yes. Summer asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the Summer MCP server still maintained?

Summer is still listed as active in the MCP registry. We last reached this channel on 24 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.