Close vs Microsoft 365 Teams
Close is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). Microsoft 365 Teams is an MCP server published by mindstone. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-12. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace | ||
|---|---|---|
| Docker MCP Catalog | Listed Version: not stated No figure published Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.3.1 Forks (GitHub): 4 Stars (GitHub): 12 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | Close | Microsoft 365 Teams |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 12 |
| Forks (GitHub) (differs) | No figure on GitHub | 4 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (mcp.close.com/mcp) | On your machine (@mindstone/mcp-server-microsoft-teams) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | 5, secrets among them: 0 |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | Not stated | github.com/mindstone/mcp-servers |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | not checked yet | no remote endpoint we check |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
Close
Streamline sales processes with integrated calling, email, SMS, and automated workflows for small and scaling businesses.
Microsoft 365 Teams
Microsoft 365 Teams via Graph: list chats, read/send messages, list teams/channels, presence.
How to run each
Close
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Requires: CLOSE_API_KEY (secret)
Microsoft 365 Teams As a local MCP server: npm package
claude mcp add --env "MS_CLIENT_ID=<YOUR_MS_CLIENT_ID>" --env "MS_CONFIG_DIR=<YOUR_MS_CONFIG_DIR>" --transport stdio mcp-server-microsoft-teams -- npx -y @mindstone/mcp-server-microsoft-teamsRequires: MS_CLIENT_ID, MS_CONFIG_DIR
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Only Close asks for
CLOSE_API_KEY (secret)
Only Microsoft 365 Teams asks for
MICROSOFT_REQUEST_TIMEOUT_MSMS_ACCOUNT_EMAILMS_CLIENT_IDMS_CONFIG_DIRMS_MCP_PACKAGE_ID
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Close · What it can do: Microsoft 365 Teams · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.