MCP Servers: Adding New Capabilities

Model Context Protocol turns any tool into something Claude Code can call. Adding the right MCP servers expands what the agent can actually do for you.

10 min · Reviewed 2026

Why MCP exists

Before MCP, every agent had its own bespoke way of integrating with every tool — different glue per agent, per service. MCP standardizes the contract: a server exposes tools, an agent calls them, both sides speak the same protocol. That standard turned 'plug Claude into Linear' from a custom integration into a one-line config.

What MCP gives Claude Code

Tools beyond the filesystem and shell — calendar, ticketing, design, data, deploy
Per-server permission scoping — Claude can only do what the server exposes
A growing ecosystem of community servers for almost every product
Symmetry with other agents — the same MCP servers work in Cursor, Windsurf, and beyond
Local servers (process on your machine) and remote servers (HTTP)

Servers worth wiring up early

A web search / browse server — for retrieval the agent can drive itself
A ticketing / issue server (Linear, GitHub Issues, Jira) — agents that resolve tickets, not just discuss them
A docs / wiki server — Notion, Confluence, your team's internal pages
A scheduling server — read calendars, propose times, never auto-send invites without approval
A data warehouse server (Postgres, Snowflake) read-only, with strict scopes

{
  "mcpServers": {
    "linear": {
      "command": "npx",
      "args": ["-y", "@org/linear-mcp"],
      "env": { "LINEAR_API_KEY": "$LINEAR_API_KEY" }
    },
    "docs": {
      "url": "https://mcp.example.com/docs",
      "transport": "http"
    }
  }
}A typical MCP server config block. Local servers run as processes; remote servers connect via HTTP.

Apply: add one server thoughtfully

Pick a tool you spend real time in (Linear, Notion, GitHub)
Find the official or top-rated MCP server for it
Read the source — confirm it does what it says, scoped how it claims
Wire it up with the most restrictive token scope that still works
Use it for a week; decide if it earned its keep before adding the next one

The big idea: MCP is how the agent gets bigger hands. Add servers deliberately, scope them tightly, and audit before installing.

End-of-lesson check

15 questions · take it digitally for instant feedback at tendril.neural-forge.io/learn/quiz/end-claude-code-mcp-creators

What is the core idea behind "MCP Servers: Adding New Capabilities"?
1. Model Context Protocol turns any tool into something Claude Code can call. Adding the right MCP servers expands what the agent can actually do for you.
2. Greenfield work where the architecture is the whole task
3. ExitPlanMode
4. Files where keeping line numbers stable matters less than getting the new shape …
Which term best describes a foundational idea in "MCP Servers: Adding New Capabilities"?
1. server
2. MCP
3. permission scope
4. capability surface
A learner studying MCP Servers: Adding New Capabilities would need to understand which concept?
1. MCP
2. permission scope
3. server
4. capability surface
Which of these is directly relevant to MCP Servers: Adding New Capabilities?
1. MCP
2. server
3. capability surface
4. permission scope
Which of the following is a key point about MCP Servers: Adding New Capabilities?
1. Tools beyond the filesystem and shell — calendar, ticketing, design, data, deploy
2. Per-server permission scoping — Claude can only do what the server exposes
3. A growing ecosystem of community servers for almost every product
4. Symmetry with other agents — the same MCP servers work in Cursor, Windsurf, and beyond
Which of these does NOT belong in a discussion of MCP Servers: Adding New Capabilities?
1. Tools beyond the filesystem and shell — calendar, ticketing, design, data, deploy
2. Greenfield work where the architecture is the whole task
3. A growing ecosystem of community servers for almost every product
4. Per-server permission scoping — Claude can only do what the server exposes
Which statement is accurate regarding MCP Servers: Adding New Capabilities?
1. A ticketing / issue server (Linear, GitHub Issues, Jira) — agents that resolve tickets, not just dis…
2. A docs / wiki server — Notion, Confluence, your team's internal pages
3. A web search / browse server — for retrieval the agent can drive itself
4. A scheduling server — read calendars, propose times, never auto-send invites without approval
Which of these does NOT belong in a discussion of MCP Servers: Adding New Capabilities?
1. A docs / wiki server — Notion, Confluence, your team's internal pages
2. Greenfield work where the architecture is the whole task
3. A web search / browse server — for retrieval the agent can drive itself
4. A ticketing / issue server (Linear, GitHub Issues, Jira) — agents that resolve tickets, not just dis…
What is the key insight about "MCP changed the agent landscape" in the context of MCP Servers: Adding New Capabilities?
1. Before MCP, picking an agent meant inheriting its tool surface.
2. Greenfield work where the architecture is the whole task
3. ExitPlanMode
4. Files where keeping line numbers stable matters less than getting the new shape …
What is the key insight about "MCP is a new attack surface" in the context of MCP Servers: Adding New Capabilities?
1. Greenfield work where the architecture is the whole task
2. Every MCP server is code your agent calls. A malicious or poorly-scoped server can read files, exfiltrate secrets, or ex…
3. ExitPlanMode
4. Files where keeping line numbers stable matters less than getting the new shape …
What is the key insight about "From the community" in the context of MCP Servers: Adding New Capabilities?
1. Greenfield work where the architecture is the whole task
2. ExitPlanMode
3. On r/ClaudeAI, the most-shared MCP setup gotcha is the shell-environment trap — Claude Code launches MCP server subproce…
4. Files where keeping line numbers stable matters less than getting the new shape …
Which statement accurately describes an aspect of MCP Servers: Adding New Capabilities?
1. Greenfield work where the architecture is the whole task
2. ExitPlanMode
3. Files where keeping line numbers stable matters less than getting the new shape …
4. Before MCP, every agent had its own bespoke way of integrating with every tool — different glue per agent, per service.
What does working with MCP Servers: Adding New Capabilities typically involve?
1. The big idea: MCP is how the agent gets bigger hands. Add servers deliberately, scope them tightly, and audit before installing.
2. Greenfield work where the architecture is the whole task
3. ExitPlanMode
4. Files where keeping line numbers stable matters less than getting the new shape …
Which best describes the scope of "MCP Servers: Adding New Capabilities"?
1. It is unrelated to tools workflows
2. It focuses on Model Context Protocol turns any tool into something Claude Code can call. Adding the right MCP serv
3. It applies only to the opposite beginner tier
4. It was deprecated in 2024 and no longer relevant
Which section heading best belongs in a lesson about MCP Servers: Adding New Capabilities?
1. Greenfield work where the architecture is the whole task
2. ExitPlanMode
3. What MCP gives Claude Code
4. Files where keeping line numbers stable matters less than getting the new shape …

← Back to interactive lesson

Tendril · Creators · Tools Literacy