Community Gmail server with auto-auth: search, read and send email via MCP.
OpenSES email on your own Amazon SES is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
OpenSES email on your own Amazon SES: shared inbox, sending, delivery status, contacts, sequences.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user openses-email-on-your-own-amazon-ses-mcp '--' npx -y openses-mcp
# 2 — ask your agent for something these tools do
# inboxes_list, inbox_threads, inbox_read and 25 more
Remote: API key · Package: no sign-in.
OpenSES email on your own Amazon SES costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one can run either way — at an address its publisher runs, or as a process under your own user, with your files and your network — and this marketplace is in the path of neither.
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user openses-email-on-your-own-amazon-ses-mcp '--' npx -y openses-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Its publisher also runs it at https://api.openses.email/mcp: nothing to start on your machine, and this marketplace is not in the path.
claude mcp add --scope user --transport http openses-email-on-your-own-amazon-ses-mcp https://api.openses.email/mcpNothing is required, but it can take OPENSES_API_KEY (Optional API key from the OpenSES dashboard. Without it, sign-in opens in the browser.), OPENSES_API_URL (Optional base URL of a self-hosted OpenSES API.) if you want to set them.
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
28 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
The account's inboxes with unread counts.
No parameter schema on file.
List conversations, filtered by inbox, unread, archived or text.
No parameter schema on file.
Read a conversation, with delivery status for sent messages.
No parameter schema on file.
Reply to a conversation as its inbox address.
No parameter schema on file.
Start a new conversation from an inbox.
No parameter schema on file.
Mark read or unread, archive, or label a conversation.
No parameter schema on file.
A short-lived download link for an attachment.
No parameter schema on file.
Send an email from a verified domain, now or scheduled.
No parameter schema on file.
Search sent email by recipient, subject, status, tag or age.
No parameter schema on file.
One email with its full delivery timeline.
No parameter schema on file.
Cancel a scheduled email.
No parameter schema on file.
SES sending health, quota and bounce and complaint rates.
No parameter schema on file.
Domains with verification state and DNS records.
No parameter schema on file.
Addresses that are never sent to.
No parameter schema on file.
Block an address in every region.
No parameter schema on file.
Allow a suppressed address again.
No parameter schema on file.
Find contacts by email, name, company, topic or consent.
No parameter schema on file.
Create or update a contact.
No parameter schema on file.
Unsubscribe a contact from everything.
No parameter schema on file.
Delete a contact.
No parameter schema on file.
Topics contacts subscribe to, with subscriber counts.
No parameter schema on file.
Sequences with their steps and enrollment counts.
No parameter schema on file.
Enroll a contact in a sequence.
No parameter schema on file.
Take a contact out of a sequence.
No parameter schema on file.
Saved templates and their placeholders.
No parameter schema on file.
One template with its bodies.
No parameter schema on file.
Create or update a template.
No parameter schema on file.
Broadcasts with status and results.
No parameter schema on file.
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install OpenSES email on your own Amazon SES or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. high is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 1.0.0. Pin a release below and the command asks for exactly that one.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish OpenSES email on your own Amazon SES can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.