claude-desktop-mcp-server

Created By
mows21a year ago
Claude Desktop MCP Server - Local desktop AI agent with file access and notifications
Overview

what is Claude Desktop MCP Server?

Claude Desktop MCP Server is a local desktop AI agent that provides file access and notifications, enabling users to interact with their files and receive updates seamlessly.

how to use Claude Desktop MCP Server?

To use Claude Desktop MCP Server, install the application on your desktop, configure the necessary permissions for file access, and start the server to begin receiving notifications and interacting with your files.

key features of Claude Desktop MCP Server?

  • Local AI agent for desktop use
  • File access capabilities
  • Notification system for updates and alerts

use cases of Claude Desktop MCP Server?

  1. Managing files and receiving notifications about changes.
  2. Automating tasks on the desktop with AI assistance.
  3. Enhancing productivity by integrating file management with AI notifications.

FAQ from Claude Desktop MCP Server?

  • Can Claude Desktop MCP Server access all file types?

Yes! It can access various file types as long as the necessary permissions are granted.

  • Is Claude Desktop MCP Server free to use?

Yes! It is free to use for everyone.

  • How does the notification system work?

The notification system alerts users about file changes and updates in real-time.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
mows21
Star
0
Language
-
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)

2 days ago