Screen capture, voice dictation, clipboard, keyboard/mouse activity. All local, all private.
Most knowledge and memory work still happens through a UI a human drives. Contextpulse MCP server moves it into the conversation instead. Screen capture, voice dictation, clipboard, keyboard/mouse activity. All local, all private.
The server publishes 14 tools. What each one is for:
get_screenshot — Capture screen (active monitor, all monitors, or a region)get_recent — Recent frames from the rolling buffer (with diff filtering)get_screen_text — OCR the current screen at native resolutionget_monitor_summary — Lightweight text summary of all monitors (low token cost)get_buffer_status — Daemon health check + buffer statsget_activity_summary — App usage breakdown over last N hourssearch_history — Full-text search across window titles + OCR textget_context_at — Frame + metadata from N minutes agoget_clipboard_history — Recent clipboard entriessearch_clipboard — Search clipboard by text contentget_agent_stats — Which MCP clients are consuming context, and how oftenget_recent_transcriptions — Recent voice dictation history (raw + cleaned)contextpulse-memory on PyPI is all you need. Most clients run it directly, so configuration is a few lines and a restart.
Plenty of knowledge and memory servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Contextpulse's toolset — get_screenshot, get_recent, get_screen_text and 11 more — is a fair guide to whether it matches your workflow. It is maintained by contextpulse; 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.
| Tool | What it does |
|---|---|
| get_screenshot | Capture screen (active monitor, all monitors, or a region) |
| get_recent | Recent frames from the rolling buffer (with diff filtering) |
| get_screen_text | OCR the current screen at native resolution |
| get_monitor_summary | Lightweight text summary of all monitors (low token cost) |
| get_buffer_status | Daemon health check + buffer stats |
| get_activity_summary | App usage breakdown over last N hours |
| search_history | Full-text search across window titles + OCR text |
| get_context_at | Frame + metadata from N minutes ago |
| get_clipboard_history | Recent clipboard entries |
| search_clipboard | Search clipboard by text content |
| get_agent_stats | Which MCP clients are consuming context, and how often |
| get_recent_transcriptions | Recent voice dictation history (raw + cleaned) |
| get_voice_stats | Dictation count, duration, accuracy stats |
| get_vocabulary | Current word correction entries |
{
"mcpServers": {
"contextpulse": {
"type": "http",
"url": "http://127.0.0.1:8420/mcp"
}
}
}Configuration as documented by the project. Restart the client after saving.
A knowledge graph your assistant keeps between sessions — entities, relations and observations that persist.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
A structured scratchpad for hard problems — stepwise reasoning with revisions, branches and visible logic.
Symbol-level code navigation, refactoring and memory for coding agents — the IDE brain your assistant has been missing.
Chat with your second brain — search, read and write vault notes through the Local REST API.