Listen Install
Install and maintain Parrot Scribe MCP on local agent hosts
Shared setup
Do this once in Parrot Scribe before you touch any host config.
- Open Settings > MCP.
- Enable the MCP server.
- Create one token per client. Copy it when shown; it is only shown once.
- Give that client recording control so it can start and stop sessions (
start_recording/stop_recording).
Every local host uses the bundled stdio shim:
/Applications/Parrot Scribe.app/Contents/MacOS/parrotscribe-mcp-shim --token <token>
Restart the host after you save its config.
The /plugin marketplace add johanthoren/parrotscribe-plugins one-liner is only for hosts that have slash commands. Other hosts get the shim and MCP tools, not /listen.
Claude Desktop
Add the marketplace so Desktop can run /listen and /recap:
/plugin marketplace add johanthoren/parrotscribe-plugins
Connect MCP in ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"parrotscribe": {
"command": "/Applications/Parrot Scribe.app/Contents/MacOS/parrotscribe-mcp-shim",
"args": ["--token", "<token-from-settings>"]
}
}
}
Claude Code and Cowork
Same marketplace one-liner as Desktop. These hosts have slash commands, so /listen and /recap are available after the catalog is added.
/plugin marketplace add johanthoren/parrotscribe-plugins
Connect MCP from the CLI:
claude mcp add --transport stdio parrotscribe -- "/Applications/Parrot Scribe.app/Contents/MacOS/parrotscribe-mcp-shim" --token <token-from-settings>
Or put this stdio block in ~/.claude.json or .mcp.json:
{
"mcpServers": {
"parrotscribe": {
"command": "/Applications/Parrot Scribe.app/Contents/MacOS/parrotscribe-mcp-shim",
"args": ["--token", "<token-from-settings>"]
}
}
}
ChatGPT desktop and Codex
ChatGPT desktop and Codex share ~/.codex/config.toml and support local STDIO. Add:
[mcp_servers.parrotscribe]
command = "/Applications/Parrot Scribe.app/Contents/MacOS/parrotscribe-mcp-shim"
args = ["--token", "<token-from-settings>"]
ChatGPT web is not a local stdio host. Codex and ChatGPT desktop get MCP tools, not /listen.
Grok Build
If Grok Build consumes the Claude plugin catalog, add it with the same marketplace one-liner:
/plugin marketplace add johanthoren/parrotscribe-plugins
Otherwise connect it as a stdio MCP host:
{
"mcpServers": {
"parrotscribe": {
"command": "/Applications/Parrot Scribe.app/Contents/MacOS/parrotscribe-mcp-shim",
"args": ["--token", "<token-from-settings>"]
}
}
}
Stdio-only Grok Build gets MCP tools, not /listen.
Gemini CLI
Add this mcpServers entry in ~/.gemini/settings.json:
{
"mcpServers": {
"parrotscribe": {
"command": "/Applications/Parrot Scribe.app/Contents/MacOS/parrotscribe-mcp-shim",
"args": ["--token", "<token-from-settings>"]
}
}
}
Gemini CLI gets MCP tools, not /listen.
Antigravity
Use ~/.gemini/config/mcp_config.json or .agents/mcp_config.json:
{
"mcpServers": {
"parrotscribe": {
"command": "/Applications/Parrot Scribe.app/Contents/MacOS/parrotscribe-mcp-shim",
"args": ["--token", "<token-from-settings>"]
}
}
}
Antigravity gets MCP tools, not /listen.
Cursor
Add the shim in .cursor/mcp.json:
{
"mcpServers": {
"parrotscribe": {
"command": "/Applications/Parrot Scribe.app/Contents/MacOS/parrotscribe-mcp-shim",
"args": ["--token", "<token-from-settings>"]
}
}
}
Cursor gets MCP tools, not /listen.
OpenCode
OpenCode does not use mcpServers. Add the server by name under mcp in ~/.config/opencode/opencode.json or the project opencode.json:
{
"mcp": {
"parrotscribe": {
"type": "local",
"command": [
"/Applications/Parrot Scribe.app/Contents/MacOS/parrotscribe-mcp-shim",
"--token",
"<token-from-settings>"
]
}
}
}
OpenCode gets MCP tools, not /listen.
Other stdio hosts
Any other local stdio MCP host uses the same shim command and token. Those hosts get MCP tools, not /listen.
Maintenance
- Rotate the token in Settings > MCP, then put the new value in the host config and restart the host.
- Update the marketplace on slash-command hosts when you want the latest
/listenand/recap. - Restart the host after any config, token, or marketplace change.
- Review capability toggles so the client still has the tools it needs, including recording control.
Tool tables and the access model stay on MCP Server. How /listen and /recap work is on Listen and Recap.