MCP
Model Context Protocol (MCP) servers extend Claude Code with external tools and services, like adding specialized tools to a developer's toolbox.
What MCP Enables
MCP provides a standardized way for Claude Code to:
- Execute tools - Call external functions and receive structured results
- Access resources - Read data from URIs (files, APIs, databases)
- Use prompts - Apply pre-defined prompt templates
- Receive events - React to notifications from connected servers
Quick Start
Install the Agronod plugins marketplace to get curated tools immediately:
/plugin marketplace add agronod/claude-plugins
/plugin install dev@agronod-pluginsThen use tools naturally in conversation:
# Claude automatically chooses the right tools
> Review my changes and create a commit with a good message
> Remember we're using PostgreSQL with Redis for caching
> Find all TODO comments in the codebaseResources
How MCP Works
Technical deep-dive into MCP architecture, tool discovery, and how Claude uses available servers.
Learn more →Installation
Install from the Agronod marketplace or manually via CLI commands.
Learn more →Server Directory
Curated directory of recommended MCP servers with installation instructions and use cases.
Learn more →Safety Guidelines
Best practices for securely installing and configuring MCP servers, including source verification and credential management.
Learn more →Custom Development
Build your own MCP servers to integrate specialized tools and workflows.
Learn more →Related
- Agronod Plugins Guide - Marketplace overview and workflows
- Troubleshooting - Solve MCP server issues
- Chat - Use MCP servers through conversation