MCP, tools, and integrations · Lesson 2
Useful MCP servers
A catalog of vetted open-source servers for common tasks.
Server categories
- Context: filesystem, memory, knowledge bases.
- Working with code: git, github, gitlab, jira, linear.
- Communication: slack, discord, gmail, calendar.
- Databases: postgres, sqlite, supabase.
- Search: brave, perplexity, exa.
- Web: playwright, puppeteer, browserless.
What to install first
- Filesystem — basic file work.
- Git/GitHub — for code and issue tracking.
- Memory — a simple local agent memory.
- Search — Brave or Exa for search.
What to pay attention to
- Who maintains it (official / community).
- When the last commit was.
- Which tokens/keys are required.
- Which operations are "destructive" — they write / delete.
Security
- Never give a server more rights than it needs.
- For destructive servers — a separate account / read-only keys where possible.
- Regularly review the list of connected servers.
Practical exercise
What to do after this lesson
Assemble a minimal set: filesystem + git + search. Use it for 1 week — see whether you need more.
Ready-to-use prompt
Template for this lesson
Copy and adapt to your context. Text in angle brackets should be replaced.
Here is the list of MCP servers I want to connect: 1. <…> 2. <…> 3. <…> Help me check: - What each one does. - Which rights are required. - Whether there are destructive operations. - Whether there are lower-privilege alternatives.
Common mistakes
What people get wrong
- Connecting 20 servers at once — losing control.
- Using read-write where read-only would do.
- Not updating servers — old versions can have bugs.
Pro tips
What works but no one documents
- "Read only" for most scenarios.
- Dedicated service accounts for AI operations.
- Log all MCP calls.
When to use
Any AI client that supports MCP.
When not to use
When you need a single built-in tool.
Official sources
Квиз — 2 вопроса
1.What should be in a baseline set of MCP servers?
2.Which does NOT belong to MCP security?
Отвечено: 0 из 2