How to Use the ChannelApe MCP in VS Code Copilot

Q: What's the difference between user and workspace config for the ChannelApe MCP?

Workspace config (.vscode/mcp.json) is shared with the whole team via your git repository, which is the recommended approach. User config is specific to your machine and won't be shared with other developers using VS Code Copilot.

Give your team access to ChannelApe data in VS Code with a shared Copilot configuration.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect ChannelApe MCP to VS Code Copilot

Create your Vinkius account to connect ChannelApe 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 ChannelApe with VS Code Copilot

Ask AI about this MCP

ChatGPT

Claude

Perplexity

A Shared MCP Server for Your Team

Add this ChannelApe server to your project's `.vscode/mcp.json` file and commit it to your repository. Every developer on the team instantly gets the same set of tools in their Copilot Chat. No more asking teammates for API keys or setting up individual environments. This keeps your entire engineering team in sync and working with the same, approved data sources. It’s built for team collaboration, not just solo developers.

Look Up Orders and Products in VS Code

When you're debugging a customer issue, ask Copilot to `get_ape_order_details` using the order ID. It pulls the data right into the chat panel in VS Code, so you don't have to switch contexts. You can see what was ordered, by whom, and its status. It works for products, too. Use `get_ape_product_details` to check SKUs, pricing, or other specs without leaving the editor. You get answers fast, right where you're writing code.

Run Pre-Deployment Sanity Checks

Before you push a new feature, run a few quick checks from your editor. Ask Copilot to `list_ape_suppliers` to confirm your vendor integrations are correct. You can also use `list_ape_channels` to make sure all expected sales channels are active. These tools give you a direct line to your live ChannelApe configuration. It's a simple way to catch potential issues before they go into production. This MCP connection makes it possible.

Setup guide

Set up ChannelApe 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 ChannelApe 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 ChannelApe tools listed. Try asking: "List my recent ChannelApe transactions" and Copilot will invoke them automatically.

.vscode/mcp.json

{
  "mcpServers": {
    "channelape-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 ChannelApe. 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 ChannelApe 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 ChannelApe MCP in VS Code Copilot

An admin or lead developer adds the ChannelApe MCP Server to the project's `.vscode/mcp.json` file. Once that file is in your git repo, everyone on the team automatically gets the ChannelApe tools in their Copilot Chat.

Workspace config (`.vscode/mcp.json`) is shared with the whole team via your git repository, which is the recommended approach. User config is specific to your machine and won't be shared with other developers using VS Code Copilot.

No, this MCP Server is designed for interactive use within an IDE like VS Code. For automated CI/CD workflows, you should use a dedicated SDK or CLI client that can run headlessly.

Yes. The connection is made from VS Code to the Vinkius platform over a standard HTTPS port (443). As long as you have general internet access, it should work without requiring special firewall rules.

Yes. The tool execution happens on Vinkius's secure platform, which is isolated from the AI model itself. Your authentication is handled by Vinkius, and no raw credentials for ChannelApe are exposed to VS Code Copilot. The system is designed to handle sensitive order and product data securely.

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