Security & Testing
gosummer.ai
An MCP server for Summer account and access management, exposing tools to view user identity, company access, access requests, and agent connection grants.
ENDPOINT 1
https://api.gosummer.ai/mcp
MCP server metadata
- Name
- summer
- Version
- 0.2.0
Summer company setup and case tools. Public discovery lists tool schemas only. Every tool call requires a Summer OAuth access token; a 401 response points to the authorization metadata. Start with summer_account_me and summer_company_capabilities. Write for the intended reader: customers for public guides and staff for internal procedures. Follow ASD-STE100 about 80%. Use short sentences, active voice, one idea per sentence and consistent terms. Avoid metaphors and technical slang. Keep necessary facts and uncertainty. Customize welcome copy, home/chat buttons and lead fields through installation settings.presentation. Website buttons open HTTPS links; lead_capture buttons open the consent form. Read the issuer's /docs/messenger-leads guide. Saved submissions emit messenger.lead.submitted through the existing signed webhooks, including the company and installation IDs. Webhook setup needs automation.manage. Read leads with cases.read. Booking handoff codes expire after 15 minutes and require the selected company's server to exchange them. Never treat contact details as account identity or claim a saved lead is a confirmed booking. Read the issuer's /docs/support-email guide before configuring support email. Identify the support address, mail provider, receiving inbox and permitted sender. Test reading, sending and DNS separately. Intercom's account check does not test inbox access or replies. This catalog has help-desk setup and credential storage. It has no direct Gmail/Outlook connector or email DNS commands. Use an existing authorized help-desk API or browser workflow when available. Saved credentials and custom integration definitions do not establish a working connection. Record test results, original message references, check times and missing steps in capability checks. Follow the company's reply and approval rules. Help-center DNS configures website addresses, not email. Keep website conversations in chat unless the visitor wants email follow-up. Contact capture does not send email. Read operational_readiness or summer_capability_checks_list for the same checklist shown in Summer. Fulfill tasks through discoverable APIs, browsers, current knowledge or combined paths. Upload relevant knowledge, configure integrations and record evidence with summer_capability_checks_report; add useful business-specific expectations with summer_capability_checks_save. A saved credential or guide alone does not prove a working path. Setup-agent reports never imply human approval or independently verified execution. Report saved, verified, pending, unavailable and enabled states exactly as returned; saved is not verified. Never ask a person to paste a secret into chat. Secret values, signing keys and service account secrets move only through the local Summer CLI; tools that would need one return a handoff command. An approved setup connection includes installing and enabling Messenger in its selected companies and environments, including production, within current budgets. Complete requested setup without asking for the same permission again or escalating installation to another agent. A local CLI handoff is a trusted secret-transfer step: run it locally when available, keeping keys out of model-visible output. Ask only for genuinely missing company/environment access or authority. This does not grant business-effect approval or investigation authority. Company settings and knowledge are company-wide. Credentials, Messenger installations and cases belong to one environment. Author company guidebooks with summer_guides_get, summer_guides_save and summer_guides_articles_save. Upload media metadata with summer_assets_uploads_create, then transfer the selected local file with the returned CLI command; never send base64 or binary through tools. Use native tools for writing, real screenshots and optional image/video creation. Preview the exact article revisions before summer_guides_publish, which needs guides.publish authority. Published customer URLs and internal knowledge citations have different audiences. Investigators, executors and conversational agents reference the same published company articles; a guide never proves a customer action completed. These are never available to an agent: Approving a business effect, outgoing customer message or plan execution; Revealing a saved credential value; Approving Summer platform access requests; Ownership transfer and owner/admin role grants; Raising model or assistant spending limits; Identity-verification attestations and clinical directions.
Known tools 65
summer_account_meShow the signed-in person, Summer access status and this connection's grant.
Inferred read-onlysummer_account_companies_listList companies the person can access and whether this connection includes each one.
Inferred read-onlysummer_account_connections_listList this person's agent connections, grants, last use and expiry.
Inferred read-onlysummer_account_connections_revokeRevoke one of this person's agent connections immediately.
Inferred read-onlysummer_guides_getRead the company's editable guidebook, draft articles, assets and publication state.
Inferred read-onlysummer_guides_articles_getRead an editable guide article and its current knowledge revision.
Inferred read-onlysummer_guides_articles_saveCreate or edit a Markdown customer article with source references and managed asset IDs.
Potential side effectssummer_guides_previewRead the exact current draft, article revisions and authenticated preview URL before publishing.
Inferred read-onlysummer_guides_authoringGet the reviewed company-specific guide-building instructions for your native coding agent.
Inferred read-onlysummer_guides_publishPublish the exact selected article revisions and ready media to the company's customer help center.
Potential side effectssummer_guides_unpublishRemove the company's guide and release media from Summer's public serving path at the expected version.
Potential side effectssummer_guides_historyRead the company's guide edits, upload and publication history.
Potential side effectssummer_guides_hosting_getRead the optional custom guide domain, DNS instructions and verified HTTPS status.
Inferred read-onlysummer_guides_hosting_saveSave or remove a custom guide hostname at the expected version.
Potential side effectssummer_guides_hosting_verifyCheck the saved domain's DNS ownership, attach it through Summer's hosting connection and verify HTTPS.
Inferred read-onlysummer_assets_listList the company's private guide media, metadata and upload status.
Potential side effectssummer_assets_uploads_createStart or recover a private resumable Markdown, image, video, PDF or caption upload from metadata.
Potential side effectssummer_assets_uploads_completeVerify the original size, content signature and SHA-256 against saved private bytes, then mark a guide upload ready.
Potential side effectssummer_assets_editEdit guide media captions, alt text, provenance, transcript or poster at the expected version, or retire unused media.
Potential side effectssummer_company_capabilitiesWhat this connection can do here, with a reason for everything unavailable.
Inferred read-onlysummer_company_setup_statusSaved, verified, pending, unavailable and enabled state for each setup item.
Inferred read-onlysummer_capability_checks_listRead the same operational capability checklist, results, discovery paths and review history shown in Summer.
Inferred read-onlysummer_capability_checks_getRead one capability, its concrete test, evidence and latest 20 review records.
Inferred read-onlysummer_capability_checks_saveEdit a capability expectation or add a business-specific custom_ capability with a reason.
Potential side effectssummer_capability_checks_reportRecord the setup agent's capability assessment with original evidence and the path Summer can discover and use.
Inferred read-onlysummer_capability_checks_testRequest a read-only Summer capability test on an authorized sample case.
Inferred read-onlysummer_company_settings_updateUpdate company-wide settings with the expected version.
Potential side effectssummer_integrations_listList provider integrations, their required fields and saved metadata.
Inferred read-onlysummer_integrations_saveDefine a custom integration's credential names and labels.
Inferred read-onlysummer_knowledge_createUpload a new company knowledge document with original revision history.
Potential side effectssummer_knowledge_historyRead the edit history of a company knowledge document.
Potential side effectssummer_knowledge_editEdit an existing company knowledge document with the expected revision and a reason.
Potential side effectssummer_messenger_installations_listList Messenger installations in this environment.
Inferred read-onlysummer_messenger_installations_createCreate an installation with a client-chosen ID.
Potential side effectssummer_messenger_installations_updateUpdate installation settings with the expected version.
Potential side effectssummer_messenger_assistant_readRead assistant settings per installation and whether the managed runtime is enabled.
Inferred read-onlysummer_messenger_leads_listRead consented website leads for this company and environment.
Inferred read-onlysummer_messenger_assistant_updateUpdate assistant instructions and escalation permission with the expected revision.
Potential side effectssummer_messenger_voice_readRead voice chat settings per installation, the available voices, published help article count and the voice assistant's update status.
Potential side effectssummer_messenger_voice_updateUpdate voice chat settings with the expected revision.
Potential side effectssummer_messenger_conversations_assistantPause the assistant in one conversation so a person can take over, or ask it to resume.
Inferred read-onlysummer_cases_listList company-owned cases or conversations, newest first, with coverage and a cursor.
Inferred read-onlysummer_cases_getRead one case or conversation with its original messages and related records.
Inferred read-onlysummer_cases_attachmentGet a short-lived download for an attachment that belongs to this case.
Inferred read-onlysummer_investigations_listRead investigation runs, saved plans, approval state and execution receipts for a case.
Inferred read-onlysummer_investigations_requestAsk Summer to investigate the case, or revise a saved plan with feedback.
Inferred read-onlysummer_actions_preparePrepare the exact work in the current saved plan for human approval in Summer.
Inferred read-onlysummer_service_accounts_saveCreate, update, rotate or disable a service account.
Potential side effectssummer_webhooks_saveCreate, update, rotate or disable a signed webhook endpoint.
Potential side effectssummer_webhooks_replayQueue past events after a cursor for delivery again to one endpoint.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.summer]
url = "https://api.gosummer.ai/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"summer": {
"type": "http",
"url": "https://api.gosummer.ai/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: summer
Remote MCP URL: https://api.gosummer.ai/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"summer": {
"url": "https://api.gosummer.ai/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"summer": {
"type": "http",
"url": "https://api.gosummer.ai/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "summer",
"transport": "streamable-http",
"url": "https://api.gosummer.ai/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.