VS Code’s MCP support is built into GitHub Copilot agent mode. Two things to note up front:Documentation Index
Fetch the complete documentation index at: https://docs.kataven.ai/llms.txt
Use this file to discover all available pages before exploring further.
- VS Code uses
mcp.jsonas the filename (notclaude_desktop_config.jsonor similar). - The top-level key is
servers(notmcpServers!) — pasting the universal entry verbatim won’t work here. - MCP tools work in Agent mode only. Ask and Edit modes ignore them.
Already done Install? Skip to step 2.
1. Mint an API key + install the binary
pip install kataven-mcp, then mint a key at hub.kataven.ai/settings → API Keys tab. Full walkthrough: Install.
2. Open the VS Code MCP config
Cmd+Shift+P (Ctrl+Shift+P on Windows/Linux) →MCP: Open User Configuration.
This opens (or creates) mcp.json in your VS Code user-config directory.
3. Paste the VS Code-specific shape
servers, not mcpServers. Save.
4. Switch Copilot to Agent mode
Open Copilot Chat (Cmd+Shift+I or the chat icon in the sidebar). At the top of the chat panel, switch the mode picker to Agent. Thekataven_* tools are now callable.
List all my Kataven agents.
VS Code’s MCP is stdio-only. Servers requiring SSE or Streamable HTTP transport won’t work here today (
kataven-mcp is stdio, so no issue). MCP tools also don’t surface in Ask or Edit modes — only Agent mode invokes them.5. Verify in the dashboard
| What changed | Open in Hub UI |
|---|---|
| Agents | hub.kataven.ai/agents |
| Phone numbers | hub.kataven.ai/phone-numbers |
| Live or recent calls | hub.kataven.ai/conversations |
| Campaigns | hub.kataven.ai/campaigns |
See also
- VS Code MCP docs — official.
- JetBrains setup — same protocol from a different IDE.
- Troubleshooting.

