clickup-operator MCP server

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is clickup-operator MCP server?

The clickup-operator MCP server is a tool designed to facilitate note storage and management through a custom URI scheme, allowing users to create, summarize, and manage notes efficiently.

how to use clickup-operator MCP server?

To use the clickup-operator MCP server, run the command uv --directory C:\Users\noahv\Documents\GitHub\clickup-operator run clickup-operator in your terminal. Ensure you have the necessary configuration set up in your Claude Desktop application.

key features of clickup-operator MCP server?

  • Custom note storage system with a note:// URI scheme.
  • Ability to add new notes with a name and content.
  • Summarization of all stored notes with adjustable detail levels.

use cases of clickup-operator MCP server?

  1. Storing and managing personal notes for easy access.
  2. Summarizing notes for quick reviews before meetings or study sessions.
  3. Integrating with other applications to enhance note-taking capabilities.

FAQ from clickup-operator MCP server?

  • How do I add a new note?

You can add a new note by using the add-note tool, providing the required name and content arguments.

  • Can I customize the summary detail level?

Yes! The summarization feature allows you to choose between brief and detailed summaries.

  • What is the note:// URI scheme?

The note:// URI scheme is a custom protocol used to access individual notes stored in the server.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
0
Language
Python
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago