How to Use the eCellar MCP in VS Code Copilot

Q: How does the shared eCellar config work for my team in VS Code Copilot?

You commit a .vscode/mcp.json file to your Git repo. When a team member opens that project in VS Code, Copilot automatically loads the eCellar tools for them, ensuring everyone has the same setup.

Give your whole engineering team secure, shared access to eCellar data inside VS Code Copilot.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect eCellar MCP to VS Code Copilot

Create your Vinkius account to connect eCellar to VS Code Copilot and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup eCellar with VS Code Copilot

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Standardize eCellar access for your entire team.

Add the eCellar server config to a `.vscode/mcp.json` file and commit it to your repository. Now, every developer who pulls the repo gets the same set of tools. No more "it works on my machine" issues. This means a senior engineer can debug a customer issue by asking Copilot to `get_customer` and a junior dev can learn the data model by asking to `list_products`. It creates a consistent, secure way for the whole team to interact with your winery's live system.

Build and debug production systems faster.

When you're building a new feature for your winery's website, you need real data. Ask Copilot's agent to "pull the last 5 orders for this customer" and it will use `list_orders` to inject that data right into your debugging session. This is about closing the gap between development and production. You can validate your code against live data structures from `get_product` or `get_order` before you even commit. It's a more reliable way to build software for your eCellar platform.

Query winery operations with VS Code Copilot.

Your product manager needs to know how many members are in a specific wine club. Instead of a support ticket, they can just ask Copilot in VS Code. The agent uses `list_clubs` and `list_club_members` to give them a direct answer. This turns Copilot into a powerful internal tool. Your team can check on daily tasting room traffic with `list_reservations` or get a quick inventory count with `list_inventory`, all without context switching or needing separate credentials for the eCellar backend. This is a solid MCP integration for any team managing a winery.

Setup guide

Set up eCellar MCP in VS Code Copilot

Prerequisites

VS Code 1.99 or later with GitHub Copilot extension
Active Vinkius subscription with a valid endpoint token

1

Open MCP configuration

Open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and run "MCP: Add Server". Select HTTP (Streamable) as the server type. VS Code will create .vscode/mcp.json in your workspace.
2

Add the eCellar MCP

Paste the JSON snippet shown on the right into your .vscode/mcp.json. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Switch to Agent mode

Open Copilot Chat (Cmd+Shift+I / Ctrl+Shift+I) and switch to Agent mode using the dropdown. MCP tools are only available in Agent mode — they do not appear in Edit or Ask modes.
4

Verify the connection

In the Copilot Chat input, type # to list available tools. You should see the eCellar tools listed. Try asking: "List my recent eCellar transactions" and Copilot will invoke them automatically.

.vscode/mcp.json

{
  "mcpServers": {
    "ecellar-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by eCellar. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect eCellar now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about eCellar MCP in VS Code Copilot

You commit a `.vscode/mcp.json` file to your Git repo. When a team member opens that project in VS Code, Copilot automatically loads the eCellar tools for them, ensuring everyone has the same setup.

Yes. You'd ask the agent to 'find the total spend for customer ID 123'. It would use the `search_customers` and `list_orders` tools to gather the data and calculate the lifetime value.

Switch Copilot Chat to agent mode and ask, 'Show me all orders from the last 24 hours'. The agent will then use the `list_orders` tool to fetch and display that information.

Yes, it's fully compatible. Your administrator can manage access, and the configuration can be rolled out organization-wide, giving your entire enterprise secure access to eCellar tools.

Access is managed through Vinkius's zero-trust platform. Each query to the eCellar MCP server runs in an ephemeral sandbox, handling sensitive customer, order, and club membership data securely. All tool access is logged, and the connection is scoped to prevent broad data exposure.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript