Community Gmail server with auto-auth: search, read and send email via MCP.
Outlook Classic 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
Mail, calendar and contacts of classic Outlook on Windows via COM. Single EXE, no Graph app.
Quickstart
Install it the way its author documents:
The full guide: https://github.com/jli-software/outlook-classic-mcp/releases/download/v1.3.1/outlook-classic-mcp.mcpb
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 Outlook Classic 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.
Install it the way its author documents:
The full guide: https://github.com/jli-software/outlook-classic-mcp/releases/download/v1.3.1/outlook-classic-mcp.mcpb
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.
Lists the newest emails in an Outlook folder (default: Inbox). Returns ID, subject, sender, date, preview and read status.
No parameter schema on file.
Searches one folder (default Inbox) or, with folder='all', every mail folder of the mailbox by subject, sender or body text. With 'all' every hit shows its folder; results are sorted by date across all folders (newest first) and 'top' applies to the total.
No parameter schema on file.
Reads one or more complete emails including body text by ID. Several IDs in ONE call are much faster than several calls.
No parameter schema on file.
Creates an email DRAFT in Outlook.
No parameter schema on file.
Changes an existing DRAFT. Only the fields you pass are changed (ideal for corrections instead of creating a new draft).
No parameter schema on file.
Creates a REPLY draft to an existing email (thread and quote of the original added automatically, RE: subject, recipients prefilled).
No parameter schema on file.
Creates a FORWARD draft of an existing email (original text and attachments included, FW: subject). Resolve names to addresses with contacts_resolve first.
No parameter schema on file.
No parameter schema on file.
Triggers Send/Receive in classic Outlook and refreshes the local cache. Useful BEFORE reading or searching when classic Outlook rarely runs (e.g. because the user works in the new Outlook). Returns the Inbox item and unread counts afterwards.
No parameter schema on file.
Lists the mailbox's complete folder tree with path, EntryID, item count and unread count. Use the ID as target for mail_move / mail_create_folder.
No parameter schema on file.
Creates a new folder. Without parent_id it is created under the Inbox.
No parameter schema on file.
Moves one or more emails into a folder.
No parameter schema on file.
Marks one or more emails as read or unread.
No parameter schema on file.
Sets Outlook categories (color tags) on one or more emails. Replaces existing categories.
No parameter schema on file.
Moves one or more emails to Deleted Items (never deletes permanently).
No parameter schema on file.
Lists the attachments of one or more emails (index, file name, size in bytes).
No parameter schema on file.
Saves attachments of one or more emails to local disk and returns the file paths (readable afterwards with normal file reading).
No parameter schema on file.
Searches your Outlook contacts (name, company, email) and the company directory (Global Address List, by name) for people and distribution lists. Returns name, SMTP email, company, department, phone and an ID for contacts_get. Word order doesn't matter ('Smith Anna' finds 'Anna Smith').
No parameter schema on file.
Turns a person's name into their email (SMTP) address — use this before writing a draft to someone you only know by name. Returns exactly one address, or the list of candidates if the name is ambiguous (never guesses).
No parameter schema on file.
Shows all details of one or more contacts or directory entries by ID (from contacts_search/contacts_list): emails, phones, company, department, job title, office, address, manager, notes.
No parameter schema on file.
Lists your own Outlook contacts (not the company directory), sorted by name.
No parameter schema on file.
Shows the signed-in mailbox (name, email), Outlook version and connection state, and this server's settings: whether sending is possible and which folders attachments may be read from or saved to.
No parameter schema on file.
Lists appointments and meetings in the default calendar that overlap a time range (default: today to +7 days), recurring occurrences included, sorted by start. Returns ID, time, subject, location, show-as, organizer and your response.
No parameter schema on file.
Shows full details of one or more calendar items: description, attendees with their responses, Teams join link, reminder, categories.
No parameter schema on file.
Creates an appointment in the default calendar. With attendees it becomes a meeting that is SAVED BUT NOT SENT — the user opens it in Outlook and clicks Send. Resolve names to addresses with contacts_resolve first.
No parameter schema on file.
Changes a calendar item. Only the fields you pass are changed; moving the start keeps the duration. For a series pass an occurrence ID to change only that occurrence. Attendees are NOT notified — for a meeting you organize the user sends the update in Outlook.
No parameter schema on file.
Delete appointments or single occurrences
No parameter schema on file.
Answers a meeting invitation you received: accept, tentative or decline. The response is saved as a DRAFT in Drafts.
No parameter schema on file.
Shows when people are busy on one day (free/busy from Exchange, in 30-minute blocks) — e.g. to find a time for a meeting. Works for colleagues in your organization; external addresses usually have no data.
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 Outlook Classic 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 | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | metadata | inspection depth (metadata) — how much of the target the scan could see | −8 |
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>".
The implementation source was not read — the published package was fetched but contains no source files the scanner reads.
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
It installs from its repository rather than from a versioned package, so the command cannot be pinned to a release. The history below is for reading; the current release on file is 1.3.1.
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 Outlook Classic 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.