Continue (the open-source VS Code / JetBrains assistant) speaks MCP natively (via the YAML config).
pip install --user claude-code-talkerEdit ~/.continue/config.yaml (or your assistant's specific config file):
mcpServers:
- name: codetalker
command: codetalker-mcp
args: []
env: {}If you maintain an assistant via Continue Hub, add codetalker as a tool block on the hub. The codetalker assistant page is at https://hub.continue.dev/assistants/codetalker (TBD — submission planned in SP-7 of the launch master plan).
VS Code → Command Palette → "Continue: Reload" — or restart your IDE.
In your config.yaml, you can add a system message guiding Continue's use of codetalker:
systemMessage: |
You have access to codetalker tools (mcp tools from the codetalker MCP server).
Use tts_set_mode to switch between direct/brief/live based on workload.
Don't call tts_speak directly — narration happens via hooks.In a Continue chat:
List the MCP tools available to you.
You should see codetalker.tts_speak, codetalker.tts_set_mode, and the rest.
- Continue's "Quick Edit" command (cmd-I) doesn't typically need narration — it's fast. Save codetalker for "Chat" interactions and the autonomous "Agent" mode.
- Continue supports MCP
resourcesandpromptsin addition totools. CodeTalker currently exposes tools only; resources/prompts may come in v1.x.