Skip to main content

Capstone: Extend Claude with MCP

Time: 30-60 minutes | Skills: MCP Configuration, Server Setup, Troubleshooting

The Scenario​

You have been asked to set up your development environment so that Claude Code can not only work with your local files but also interact with external services. Your goal is to configure at least two MCP servers, verify they work, and then use them together to complete a real task.

Requirements​

  1. Configure two or more MCP servers from the list below (or others you find)
  2. Verify each server connects using /mcp
  3. Complete a task that uses both servers in a single conversation
  4. Troubleshoot at least one issue (even if you have to create one intentionally)

Choose a combination based on what you have available:

CombinationWhat You Need
Filesystem + GitHubA GitHub account with a Personal Access Token
Filesystem + Brave SearchA free Brave Search API key
Filesystem + MemoryNothing extra — both work without API keys
Easiest Starting Point

If you do not have API keys set up, use the Filesystem + Memory combination. Neither requires an API key, so you can focus on configuration and usage.

Step-by-Step Guide​

Part 1: Configure the Servers​

Add your two chosen servers. For example, Filesystem and Memory:

claude mcp add filesystem -- npx -y @modelcontextprotocol/server-filesystem C:\Users\YourName\Documents

claude mcp add memory -- npx -y @modelcontextprotocol/server-memory

Verify with:

claude mcp list

Part 2: Verify Connections​

  1. Start Claude Code: claude
  2. Type /mcp and verify both servers show as connected
  3. If either server failed, apply the troubleshooting techniques from Lesson 4:
    • Try npx.cmd on Windows
    • Check for path issues
    • Run the server command directly in the terminal

Part 3: Complete a Combined Task​

Use both servers in a single conversation. Here are example tasks for each combination:

Filesystem + Memory:

  • Ask Claude to read files from your Documents folder and summarize what projects are there
  • Then ask Claude to store that summary in its memory
  • Start a new Claude session and ask Claude to recall what it knows about your projects

Filesystem + GitHub:

  • Ask Claude to read a project folder and create a GitHub issue describing a feature you want to add
  • Ask Claude to list your recent GitHub issues and save the list to a file in a specific directory

Filesystem + Brave Search:

  • Ask Claude to read a code file, identify a library it uses, search the web for that library's documentation, and save a summary to a notes file

Part 4: Troubleshoot​

If everything worked perfectly in Part 2, practice troubleshooting by intentionally breaking something:

  1. Edit your settings to introduce a typo in a server name
  2. Try to use the broken server and observe the error
  3. Fix the issue and verify the server reconnects

Self-Assessment​

  • Configured at least 2 MCP servers (using CLI or settings.json)
  • Verified both servers connect successfully with /mcp
  • Used MCP tools from both servers to complete a real task
  • Troubleshot at least one connection issue (real or intentional)
  • Understand the difference between global and project-level configuration
Help Us Improve

How was this lesson? Take 2 minutes to share your feedback — it helps us make the tutorials better for everyone.

Give Feedback →