Bring Lead Management
to VS Code Copilot
Learn how to connect TaskForce to VS Code Copilot and start using 9 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the TaskForce MCP Server?
Connect your AI agent to TaskForce to natively manage your CRM workflow, customer interactions, and invoicing through natural language commands.
What you can do
- Lead & Customer Management — Query lists of active leads, fetch detailed customer profiles, and instantly create new lead records on the fly.
- Case Tracking — Read and track support or business cases, and generate new cases directly from your chat interface.
- Financial Overview — Pull real-time lists of pending invoices and active quotes to monitor business performance without opening a dashboard.
How it works
1. Retrieve your API Key from the TaskForce Admin dashboard.
2. Provide the key to this integration.
3. Instruct your agent to pull your recent leads or check the status of an invoice.
Who is this for?
- Sales & Support Teams — Update leads and track customer cases seamlessly.
- Accountants — Monitor invoices and quotes dynamically.
- Developers — Connect your TaskForce database with external custom tools.
Built-in capabilities (9)
Create a new case
Create a new lead
Get customer details
Get lead details
List all cases
List all customers
List all invoices
List all leads
List all quotes
Why VS Code Copilot?
GitHub Copilot Agent mode brings TaskForce data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 9 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.
- —
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
TaskForce in VS Code Copilot
TaskForce and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect TaskForce to VS Code Copilot through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for TaskForce in VS Code Copilot
The TaskForce 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. All 9 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in VS Code Copilot only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* 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
How Vinkius secures
TaskForce for VS Code Copilot
Every tool call from VS Code Copilot to the TaskForce MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I add a new lead directly from the chat?
Yes. By invoking the 'create_taskforce_lead' tool and providing the lead's information in JSON format, the AI will register it instantly.
How do I check my pending invoices?
You can use the 'list_taskforce_invoices' tool. The agent will fetch all your invoices and present their statuses.
Is it possible to view the details of a specific customer case?
Yes, using the 'list_taskforce_cases' tool you can query all active support or business cases assigned in your CRM.
Which VS Code version supports MCP?
MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.
How do I switch to Agent mode?
Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.
Can I restrict which MCP tools Copilot can access?
Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.
Does MCP work in VS Code Remote or Codespaces?
Yes. MCP servers configured via .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.
MCP tools not available
Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.