Model Context Protocol (MCP) tool to interact with Claude Desktop on macOS
Model Context Protocol (MCP) tool to interact with Claude Desktop on macOS. That is what the claude assist mcp mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
A Model Context Protocol (MCP) server that enables Claude Code to communicate with Claude Desktop. This server allows Claude Code to send prompts to Claude Desktop and poll for responses.
Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
The server publishes 11 tools. What each one is for:
Tool — askParameters — { "prompt": "What is dependency injection?" }description — What changes to review (e.g., "authentication fix")polling_interval — How often to check for response (default: 1.5s)timeout — Maximum wait time for response (default: 30s)get_conversations — The get_conversations tool exposed by this serverWorkarounds — 1. Use Claude's API: For programmatic access to responses, consider using Claude's API directly instead of desktop automation 2. **ManualSetup — 1. Copy the example command to your Claude Commands directory: bash cp examples/claude-peer-review.md ~/.claude/commands/Usage — The peer review command accepts up to 3 arguments: - description: What changes to review (e.g., "authentication fix") - polling_interval: HowLinting — The Linting tool exposed by this serverTools — The Tools tool exposed by this serverConfiguration is passed through the environment: SKIP_CLAUDE_POLLING, LOG_LEVEL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
This sits in the file and storage access group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Claude Assist MCP's toolset — Tool, Parameters, description and 8 more — is a fair guide to whether it matches your workflow. It is maintained by dpaluy; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Tool | ask |
| Parameters | { "prompt": "What is dependency injection?" } |
| description | What changes to review (e.g., "authentication fix") |
| polling_interval | How often to check for response (default: 1.5s) |
| timeout | Maximum wait time for response (default: 30s) |
| get_conversations | The get_conversations tool exposed by this server. |
| Workarounds | 1. **Use Claude's API**: For programmatic access to responses, consider using Claude's API directly instead of desktop automation 2. **Manual verification**: After sending a prompt, manually check the Claude Desktop wind |
| Setup | 1. Copy the example command to your Claude Commands directory: bash cp examples/claude-peer-review.md ~/.claude/commands/ |
| Usage | The peer review command accepts up to 3 arguments: - **description**: What changes to review (e.g., "authentication fix") - **polling_interval**: How often to check for response (default: 1.5s) - **timeout**: Maximum wai |
| Linting | The Linting tool exposed by this server. |
| Tools | The Tools tool exposed by this server. |
{
"mcpServers": {
"claude-desktop": {
"command": "npx",
"args": ["mcp-claude-desktop"]
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| SKIP_CLAUDE_POLLING | Configuration value read at startup. | Optional |
| LOG_LEVEL | Configuration value read at startup. | Optional |
Scoped local file access — read, write, search and reorganise files in directories you explicitly allow.
Search and read your Drive — Docs, Sheets and files become context your assistant can actually use.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Chat with your second brain — search, read and write vault notes through the Local REST API.
Upload, search, transform and organise your Cloudinary media library from a chat window
Run an M&A data room — projects, folders, permissions and diligence Q&A — from an AI conversation.