Extend Click applications with Model Context Protocol (MCP) support
Connect Click to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Extend Click applications with Model Context Protocol (MCP) support. The click mcp server is what makes that connection.
A Python library that extends Click applications with Model Context Protocol (MCP) support, allowing AI agents to interact with CLI tools.
click-mcp provides a simple decorator that converts Click commands into MCP tools. This enables AI agents to discover and interact with your CLI applications programmatically.
click-mcp on PyPI is all you need. Most clients run it directly, so configuration is a few lines and a restart.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
Setup — The Setup tool exposed by this serverTesting — The Testing tool exposed by this serverLinting — The Linting tool exposed by this serverBuilding — The Building tool exposed by this serverDocumentation — The Documentation tool exposed by this serverAmong the knowledge and memory options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Click's toolset — Setup, Testing, Linting and 2 more — is a fair guide to whether it matches your workflow. It is maintained by Stephen Crowe; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Setup | The Setup tool exposed by this server. |
| Testing | The Testing tool exposed by this server. |
| Linting | The Linting tool exposed by this server. |
| Building | The Building tool exposed by this server. |
| Documentation | The Documentation tool exposed by this server. |
{
"mcpServers": {
"click": {
"command": "uvx",
"args": ["click-mcp"]
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
A knowledge graph your assistant keeps between sessions — entities, relations and observations that persist.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
A structured scratchpad for hard problems — stepwise reasoning with revisions, branches and visible logic.
Symbol-level code navigation, refactoring and memory for coding agents — the IDE brain your assistant has been missing.
Chat with your second brain — search, read and write vault notes through the Local REST API.