Percept MCP Server

Percept MCP server exists for a simple reason — assistants are far more useful when they can act on Percept directly instead of describing what you should do. Ambient voice intelligence for AI agents. Wearable mics to agent actions via MCP.

What you get

Percept connects your real-world data to your AI agent through hardware capture, tool connectors, and a knowledge graph that enables your agent to take initiative.

• 🎧 Hear — — Omi pendant captures ambient audio. Chrome extension captures browser audio. Meetings, conversations, podcasts — all transcribed and searchable
• ⌚ Interact — — Apple Watch app with push-to-talk, raise-to-speak, and complications
• 🔗 Connect — — Gmail, GitHub, Linear, Calendar, Slack connectors sync your work context
• 🧠 Understand — — Knowledge graph connects people, projects, conversations, and events across all sources
• ⚡ Act — — Initiative engine detects patterns and triggers actions without being asked

Setting it up

Installation goes through your MCP client rather than a global install: point it at getpercept on PyPI and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the percept mcp server does with a few real requests.

Choosing this one

Among the team communication options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. It is maintained by davidemanuelDEV; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.