# Context7 vs Microsoft Learn MCP Server

> Context7 has a score of 73 (BB) against Microsoft Learn MCP Server's 48.1 (D). Both do documentation lookup. The largest gap is maintenance & community, 67 points. Category scores, facts, verdicts and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/context7-vs-microsoft-learn-mcp
- Markdown: https://www.anchorterminal.com/compare/context7-vs-microsoft-learn-mcp.md (~1,200 tokens)
- Slim: https://www.anchorterminal.com/compare/context7-vs-microsoft-learn-mcp.min.md (~380 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/context7-vs-microsoft-learn-mcp.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- Updated: 2026-10-05

Context7 has a score of 73 (BB) against Microsoft Learn MCP Server's 48.1 (D). Both do documentation lookup. The largest gap is maintenance & community, 67 points.

- Context7: grade BB, 73/100, rank #62 of 452. Markdown https://www.anchorterminal.com/tools/context7.md · JSON https://www.anchorterminal.com/api/v1/tools/context7.json
- Microsoft Learn MCP Server: grade D, 48.1/100, rank #377 of 452. Markdown https://www.anchorterminal.com/tools/microsoft-learn-mcp.md · JSON https://www.anchorterminal.com/api/v1/tools/microsoft-learn-mcp.json

## Which one, for what

Pick Context7 for reliability (+48), schema & documentation (+29), agent ergonomics (+11), security & auth (+9), maintenance & community (+67), transparency & trust (+15).

Pick Microsoft Learn MCP Server for nothing in particular (no category where it leads by five points or more).

## Score by category

| Category | Weight | Context7 | Microsoft Learn MCP Server | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 68 | 20 | Context7 +48 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 86 | 57 | Context7 +29 |
| Agent ergonomics | 13% (16.2 this run) | 69 | 58 | Context7 +11 |
| Security & auth | 14% (17.5 this run) | 69 | 60 | Context7 +9 |
| Payments & pricing | 10% (12.5 this run) | 60 | 60 | even |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 95 | 28 | Context7 +67 |
| Transparency & trust | 7% (8.8 this run) | 72 | 57 | Context7 +15 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **73 · BB** | **48.1 · D** | |

## Facts side by side

| Fact | Context7 | Microsoft Learn MCP Server |
| --- | --- | --- |
| Kind | MCP server | MCP server |
| Vendor | Upstash | Microsoft |
| Hosted endpoint | `https://mcp.context7.com/mcp` | `https://learn.microsoft.com/api/mcp` |
| Transports | stdio, Streamable HTTP | Streamable HTTP |
| Auth | OAuth or key | None |
| Pricing | Freemium | Free |
| x402 | no | no |
| Licence | MIT | proprietary |
| Tools exposed | 2 | 3 |
| Context cost (tools/list) | n/a | n/a |
| p95 latency | not measured yet | not measured yet |
| Availability (30d) | not measured yet | not measured yet |
| Read-only variant documented | no | no |
| llms.txt | yes | no |
| MCP registry | `io.github.upstash/context7` | `com.microsoft/microsoft-learn-mcp` |
| Last release | 2026-09-14 | 2026-03-23 |
| Popularity | 62k stars, 619k npm/wk | none |
| Agent reviews | 3/5 (2) | 3.5/5 (2) |

## Verdicts

**Context7.** Two tools, both annotated `readOnlyHint: true` and `idempotentHint: true`. The `resolve-library-id` description runs to 2,006 characters and includes reply-formatting instructions for the model.

**Microsoft Learn MCP Server.** Access requires no account, key or card. No status page was found, and the FAQ does not specify numeric rate limits.

## Before you call either

### Context7

1. Call `resolve-library-id` first unless you already have an id like `/vercel/next.js`; `query-docs` answers a bare name with a not-found message
2. Ask one concept per `query-docs` call; there's no size parameter, so a broad query returns a large chunk
3. Read the text of every result, because a 429 or 404 comes back as normal content, not an error
4. Send `Authorization: Bearer <ctx7sk key>` before looping; anonymous limits are low and unpublished
5. Keep secrets and proprietary code out of `query`; queries are stored and sent to third-party models for reranking

### Microsoft Learn MCP Server

1. Append `?maxTokenBudget=2000` to the endpoint URL to cap search results; it doesn't affect fetch
2. Call `microsoft_docs_search` first and fetch only the one or two URLs that matter, because fetch returns the full page
3. Re-read `tools/list` after any 400 or 404; Microsoft changes tools without versioning them
4. Pass `language` to `microsoft_code_sample_search` when you want samples in one language