8 min read
Lesson 2 of 6
Using Pre-Built MCP Servers
From the course MCP & AI Tool Integration: Connect AI to Everything
You don't need to build MCP servers from scratch — there's a rich ecosystem of pre-built servers ready to use. Here's how to find, install, and configure them.
Finding MCP Servers
- Smithery.ai — The largest MCP server registry with thousands of servers
- GitHub MCP Servers org — Official reference implementations
- npm / PyPI — Many servers published as packages
- Glama.ai — Curated directory with ratings and reviews
Installing MCP Servers in Claude Desktop
Claude Desktop uses a configuration file to define MCP servers:
{
"mcpServers": {
"filesystem": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-filesystem", "/Users/you/Documents"]
},
"github": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-github"],
"env": {
"GITHUB_TOKEN": "ghp_your_token_here"
}
}
}
}
Popular MCP Servers
File System — Read, write, and search files on your computer GitHub — Create issues, PRs, read repos, manage projects PostgreSQL / SQLite — Query and analyze databases Brave Search — Web search from within AI conversations Slack — Read channels, send messages, search history Google Drive — Access and search your documents Puppeteer — Browser automation and web scraping
Configuring in Cursor / VS Code
AI code editors support MCP through settings:
{
"mcp.servers": {
"database": {
"command": "npx",
"args": ["-y", "mcp-server-postgres", "postgresql://localhost/mydb"]
}
}
}
Security Considerations
- Review what permissions each server requests before enabling
- Use read-only database connections when possible
- Scope file system access to specific directories
- Store API keys in environment variables, not config files
- Regularly audit which servers have access to sensitive data
Key Takeaways
- •Smithery.ai and GitHub are the main sources for pre-built MCP servers
- •Configure servers via JSON in Claude Desktop, Cursor, or VS Code
- •Popular servers cover file systems, GitHub, databases, search, and Slack
- •Always review permissions and scope access to minimum required
- •Store API keys in environment variables, not configuration files
0 of 6 lessons marked complete
Progress is kept in this browser only.