Ecosystem at a Glance: MCP, Tools, and Cookbooks

The wider Claude ecosystem

Around the SDKs sit three things worth knowing on day one: Model Context Protocol (MCP) for plugging in external capabilities; built-in tools like web_search, code_execution, and computer_use; and the Anthropic Cookbook with reference implementations for everything from RAG to evaluations.

MCP in one paragraph

MCP is an open protocol that lets a Claude client connect to capability servers — filesystem, GitHub, databases, anything someone has wrapped. The Agent SDK and Claude Code CLI both support MCP servers natively. cwkPippa's Pippa surfaces several MCPs (vault, NetOps, image generation) so the same Claude can talk to them through the same protocol regardless of brain.

Cookbook is the reference shelf

The Anthropic Cookbook on GitHub holds working notebooks for tool use patterns, RAG pipelines, evals, vision, and prompt caching. When the docs feel abstract, the cookbook is where the executable example lives. Bookmark it; it ages better than your bookmarks of random tutorials.

Principle: Treat MCP as the long-term integration surface and the Cookbook as the example shelf. Both move faster than your training data.

Code

Discover what MCP servers exist locally·bash

# Inside Claude Code CLI (interactive):
#   /mcp list
#
# From shell, peek at the project-local config:
cat .mcp.json 2>/dev/null || echo 'no project-level MCP config yet'

# Or the user-level config:
cat ~/.claude/mcp.json 2>/dev/null || echo 'no user-level MCP config yet'

Hand-launch a stdio MCP server (the simplest case)·json

{
  "mcpServers": {
    "pippa-vault": {
      "command": "node",
      "args": ["/Users/you_username/Obsidian/pippa/mcp/vault-server.js"]
    }
  }
}

Ecosystem at a Glance: MCP, Tools, and Cookbooks

The wider Claude ecosystem

MCP in one paragraph

Cookbook is the reference shelf

Code

External links

Exercise

Progress

Comments 0