Community Gmail server with auto-auth: search, read and send email via MCP.
Langmail MCP for your own Stalwart: email, calendar 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
Self-hosted MCP server for Stalwart: email, calendar and contacts over JMAP, CalDAV and CardDAV.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --env 'STALWART_URL=${STALWART_URL}' --transport stdio langmail-mcp-for-your-own-stalwart-email-calendar '--' npx -y langmail-mcp
# 2 — ask your agent for something these tools do
# update_calendar_event, search_contacts, search_emails and 36 more
It needs STALWART_URL: this reads it from your environment, so export it first.
Langmail MCP for your own Stalwart: email, calendar 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 runs on your machine: your client starts Langmail MCP for your own Stalwart: email, calendar as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
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. Claude Code reads STALWART_URL (Base URL of your Stalwart server (JMAP, CalDAV and CardDAV), e.g. https://mail.example.com) from your environment each time it starts the server, so the value stays out of its config: export it in your shell profile (macOS, Linux), or run setx STALWART_URL … and open a new terminal (Windows). The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user --env 'STALWART_URL=${STALWART_URL}' --transport stdio langmail-mcp-for-your-own-stalwart-email-calendar '--' npx -y langmail-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
It reaches a system of yours, so it needs settings only you can give it: STALWART_URL — Base URL of your Stalwart server (JMAP, CalDAV and CardDAV), e.g. https://mail.example.com. You set it in your own client’s config, on your machine — this marketplace never holds it.
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.
39 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.
Update, edit or reschedule an existing calendar event or meeting: move it to a new time,
| Parameter | Type | Required | Notes |
|---|---|---|---|
| addedAttendees | array | no | Email addresses to invite on top of the stored attendees. Cannot be combined with attendees. |
| attendees | yes | The complete attendee list after the edit; [] uninvites everyone. Omit to keep the stored attendees, or use addedAttendees/removedAttendees instead. | |
| calendarUrl | yes | — | |
| description | yes | New description; "" clears it. Omit to keep the stored one. | |
| end | no | New end, ISO 8601, or an exclusive date for an all-day event. Omit to keep the event’s length when moving start, its stored end otherwise. | |
| location | yes | New location; "" clears it. Omit to keep the stored one. | |
| notify | string | no | all (default) re-notifies the attendees by iMIP; none edits silently. |
| recurrence | no | New repeat rule for the whole series; "none" makes it a one-off. Omit to keep the stored rule. … | |
| recurrenceId | no | To change one occurrence of a repeating series alone, its original start as an ISO 8601 instant (e.g. 2026-06-16T10:00:00Z), or its date for an all-day series (2026-06-16). Not combinable with `recurr | |
| reminderMinutesBefore | no | Minutes before the start to remind the user (all-day events start at 00:00, so 900 = 09:00 the day before); replaces any stored reminders. "none" removes them. Omit to keep the stored ones. | |
| removedAttendees | array | no | Email addresses to uninvite (case-insensitive). Cannot be combined with attendees. |
| start | no | New start, ISO 8601, or a date (2026-10-03) for an all-day event. Omit to keep the stored start. | |
| timeZone | yes | IANA zone for the start/end you pass, e.g. Europe/Berlin: their clock digits are read as wall-clock time here, overriding any offset. Defaults to the event’s own stored zone. Times you omit keep their | |
| title | no | New title. Omit to keep the stored one. | |
| uid | yes | — |
Resolve a person's name, partial name, email address, organization, or what
| Parameter | Type | Required | Notes |
|---|---|---|---|
| context | string | no | Biases address ranking when a person has addresses in several contexts. work prefers organization-domain addresses; private prefers personal-domain addresses. Never filters a person out entirely. |
| limit | integer | no | Maximum number of matching people. |
| query | string | yes | Name, partial name, email address, organization, or what the person is to the user ("lawyer", "my landlord"). Matched against display names, organizations, addresses, address domains, and the roles st |
| response_format | string | no | concise returns name, contact id, roles, best address, confidence, relationship, the birthday when stored, and the last interactions. detailed adds all known addresses with their own confidence, p |
Search the authenticated user's mailbox. Combine free-text (query —
| Parameter | Type | Required | Notes |
|---|---|---|---|
| after | no | Only messages received on/after this UTC ISO-8601 timestamp, e.g. "2026-04-01T00:00:00Z" (start of "last 3 months"). Filters the RECEIVED date, not any date the message talks about: a confirmation arr | |
| before | no | Only messages received strictly before this UTC ISO-8601 timestamp, e.g. "2026-07-01T00:00:00Z". Filters the received date; for an event-anchored request, end the window at the event rather than bound | |
| cursor | string | no | The cursor a previous search_emails result printed, to get the page after it. Pass it exactly as printed, with the same query and filters as that search (limit may change); leave it out to start from |
| from | string | no | Substring match on the sender name or address. |
| keywords | array | no | — |
| limit | integer | no | Hits per page, 1–…. When more match, the page prints a cursor for the next one. |
| mailbox | string | no | Restrict to a named mailbox/folder (e.g. "Inbox"). The standard places — Inbox, Sent, Archive, Drafts, Trash, Junk — resolve to the folder holding that role, so they work under whatever name the serve |
| query | string | no | Free-text search over subject, body, and addresses. Terms are OR'd — a message matches if it contains ANY term. Messages containing every term come first, then the rest ranked within their page by how |
| read | boolean | no | false finds only unread messages, true only read ones. Leave out to match both. Without mailbox it covers every folder, so { read: false } alone is "everything not read yet", Archive, Junk and Trash i |
| starred | boolean | no | true finds only starred messages, false only unstarred ones. Leave out to match both. |
Edit a staged draft that has not been sent. Omitted fields keep their staged values; an empty
| Parameter | Type | Required | Notes |
|---|---|---|---|
| attachments | no | … Omit to keep the files already attached; pass an empty array to remove them all. Supplying the field replaces the whole list, so to add one more file, list the existing ones by the blobIds get_draft | |
| bcc | yes | — | |
| cc | yes | — | |
| draftId | string | yes | The draft id, as returned by create_draft or list_drafts — edits do not change it — or a message id from search_emails with mailbox: "Drafts". Editing a draft found that way returns the draftId to u |
| html | string | no | Replace the HTML body. On a reply, write only the new part: the quoted original is re-attached below it, so do not paste the quote from get_draft back in. Omit to keep the body. |
| quoteOriginal | boolean | no | On a reply, with text or html: whether the original is quoted below the new text. Defaults to whatever the staged draft does — unless the same call adds a to/cc/bcc recipient the original wa |
| subject | string | no | Replace the subject. Omit to keep it. |
| text | string | no | Replace the plain-text body. On a reply, write only the new part: the quoted original is re-attached below it, so do not paste the quote from get_draft back in. Omit to keep the body. |
| to | yes | — |
Archive one or more messages: remove them from the Inbox and file them in the Archive
No parameter schema on file.
Creates a new calendar for the authenticated user, with an optional color. Use this when the
| Parameter | Type | Required | Notes |
|---|---|---|---|
| color | string | no | — |
| name | string | yes | — |
Create, schedule or book a new calendar event or meeting on the user’s calendar, and invite
| Parameter | Type | Required | Notes |
|---|---|---|---|
| attendees | array | no | Email addresses to invite; each receives an iMIP invitation. Omit for a personal event — a block of the user’s own time — with no invitations sent. |
| calendarUrl | string | no | — |
| description | string | no | — |
| end | yes | Event end as ISO 8601 (see timeZone). For an all-day event a date, exclusive: the day after the last day (a day off on 2026-10-03 ends 2026-10-04). | |
| location | string | no | — |
| notify | string | no | Whether to send the iMIP invitations. all (default) sends them; none invites nobody. |
| recurrence | no | Repeat rule; omit for a one-off event. start/end are its first occurrence. … | |
| reminderMinutesBefore | integer | no | Remind the user this many minutes before the start (e.g. 30); omit for no reminder. An all-day event starts at 00:00, so 900 = 09:00 the day before. |
| showAs | string | no | Whether this event counts as busy time. busy (default) means it does; free means it does not — for holds, reminders and travel buffers the user does not want counted against their availability. In |
| start | yes | Event start as ISO 8601 (see timeZone), or a date (2026-10-03) for an all-day event. | |
| timeZone | no | IANA zone for start/end, e.g. Europe/Berlin: their clock digits are read as wall-clock time here, overriding any offset. Defaults to the account timezone, then UTC. | |
| title | string | yes | — |
Create a contact in the user’s address book — a person the address book does not
| Parameter | Type | Required | Notes |
|---|---|---|---|
| birthday | no | — | |
| emails | array | no | Email addresses for this person. A contact does not need one — a name alone is a valid record. |
| name | string | yes | The display name, e.g. "Robin Fairweather". |
| note | string | no | Free-text note about the person. |
| organization | string | no | Company or organization the person belongs to. |
| phones | array | no | Phone numbers for this person. |
| postalAddresses | array | no | Postal addresses, structured by component. |
| roles | array | no | What the person is to the user ("lawyer", "landlord"), so a later "write to my lawyer" finds them. Only roles the user said or confirmed; never inferred from mail. |
Write, compose or draft an email and stage it in the user’s Drafts folder without sending it.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| attachments | no | — | |
| bcc | yes | — | |
| cc | yes | — | |
| from | string | no | Sending address. Defaults to the authenticated account’s own address. Only an address this account is configured to send as (its aliases) is accepted; anything else is rejected rather than silently su |
| html | string | no | HTML body. Pass text as well when both are wanted — the two are sent as alternatives. |
| idempotencyKey | string | no | Client-chosen key that makes this call safe to retry: a repeat with the same key returns the first call’s answer instead of staging a second draft. |
| forwardOf | string | no | Id of a message to forward, as returned by search_emails or get_thread. The draft gets the "Fwd: …" subject, a "Forwarded message" block with the original’s From, Date, Subject, To and Cc below your t |
| inReplyTo | string | no | Id of the message this draft replies to, as returned by search_emails or get_thread. Sets the threading headers and defaults the subject to "Re: …" and the recipients to that message’s sender — pass ` |
| quoteOriginal | boolean | no | With inReplyTo: quote the original below the new text, under an "On …, <sender> wrote:" line, the way a mail client does. Defaults to true — unless to/cc/bcc name someone the original was not |
| replyAll | boolean | no | With inReplyTo: also Cc everyone the original was addressed to, minus the user themselves. Ignored without inReplyTo. |
| subject | string | no | Subject line. Defaults to "Re: …" when inReplyTo is set. |
| text | string | no | Plain-text body. |
| to | yes | — |
Create a persistent mail rule (filter) that automatically sorts, labels, archives or forwards
| Parameter | Type | Required | Notes |
|---|---|---|---|
| actions | yes | — | |
| conditions | yes | — | |
| existingMail | object | no | Optionally also apply the actions to mail already in the mailbox. Omit (or mode "none") to affect future mail only — the safe default unless the user asked for a cleanup too. |
| match | yes | — | |
| name | no | — |
Cancel, delete or remove a calendar event or meeting the user organizes, identified by its uid
| Parameter | Type | Required | Notes |
|---|---|---|---|
| calendarUrl | string | no | — |
| recurrenceId | no | — | |
| uid | yes | — |
Delete a contact by id, removing it from the account and from every device syncing
| Parameter | Type | Required | Notes |
|---|---|---|---|
| contactId | yes | — |
Permanently delete an unsent draft. Use this to retire a draft that is no longer wanted — for
| Parameter | Type | Required | Notes |
|---|---|---|---|
| draftId | string | yes | The draft id, as returned by create_draft, update_draft or list_drafts — edits do not change it — or a message id from search_emails with mailbox: "Drafts", which an edit replaces with the draftId i |
Delete a persistent mail rule by id so it stops applying to future incoming messages.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ruleId | string | yes | The id of the rule to delete, e.g. "rule-1a2b3c4d" — as returned by create_mail_rule or list_mail_rules. |
Get a short-lived download URL for one email attachment, identified
| Parameter | Type | Required | Notes |
|---|---|---|---|
| blobId | string | yes | The attachment blobId, as listed by search_emails, get_thread, or get_email for that message. |
| emailId | string | yes | The id of the message the attachment belongs to. |
Get a short-lived download URL for the raw source of one message: the full RFC 5322 / MIME
| Parameter | Type | Required | Notes |
|---|---|---|---|
| emailId | string | yes | The id of the message, as returned by search_emails or get_thread. |
Forward a message to someone and SEND it immediately. This delivers mail and cannot be undone —
| Parameter | Type | Required | Notes |
|---|---|---|---|
| bcc | yes | — | |
| cc | yes | — | |
| html | string | no | HTML version of the note above the forwarded message. |
| idempotencyKey | string | no | Client-chosen key that makes this call safe to retry: a repeat with the same key returns the first call’s answer instead of sending a second forward. Pass one whenever the call might be retried. |
| messageId | string | yes | Id of the message to forward, as returned by search_emails or get_thread. |
| subject | string | no | Override the subject. Defaults to "Fwd: <original subject>". |
| text | string | no | Optional note above the forwarded message, in plain text. Write only the note: the original follows it. |
| to | yes | — |
Read a staged draft back: its sender, every recipient including bcc, subject, whether it is
| Parameter | Type | Required | Notes |
|---|---|---|---|
| draftId | string | yes | The draft id, as returned by create_draft, update_draft or list_drafts — edits do not change it — or a message id from search_emails with mailbox: "Drafts", which an edit replaces with the draftId i |
Fetch a single message's recipients and body by id. The body is
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | The message id, as returned by search_emails or get_thread. |
List every message in the same thread as a given message id, oldest-first
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | A message id; every message in its thread is returned. |
Read the user’s calendar, agenda or schedule — what’s on their calendar, what meetings they
| Parameter | Type | Required | Notes |
|---|---|---|---|
| calendarUrl | string | no | — |
| end | no | — | |
| start | no | — |
Lists the authenticated user's calendars — the calendars themselves, not the events on them.
No parameter schema on file.
List the drafts staged in the user's Drafts folder, newest first, optionally narrowed by a subject or
| Parameter | Type | Required | Notes |
|---|---|---|---|
| after | no | Only drafts last staged or edited on/after this UTC ISO-8601 timestamp, e.g. "2026-10-01T00:00:00Z". | |
| before | no | Only drafts last staged or edited strictly before this UTC ISO-8601 timestamp, e.g. "2026-10-08T00:00:00Z". | |
| limit | integer | no | How many drafts to return, newest first. Up to …. |
| query | string | no | Whole words matched against the subject and every recipient (to, cc, bcc), by name or address — e.g. "invoice", "Nadia" or "nadia@example.org". A fragment of a word does not match: "invo" finds nothin |
List the persistent mail rules with their ids, names, enabled state, conditions,
No parameter schema on file.
List the contacts whose birthday falls within the next days days (7 for a
| Parameter | Type | Required | Notes |
|---|---|---|---|
| days | integer | no | Length of the window in days, counting from as day 0: 7 for a week (Monday through Sunday), 30 for a month, 90 for a quarter. Defaults to 30. |
| from | string | no | First day of the window as YYYY-MM-DD. Defaults to today in the account’s time zone (UTC when none is set) — pass the user’s local date when you know it. A past date answers "which birthdays did I m |
| limit | integer | no | Maximum number of people to list. Defaults to 25. |
Set or clear the flags on one or more messages: read / unread, to-do, and starred.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| read | boolean | no | true marks the messages read, false marks them unread. Leave out to keep read state. |
| starred | boolean | no | true stars the messages, false removes the star. Leave out to keep it. |
| todo | boolean | no | true flags the messages as a to-do for the user, false clears the to-do (e.g. once it is done). Leave out to keep it. |
Merge duplicate contacts — the same person or organization collected under several addresses —
| Parameter | Type | Required | Notes |
|---|---|---|---|
| contactId | yes | The contact to keep, as printed by search_contacts under contact_id. Its name, organization and birthday win. | |
| mergeContactIds | array | yes | The contacts to fold into it and then delete, as printed by search_contacts under contact_id. Up to 10. |
| preferredEmail | string | no | The address mail to this contact should go to, from any of the merged contacts. Omit it to keep the preferred address the kept contact has now. |
Moves events from one of the user’s calendars to another — for example into a new "Private"
| Parameter | Type | Required | Notes |
|---|---|---|---|
| calendar | string | yes | Destination calendar: its name (matched ignoring case) or its URL, both as list_calendars shows them. It must already exist; calendars are never created here. |
| fromCalendar | string | no | Only needed when a uid exists in more than one calendar: the calendar to move it out of, by name or URL. Omit otherwise; each event is found wherever it is. |
| uids | array | yes | Events to move, by the uid list_calendar_events shows. A recurring event moves as a whole series, including its changed occurrences. Up to … per call. |
Move one or more messages into a folder. They are removed from every folder they were in
| Parameter | Type | Required | Notes |
|---|---|---|---|
| mailbox | string | yes | Destination folder. The standard places — Inbox, Archive, Sent, Drafts, Junk — resolve to the folder holding that role whatever the server calls it; any other value must match an existing folder name |
Validate a proposed mail rule and estimate its effect WITHOUT creating or changing
| Parameter | Type | Required | Notes |
|---|---|---|---|
| actions | yes | — | |
| conditions | yes | — | |
| existingMail | object | no | The existing-mail policy being considered — its scope decides where matches are counted (default: inbox). |
| match | yes | — | |
| name | no | — |
Reply to a message and SEND the reply immediately. This delivers mail to the recipients and
| Parameter | Type | Required | Notes |
|---|---|---|---|
| bcc | array | no | Blind-copy these addresses on the reply. Never derived from the original — a reply only ever bcc’s who you name here. Cannot be combined with replyAll. |
| cc | yes | — | |
| html | string | no | HTML body of the reply. |
| idempotencyKey | string | no | Client-chosen key that makes this call safe to retry: a repeat with the same key returns the first call’s answer instead of sending a second reply. Pass one whenever the call might be retried. |
| messageId | string | yes | Id of the message being replied to, as returned by search_emails or get_thread. |
| quoteOriginal | boolean | no | Quote the original below the new text, under an "On …, <sender> wrote:" line, the way a mail client does. Defaults to true — unless to/cc/bcc name someone the original was not addressed to, wher |
| replyAll | boolean | no | Reply to everyone: the original’s To and Cc are added to Cc, minus the user themselves. Cannot be combined with to, cc, or bcc. |
| subject | string | no | Override the subject. Defaults to "Re: <original subject>". |
| text | string | no | Plain-text body of the reply. |
| to | yes | — |
RSVP to a calendar invite or meeting invitation on the authenticated user’s behalf — accept,
| Parameter | Type | Required | Notes |
|---|---|---|---|
| calendarUrl | string | no | — |
| response | string | yes | — |
| uid | yes | — |
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
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 Langmail MCP for your own Stalwart: email, calendar 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 | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| 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. minimal 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 0.2.0. Pin a release below and the command asks for exactly that one.
No release note was published with this version.
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
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 Langmail MCP for your own Stalwart: email, calendar 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.