Bring Product Management
to VS Code Copilot
Learn how to connect Craft.io to VS Code Copilot and start using 13 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the 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.
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.
How it works
1. Subscribe to this server
2. Enter your Craft.io API Key and Account ID (found in your account settings)
3. Start managing your product ecosystem from your favorite AI assistant
Who is this for?
- Product Managers & Owners — quickly retrieve feature details and update backlog items via simple AI commands.
- Engineering Leads — monitor epic progress and verify feature requirements directly from the workspace.
- Product Operations — manage workspace distributions and verify portfolio metadata via the AI assistant.
Built-in capabilities (13)
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
Why VS Code Copilot?
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.
- —
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 in VS Code Copilot
Craft.io and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Craft.io 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 Craft.io in VS Code Copilot
The Craft.io 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 13 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
Craft.io for VS Code Copilot
Every tool call from VS Code Copilot to the Craft.io MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I see all the items in a specific workspace via AI?
Yes! Use the list_workspace_items tool and provide the Workspace ID. Your agent will retrieve all features, stories, and epics organized within that environment.
How do I add a new feature to my backlog using the agent?
Use the create_product_item action. Provide the Workspace ID and the title of the feature. The agent will instantly create the record in your Craft.io account.
Is it possible to list all my product portfolios via AI?
Absolutely. Use the list_product_portfolios query. The agent will retrieve the complete list of portfolios configured in your account, allowing you to monitor high-level strategy.
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.