JompterWhat each agent gets.
Everything below the first column works in any app on your Mac. The rest depends on whether Jompter writes a connection for it.
| Agent | Voice, screenshots, paste | MCP connection | Agent skills |
|---|---|---|---|
| Claude Code | a command you run in a terminal | ~/.claude/skills/ | |
| Cursor | ~/.cursor/mcp.json | ~/.cursor/skills/ | |
| Codex | ~/.codex/config.toml | ~/.agents/skills/ | |
| OpenCode | ~/.config/opencode/opencode.json | ||
| GitHub Copilot | |||
| VS Code | |||
| Windsurf | |||
| Gemini CLI |
How it reaches each one.
Jompter with Claude Code
Hold the hotkey and your words are typed straight into the terminal Claude Code runs in; screenshots and recordings drag in as files.
It asks before each tool it has not seen, and Jompter’s server has 37. One rule — "allow": ["mcp__jompter"] in ~/.claude/settings.json — covers the whole server.
- MCP snippet goes in
- a command you run in a terminal
- Skills install to
- ~/.claude/skills/
Jompter with Cursor
Dictation types into Cursor’s chat or the editor, whichever has focus. Drag an annotated screenshot into the chat and it reads it.
Jompter writes the snippet with your port and key already in it — both differ on every Mac.
- MCP snippet goes in
- ~/.cursor/mcp.json
- Skills install to
- ~/.cursor/skills/
Jompter with Codex
Talk into the Codex CLI the way you would type into it; the transcript lands where the cursor is.
The Codex CLI takes its MCP servers in TOML, so the panel generates that rather than JSON.
- MCP snippet goes in
- ~/.codex/config.toml
- Skills install to
- ~/.agents/skills/
Jompter with OpenCode
Dictate into the OpenCode session, and drop screenshots or a combined frame sheet in as files.
Jompter writes an OpenCode snippet, so boards and prompts are available to it like any other client.
- MCP snippet goes in
- ~/.config/opencode/opencode.json
Jompter with GitHub Copilot
Dictation types into the Copilot chat box, and a Jompter prompt pastes in as Markdown with its screenshots attached as files.
Jompter does not write an MCP snippet for Copilot today — the paste-and-drag path is how you use it.
Connect GitHub Copilot →
Jompter with VS Code
Anywhere you can type in VS Code — a chat panel, a commit message, a comment — you can talk instead.
The same goes for any editor extension: Jompter types into whatever is focused, so it does not need to know about the extension.
Connect VS Code →
Jompter with Windsurf
Speak your change into Cascade, and drag the annotated shot in beside it.
No MCP snippet from Jompter’s panel yet; the prompt still arrives as one Markdown block.
Connect Windsurf →
Jompter with Gemini CLI
Dictate into the Gemini CLI in your terminal, then paste the prompt with its transcript and frame timestamps.
No MCP snippet from Jompter’s panel yet — dictation and paste work the same as in any terminal.
Connect Gemini CLI →Connecting Jompter to an agent.
What works everywhere, and what needs a connection.
No. Dictation types into whatever app has focus, screenshots and recordings leave as real files, and a prompt copies as Markdown — so any agent that takes typing, files or a paste already works.
The panel writes a ready-made snippet for Claude Code, Cursor, Codex CLI, OpenCode and Claude Desktop. Over MCP an agent can read your prompts, work through the to-dos and draw on a Jompter board.
localhost can resolve to IPv6 and the server only listens on IPv4. The symptom is a connection that never establishes, so the snippets always use 127.0.0.1.
No. Letting agents draw on boards is one switch, and letting them work on your prompts is a second one that is off by default. While it is off, agents are not even told the prompt tools exist.