Paste MCP
OfficialPaste MCP is a local MCP server that bridges AI tools to the Paste clipboard manager on macOS, keeping all data on-device. Here's what you can do:
Check connection status: Use
paste_statusto verify if Paste is running and available, with guidance on how to bring it online if tools are missingAccess clipboard history: Allow AI assistants (Claude, Codex, Cursor, etc.) to search and retrieve items from your Mac's clipboard history
Work with pinboards: Enable AI tools to pull clipboard items into context or save AI-generated output to Paste pinboards
Privacy-first local access: All operations run locally on your Mac — no data is sent to external servers
Paste MCP
Local MCP server for Paste. Give Claude, Codex, Cursor, and other AI tools access to your Mac's clipboard history and pinboards — without anything leaving your device.
Your assistant can search your clipboard items, pull one into context, or save its output to a pinboard.
Install
Use add-mcp to connect Paste to all your installed AI apps:
npx add-mcp @pasteapp/mcpThe first time an app uses Paste, it'll ask you to authenticate and allow access.
Alternatively, connect Paste to each app manually:
Claude Code
claude mcp add paste -- npx -y @pasteapp/mcpCodex
codex mcp add paste -- npx -y @pasteapp/mcpCursor
VS Code
Connect from Paste
You can also connect any app right inside Paste. Open Settings → MCP & AI Tools, click Connect AI Tool, and choose your app — Paste does the rest.

Related MCP server: Colab MCP
Privacy Policy
Paste MCP runs locally on your Mac — it bridges your AI app to Paste's on-device server and sends nothing to Paste's own servers. Your clipboard items only reach the AI apps you approve, and you can revoke access anytime in Settings → MCP & AI Tools.
Full policy — what data is processed, how it's stored, sharing, retention, and contact: https://pasteapp.io/privacy.
Troubleshooting
The AI tool says Paste isn't available. Make sure Paste is running and MCP is enabled in Settings → MCP & AI Tools.
Tools don't show up after connecting. Fully quit and reopen your AI app so it relaunches the server.
npx errors or "command not found".
Confirm Node.js 18+ is installed: node --version.
Requirements
Contributing
Issues and pull requests welcome — see the issue tracker.
License
Available Tools
1 toolpaste_statusA
Returns Paste's connection status. Call this if Paste-related tools are missing — the response explains how to bring Paste online.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description still discloses the output (connection status and instructions to bring Paste online). It is transparent about its read-only nature and does not hide any side effects.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences, immediately front-loading the purpose. Every word adds value, with no extraneous information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a zero-parameter status tool, the description fully explains what it returns and why it exists. No output schema is needed given the simplicity.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
There are zero parameters and schema coverage is 100%. The description adds no parameter info, but none is needed. Baseline score of 4 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool returns Paste's connection status and provides specific guidance for when it should be called. The verb 'returns' and resource 'connection status' are explicit.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly states when to use this tool: 'Call this if Paste-related tools are missing'. Although no alternatives are listed, the condition is clear given no siblings.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
1 tool update
v0.1.1- First observed
paste_status
TDQS
With only one tool, there is no possibility of confusion between tools. The tool has a clear and distinct purpose.
Having a single tool makes naming trivially consistent. The name 'paste_status' follows a clear noun_noun pattern that aligns with the server's purpose.
One tool is at the low end of reasonable scope. The server's purpose seems to require more tools, but the single tool serves as a diagnostic entry point.
The tool set is severely incomplete for any real task beyond checking status. Agents cannot perform any Paste-related operations without additional tools that appear only after Paste is online.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
Connect your team's living knowledge base — docs, data, issues, CRM — to Claude and ChatGPT.
One workspace of tools for Claude and ChatGPT: connect 600+ apps, generate media, build tools.
Deploy HTML and Markdown as live URLs. Create, search, update, and manage pastes from any AI agent.
- alloyOAuthai.usealloy
Connect Claude, Cursor, Codex, and other AI tools to your robotics mission data.
Related MCP Servers
- AlicenseNot gradedqualityAmaintenanceGives AI assistants direct access to macOS clipboard - letting Claude copy generated code, text, or files straight to your clipboard for pasting anywhere on Mac.245MIT
- -licenseNot gradedqualityNot gradedmaintenanceEnables AI coding assistants like Claude Code, Cursor, and Codex to share chat logs, terminal history, and session context with each other. Eliminates the need to re-explain context when switching between different AI coding tools.2-
- AlicenseNot gradedqualityDmaintenanceBring your Plaud Note recordings into Claude Desktop. Search meetings, pull transcripts, and ask Claude about your notes — directly from chat.1MIT
- AlicenseNot gradedqualityDmaintenanceConnect your Supabase projects to Cursor, Claude, Windsurf, and other AI assistants.Apache 2.0
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/pasteapp/paste-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server