Craft.io MCP Server for VS Code CopilotGive VS Code Copilot instant access to 13 tools to Check Craft Status, Create Item, Get Company, 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 Craft.io app connector for VS Code Copilot is a standout in the Productivity category — giving your AI agent 13 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 Craft.io and 3,400+ MCP Servers from a single visual interface.




{
"mcpServers": {
"craftio": {
"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 Craft.io MCP Server
Connect your Craft.io product management account to any AI agent and simplify how you coordinate your product strategy, manage features, and monitor roadmaps through natural conversation.
GitHub Copilot Agent mode brings Craft.io data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 13 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.
What you can do
- Workspace Oversight — List all product management workspaces and retrieve detailed metadata and configurations.
- Feature & Epic Tracking — List, query, and create new items (features, stories, epics) within your workspaces to manage your backlog.
- Portfolio Control — List and query product portfolios to understand high-level organizational distribution and strategy.
- Data Insights — Fetch complete metadata, descriptions, and current status for any specific product item via AI.
- Roadmap Monitoring — Track the progress of features and epics directly from your agent to stay on top of your release cycle.
- Operational Visibility — Check account status and verify project metadata directly from Claude, Cursor, or any MCP client.
The Craft.io MCP Server exposes 13 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 13 Craft.io tools available for VS Code Copilot
When VS Code Copilot connects to Craft.io through Vinkius, your AI agent gets direct access to every tool listed below — spanning product-management, roadmap-software, feature-tracking, 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.
Verify connectivity
Create an item
Get company details
Get competitors
Get company employees
Get company financials
Get company news
Get item details
Get portfolio details
List workspace items
List portfolios
List workspaces
Search companies
Connect Craft.io to VS Code Copilot via MCP
Follow these steps to wire Craft.io 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 Craft.io
Why Use VS Code Copilot with the Craft.io MCP Server
GitHub Copilot for Visual Studio Code provides unique advantages when paired with Craft.io 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
Craft.io + VS Code Copilot Use Cases
Practical scenarios where VS Code Copilot combined with the Craft.io 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 Craft.io in VS Code Copilot
Ready-to-use prompts you can give your VS Code Copilot agent to start working with Craft.io immediately.
"List all active workspaces in my Craft.io account."
"Show me the last 5 items in the 'Mobile App Roadmap' (ID: 10293)."
"Create a new feature: 'AI Search Integration' in workspace 'ws_88231'."
Troubleshooting Craft.io MCP Server with VS Code Copilot
Common issues when connecting Craft.io to VS Code Copilot through the Vinkius, and how to resolve them.
MCP tools not available
Craft.io + VS Code Copilot FAQ
Common questions about integrating Craft.io 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.