MCP Overview
This section treats MCP servers as privileged integrations, not lightweight plugins.
Who This Section Is For
- engineers evaluating MCP-enabled workflows
- platform and security reviewers approving new integrations
- teams deciding whether a server should stay read-only, pilot-only, or prohibited
How To Read This Section
Most pages in this section are evaluation checklists, not verified installation guides. That is intentional.
Use a page as a verified implementation guide only when the repository can responsibly identify one implementation, its maintainer, host support, permissions, and revocation path.
Best First Pages
| Page | Purpose | Maturity |
|---|---|---|
| What is MCP? | understand the protocol and trust boundary | Most mature |
| Useful MCP Servers | choose categories worth evaluating | Strong |
| GitHub MCP | repo and PR access evaluation | Strong |
| Filesystem MCP | local file and shell risk framing | Strong |
| Supabase / Postgres MCP | database access evaluation | Strong |
Recommended Reading Order
- Read What is MCP?.
- Read Security and Permissions.
- Read MCP Approval Policy.
- Only then evaluate a category-specific page.
Current Limitations
- host behavior differs across clients
- many servers are community maintained
- account, plan, or network constraints often block local verification
- protocol support can be newer than an organization's approval process
Verification Note
Unless a page explicitly says otherwise, MCP pages here are Documentation verified or Needs verification. Treat them as approval aids, not deployment approvals.