About clickup-operator MCP server
clickup-operator MCP server is a small server implementation described as connecting ClickUp through Claude. Its documented components store notes, expose them as resources, and provide a prompt for summarizing them.
Key features
- 01Add notes with name and content
- 02Expose notes as resources
- 03Summarize stored notes
- 04Choose brief or detailed style
Use cases
- 01Store notes on the server
- 02Retrieve individual notes as resources
- 03Summarize a collection of notes
- 04Adjust summary detail
MCP support
The server exposes a note-adding tool, note resources, and a summarize-notes prompt to MCP clients.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEclickup-operator MCP server
clickup thru claude
uv --directory C:\Users\noahv\Documents\GitHub\clickup-operator run clickup-operator
Components
Resources
The server implements a simple note storage system with:
- Custom note:// URI scheme for accessing individual notes
- Each note resource has a name, description and text/plain mimetype
Prompts
The server provides a single prompt:
- summarize-notes: Creates summaries of all stored notes
- Optional "style" argument to control detail level (brief/detailed)
- Generates prompt combining all current notes with style preference
Tools
The server implements one tool:
- add-note: Adds a new note to the server
- Takes "name" and "content" as required string arguments
- Updates server state and notifies clients of resource changes
Configuration
[TODO: Add configuration details specific to your implementation]
Quickstart
Install
Claude Desktop
On MacOS: ~/Library/Application\ Support/Claude/claude_desktop_config.json
On Windows: %APPDATA%/Claude/claude_desktop_config.json
Development/Unpublished Servers Configuration
``` "mcpServers": { "clickup-operator": { "command": "uv", "args": [ "--directory", "C:\Users\noahv\Documents\GitHub\create-python-server\clickup-operator", "run", "clickup-operator" ] } } ```Published Servers Configuration
``` "mcpServers": { "clickup-operator": { "command": "uvx", "args": [ "clickup-operator" ] } } ```Development
Building and Publishing
To prepare the package for distribution:
- Sync dependencies and update lockfile:
uv sync
- Build package distributions:
uv build
This will create source and wheel distributions in the dist/ directory.
- Publish to PyPI:
uv publish
Note: You'll need to set PyPI credentials via environment variables or command flags:
- Token:
--tokenorUV_PUBLISH_TOKEN - Or username/password:
--username/UV_PUBLISH_USERNAMEand--password/UV_PUBLISH_PASSWORD
Debugging
Since MCP servers run over stdio, debugging can be challenging. For the best debugging experience, we strongly recommend using the MCP Inspector.
You can launch the MCP Inspector via npm with this command:
npx @modelcontextprotocol/inspector uv --directory C:\Users\noahv\Documents\GitHub\create-python-server\clickup-operator run clickup-operator
Upon launching, the Inspector will display a URL that you can access in your browser to begin debugging.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.