// 11 tips in MCP Servers
Working with Model Context Protocol servers.
Scaffold a custom MCP server with Claude to give it direct access to your internal APIs, dashboards, and microservices.
Use --strict-mcp-config to restrict Claude Code to only the MCP servers you explicitly provide, ignoring all other sources.
When an MCP server misbehaves, /mcp gives you a live view of every connected server, its status, and the tools it's exposing — right inside your session.
Add the Slack MCP server to let Claude post deployment updates, incident alerts, or standup summaries directly to your channels.
The Filesystem MCP server gives Claude read/write access to whole directories, unlocking bulk file operations, cross-project searches, and codebase-wide audits without copying content into the chat.
The Postgres MCP server gives Claude read access to your real schema and data — so it writes SQL against your actual tables, not imaginary ones.
Give Claude live access to the web by connecting the Brave Search MCP server — no more answers that stop at its training cutoff.
Configure MCP servers at user scope for cross-project tools and project scope for repo-specific connections — both configs merge at runtime.
The GitHub MCP server gives Claude Code read/write access to your repos, issues, and PRs — all from the terminal.
Extend Claude Code with MCP servers to add database access, GitHub integration, web search, and more — right from the terminal.
Use the Laravel Boost MCP server to give Claude access to version-specific Laravel docs, your database schema, and read-only SQL queries — all without leaving the conversation.