Ms 365 MCP Server vs Qmailing MCP Server
A side-by-side look at the Ms 365 MCP Server and Qmailing MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Ms 365 MCP Server for communication work as a local process; choose Qmailing MCP Server for communication as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Ms 365 MCP Server when
- You need dedicated capabilities in the Communication domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: OAuth 2.0.
- You want tools like
login, logout, verify-login.
Choose Qmailing MCP Server when
- You need dedicated capabilities in the Communication domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
QMAILING_API_TOKEN. - You want tools like
qmailing_list_mailboxes, qmailing_get_mailbox, qmailing_create_mailbox.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Communication | Communication |
| Quality signal | 73/100 · Great | 60/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | OAuth 2.0 | API key required |
| Pricing | Free | Paid service |
| Required env vars | None listed | QMAILING_API_TOKEN |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1,071 | 1 |
| Directory activity | 7 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | 19 | 10 |
| Full listing | View Ms 365 MCP Server | View Qmailing MCP Server |
Tools & capabilities
Ms 365 MCP Server tools 19
loginAuthenticate with Microsoft accountlogoutLog out from Microsoft accountverify-loginCheck current Microsoft authentication statuslist-accountsList all Microsoft accounts configured in this server. Use this to discover available account emails before making tool calls. Reflects accounts added mid-session via --login.select-accountSelect a Microsoft account as the default. Accepts email address (e.g. user@outlook.com) or account ID. Use list-accounts to discover available accounts.remove-accountRemove a Microsoft account from the cache. Accepts email address (e.g. user@outlook.com) or account ID. Use list-accounts to discover available accounts.graph-batchCombine up to 20 Graph requests into a single HTTP call. Body: { requests: [{ id: '1', method: 'GET'|'POST'|'PATCH'|'DELETE', url: '/me/messages?$top=5', headers?: {...}, body?: {...}, dependsOn?: ['1'] }, ...] }. Returns { responses: [{ id, status, body, headers }] } in arbitrary order — match by id. Use cases: (1) parallelize many small reads (e.g. fetch 15 mail messages by id in one round-trip); (2) sequence dependent writes via dependsOn; (3) batch many Excel range writes into one call to dramatically reduce latency on large workbook builds. Note: each sub-request URL is relative to the Graph version root (/me/..., /drives/..., NOT https://graph.microsoft.com/v1.0/...). 💡 TIP: Combine up to 20 Graph requests into a single HTTP call. Body: { requests: [{ id: '1', method: 'GET'|'POST'|'PATCH'|'DELETE', url: '/me/messages?$top=5', headers?: {...}, body?: {...}, dependsOn?: ['1'] }, ...] }. Returns { responses: [{ id, status, body, headers }] } in arbitrary order — match by id. Use cases: (1) parallelize many small reads (e.g. fetch 15 mail messages by id in one round-trip); (2) sequence dependent writes via dependsOn; (3) batch many Excel range writes into one call to dramatically reduce latency on large workbook builds. Note: each sub-request URL is relative to the Graph version root (/me/..., /drives/..., NOT https://graph.microsoft.com/v1.0/...).list-subscriptionsRetrieve the properties and relationships of webhook subscriptions, based on the app ID, the user, and the user's role with a tenant. The content of the response depends on the context in which the app is calling; for details, see the scenarios in the Permissions section. 💡 TIP: Lists webhook subscriptions owned by the current app/user. Returns id, resource, changeType, notificationUrl, expirationDateTime, clientState. Use $filter=resource eq '/me/messages' to find subscriptions for a specific resource. No dedicated 'Subscription.*' scope exists — the caller must already have a read permission for the subscribed resource (e.g. Mail.Read for /me/messages), which is supplied by the tool that reads that resource.create-subscriptionSubscribes a listener application to receive change notifications when the requested type of changes occur to the specified resource in Microsoft Graph. To identify the resources for which you can create subscriptions and the limitations on subscriptions, see Set up notifications for changes in resource data: Supported resources. Some resources support rich notifications, that is, notifications that include resource data. For more information about these resources, see Set up change notifications that include resource data: Supported resources. 💡 TIP: Creates a webhook subscription for change notifications. Required body: { changeType (comma-separated: 'created,updated,deleted'), notificationUrl (HTTPS, must validate with token echo), resource (e.g. '/me/mailFolders/inbox/messages', '/users/{id}/events', '/teams/{id}/channels/{id}/messages'), expirationDateTime (ISO 8601, max varies by resource type — 1 hour for calls, 24h for messages, 3 days for mail), clientState (opaque string returned in notifications, for validation) }. Optional: includeResourceData (true enables rich notifications, requires encryptionCertificate + encryptionCertificateId). No dedicated scope — caller must have a read permission for the target resource (e.g. Mail.Read, Calendars.Read, ChannelMessage.Read.All, Files.Read.All).get-subscriptionRetrieve the properties and relationships of a subscription. See the table in the Permissions section for the list of resources that support subscribing to change notifications. 💡 TIP: Gets a specific webhook subscription by id. Use list-subscriptions to find the id. Returns full subscription details including resource, changeType, notificationUrl, expirationDateTime, applicationId.update-subscriptionRenew a subscription by extending its expiry time. The table in the Permissions section lists the resources that support subscribing to change notifications. Subscriptions expire after a length of time that varies by resource type. In order to avoid missing change notifications, an app should renew its subscriptions well in advance of their expiry date. See subscription for maximum length of a subscription for each resource type. 💡 TIP: Renews a webhook subscription by extending its expiration. Body: { expirationDateTime (ISO 8601, new expiry) }. Call before the current expirationDateTime to avoid missing notifications. Max extension varies by resource type — check Microsoft Graph docs for subscription limits.delete-subscriptionDelete a subscription. For the list of resources that support subscribing to change notifications, see the table in the Permissions section. 💡 TIP: Deletes a webhook subscription. No further change notifications will be sent. Use this to clean up stale subscriptions or stop receiving notifications. Use list-subscriptions to find the id.- +7 more on the listing page
Qmailing MCP Server tools 10
qmailing_list_mailboxesList every mailbox on the accountqmailing_get_mailboxFetch one mailbox by idqmailing_create_mailboxCreate a new mailbox under qmailing.com or a verified custom domainqmailing_list_domainsList custom domains and verification stateqmailing_get_dns_recordsDNS-records checklist for one domainqmailing_list_emailsList a mailbox folder (incl. `MUTED`); items carry `muted` + `suspicious` flagsqmailing_get_emailFetch one email with full body + attachment metadataqmailing_get_attachmentFetch one attachment's bytes (Base64, 5 MiB inline cap)qmailing_send_emailSend mail (recipients, subject, HTML/text, attachments)qmailing_register_webhookManage event webhooks
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Ms 365 MCP Server
{
"mcpServers": {
"softeria-ms-365-mcp-server": {
"command": "npx",
"args": [
"-y",
"@softeria/ms-365-mcp-server"
]
}
}
}
Qmailing MCP Server
{
"mcpServers": {
"thesameabramovych-qmailing-mcp-server": {
"command": "npx",
"args": [
"-y",
"@qmailing/mcp-server"
],
"env": {
"QMAILING_API_TOKEN": "YOUR_QMAILING_API_TOKEN_HERE"
}
}
}
}
Frequently asked questions
Ms 365 MCP Server is categorized under Communication and uses a local stdio subprocess. Qmailing MCP Server belongs to Communication and uses a local stdio subprocess. Pick Ms 365 MCP Server for communication work and Qmailing MCP Server for communication.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Ms 365 MCP Server is listed as free. Auth: oauth 2.0. Qmailing MCP Server is listed as a paid service. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add softeria-ms-365-mcp-server and thesameabramovych-qmailing-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Ms 365 MCP Server has a quality signal of 73/100 (Great) with 7 views, 0 installs and 1,071 GitHub stars. Qmailing MCP Server has 60/100 (Good) with 4 views, 0 installs and 1 GitHub stars.