MCP servers
Model Context Protocol servers give a model real access to something on your machine or account: a database, a repository, a file system, an issue tracker. The configuration is short, the consequences are not, so every entry here says what the server can reach and what it can change.
Slack MCP server
Lets the model read and post to the Slack channels it can access: search history, summarise a thread, or draft a message for you to send.
Tested on Claude Sonnet · Jun 2026
GitHub MCP server
Issues, pull requests and code search without leaving the conversation. Scope the token to what you need.
Tested on Claude Sonnet · May 2026
Notion MCP server
Gives the model access to your Notion pages and databases: read project docs, update a status field, or draft a new page from a conversation.
Tested on Claude Sonnet · Jun 2026
Filesystem MCP server
Gives the model read and write access to directories you name. The most useful MCP server and the one that deserves the most thought before you…
Tested on Claude Sonnet · May 2026
Fetch MCP server
Lets the model retrieve a URL and read it as text. Simple and useful, and the plainest case of untrusted input in the whole protocol.
Tested on Claude Sonnet · May 2026
PostgreSQL MCP server
Lets the model query your database directly. Read-only is the setting that counts, and it is not the default everywhere.
Tested on Claude Sonnet · May 2026