Once you can connect an MCP server, the next question hits fast: which ones? There are thousands of public servers now — wonderful for capability, overwhelming for choosing.

The good news is that most people's real needs are covered by a small, well-established set. Here's the opinionated starter map — the five categories that pay off soonest, so you build something useful today instead of collecting connections you never touch.

1Filesystem — the universal first win

If you connect only one server, make it this one. A filesystem server lets your assistant read and write files in a folder you choose, turning it from something you copy and paste into and out of, into something that works directly with your documents, drafts, and notes.

It's the most tangible "aha" moment in MCP, and it benefits everyone. Start here, point it at one dedicated folder, and you'll feel the shift from feeding the assistant to directing it.

2Repository — for anyone who writes code

If software is your work, a server connecting your code platform is transformative. It lets the assistant read issues, examine code across a project, and help manage the work where it lives, instead of you pasting fragments back and forth.

Because it can see the surrounding code rather than an isolated snippet, its suggestions fit. This turns "help me with this function" into "read this issue, find the relevant code, and propose a fix."

3Web fetch — break the training cutoff

An unconnected assistant only knows what it was trained on. A web-fetching server gives it a way to pull in and read current pages on demand, so it can reason from the actual source rather than stale internal knowledge. For research or anything time-sensitive, this is the server that grounds it in what's published now.

4Docs / Knowledge — bring your own context in

Pair the outside world with your own materials. A server that reaches your documents and notes lets the assistant blend external information with your internal context — pulling the right document into a question, or cross-referencing your notes against a current source. It stops being a general oracle and becomes one that knows your specific material.

5Messaging — for work that's mostly coordination

If your day is conversations as much as creation, a messaging server earns its place. It can summarize a channel you've been away from or help draft a reply in context, turning a wall of unread messages into something the assistant can digest and act on.

How to actually choose

Start with the filesystem server, then add the one or two that match where your real work lives. Resist connecting all five at once — each server is a capability and a responsibility, and a small, deliberate stack is easier to trust and keep secure than a sprawling one. And before connecting anything that touches an important account, take a moment to trust the publisher: prefer first-party servers for anything that genuinely matters.

Which server would you connect first — files, or straight to your code?