Thoughtly MCP Server for VS Code CopilotGive VS Code Copilot instant access to 11 tools to Create Contact, Delete Contact, Get Call History, and more
GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.
Ask AI about this App Connector for VS Code Copilot
The Thoughtly app connector for VS Code Copilot is a standout in the Communication category — giving your AI agent 11 tools to work with, ready to go from day one.
Vinkius delivers Streamable HTTP and SSE to any MCP client
Vinkius Desktop App
The modern way to manage MCP Servers — no config files, no terminal commands. Install Thoughtly and 3,400+ MCP Servers from a single visual interface.




{
"mcpServers": {
"thoughtly": {
"url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
}
}
}
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
About Thoughtly MCP Server
Connect your Thoughtly voice AI platform to any text-based AI agent to seamlessly bridge the gap between text commands and real-world phone calls.
GitHub Copilot Agent mode brings Thoughtly data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 11 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.
What you can do
- Trigger Phone Calls — Instantly instruct your AI Voice Agents (Interviews) to dial any contact and execute conversational phone workflows
- Contact Management — Query your Thoughtly CRM directory, register new leads with phone numbers, and manage their details
- Call Logs & Transcripts — Retrieve detailed call histories, metadata, and full transcripts of conversations conducted by your voice agents
- Agent Fleet Control — List and inspect all your active AI Voice Agents to deploy the right persona for each outbound campaign
The Thoughtly MCP Server exposes 11 tools through the Vinkius. Connect it to VS Code Copilot in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.
All 11 Thoughtly tools available for VS Code Copilot
When VS Code Copilot connects to Thoughtly through Vinkius, your AI agent gets direct access to every tool listed below — spanning voice-ai, agents, crm, and more. Every call is secured with network, filesystem, subprocess, and code evaluation entitlements inside a sandboxed runtime. Beyond a simple connection, you get a full AI Gateway with real-time visibility into agent activity, enterprise governance, and optimized token usage.
Optionally includes first name, last name, email. Create a new Thoughtly contact
Delete a Thoughtly contact
Get details and transcript for a specific call
Get specific Thoughtly contact details
Get details for a specific Thoughtly Voice Agent
Get Thoughtly user details
List past phone calls (Call logs)
List Thoughtly contacts
List Thoughtly Voice Agents (Interviews)
Trigger an AI outbound phone call
Update an existing Thoughtly contact
Connect Thoughtly to VS Code Copilot via MCP
Follow these steps to wire Thoughtly into VS Code Copilot. The entire setup takes under two minutes — your credentials stay safe behind the Vinkius.
Create MCP config
.vscode/mcp.json file in your project rootAdd the server config
Enable Agent mode
Start using Thoughtly
Why Use VS Code Copilot with the Thoughtly MCP Server
GitHub Copilot for Visual Studio Code provides unique advantages when paired with Thoughtly through the Model Context Protocol.
VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor
Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access
Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop
GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services
Thoughtly + VS Code Copilot Use Cases
Practical scenarios where VS Code Copilot combined with the Thoughtly MCP Server delivers measurable value.
Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step
DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review
Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses
Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples
Example Prompts for Thoughtly in VS Code Copilot
Ready-to-use prompts you can give your VS Code Copilot agent to start working with Thoughtly immediately.
"List all my available Voice Agents in Thoughtly."
"Create a new contact with the phone number +1234567890 and tell the Sales SDR Voice Agent to call them."
"Get the call transcript for the latest interaction with Call ID CAL-554."
Troubleshooting Thoughtly MCP Server with VS Code Copilot
Common issues when connecting Thoughtly to VS Code Copilot through the Vinkius, and how to resolve them.
MCP tools not available
Thoughtly + VS Code Copilot FAQ
Common questions about integrating Thoughtly MCP Server with VS Code Copilot.
Which VS Code version supports MCP?
How do I switch to Agent mode?
Can I restrict which MCP tools Copilot can access?
Does MCP work in VS Code Remote or Codespaces?
.vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.