Summer

This connector has been deprecated

This was a duplicate manual listing. Use Summer’s official listing, imported from the official MCP Registry. Summer’s MCP server remains active at https://api.gosummer.ai/mcp. Setup and documentation: https://gosummer.ai/docs/mcp-clients.

Add a support email address

summer_messenger_email_create

Add a support email address. Summer creates its private forwarding address and signing key and returns the DNS record to add. The address starts off; nothing is sent.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "company": "<company>",
      "environment": "<environment>",
      "support_address": "<support_address>",
      "display_name": "<display_name>"
    },
    "name": "summer_messenger_email_create"
  }
}

Input Schema

Name	Required	Description
`company`	Yes	Summer company ID
`environment`	Yes	Environment that owns the resource
`display_name`	Yes	Sender name customers see on replies.
`idempotency_key`	No	Reuse the same key when retrying the same change
`installation_id`	No	Messenger installation whose inbox the emails join. Defaults to the first installation.
`support_address`	Yes	The address customers already write to, such as support@example.com.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 22, 2026

TDQS

B3.4/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare non-read-only, non-destructive, non-idempotent, open-world. The description adds real value by disclosing hidden side effects (private forwarding address and signing key creation) and that the address begins inactive so nothing is sent. It stops short of stating permissions required, what the DNS record looks like, or consequences of an already-existing address.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences; the action is front-loaded, followed by side effects and then the inactive-state caveat. No wasted clauses.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description helpfully discloses the return value (a DNS record to add) and the initial inactive state. It is nearly complete for a create tool; missing only prerequisite/ordering guidance (DNS verification) and what happens on conflict with an existing address.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so all six parameters (including idempotency_key and installation_id defaults) are already documented inline. The description only echoes the support-address concept and adds no format or constraint detail beyond the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Add') and resource ('support email address'), plus what gets provisioned behind the scenes (forwarding address, signing key). It doesn't explicitly contrast with the sibling tools summer_messenger_email_update/email_read/email_check, but 'Add' vs. those names makes the distinction inferable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No statement of when to prefer this over summer_messenger_email_update, nor prerequisites such as whether DNS must be verified before mail flows. The only usage-adjacent cue is that the address starts inactive, which is behavioral rather than a when-to-use rule.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Summer tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?