2,500+ MCP servers ready to use
Vinkius

GRIN MCP Server for VS Code Copilot 12 tools — connect in under 2 minutes

Built by Vinkius GDPR 12 Tools IDE

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.

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install GRIN and 2,500+ MCP Servers from a single visual interface.

Vinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop Interface
Download Free Open SourceNo signup required
Classic Setup·json
{
  "mcpServers": {
    "grin": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}
GRIN
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* 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 GRIN MCP Server

Connect your GRIN Creator Management account to any AI agent and take full control of your influencer marketing workflows through natural conversation.

GitHub Copilot Agent mode brings GRIN data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 12 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

What you can do

  • CRM Orchestration — List and retrieve detailed creator profiles, social handles, and custom properties natively
  • Campaign Management — Monitor active influencer campaigns and track specific creator activations flawlessly
  • Content Oversight — Access and review the library of posts, stories, and media generated by your creators synchronously
  • Performance Tracking — Retrieve conversion data and ROI metrics attributed to specific influencers flawlessly
  • Logistics & Seeding — Manage product seeding orders and fulfillment statuses sent to creators natively
  • Partnership Navigation — List and verify formal brand-creator relationships and manage payouts synchronously

The GRIN MCP Server exposes 12 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.

How to Connect GRIN to VS Code Copilot via MCP

Follow these steps to integrate the GRIN MCP Server with VS Code Copilot.

01

Create MCP config

Create a .vscode/mcp.json file in your project root

02

Add the server config

Paste the JSON configuration above

03

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown

04

Start using GRIN

Ask Copilot: "Using GRIN, help me...". 12 tools available

Why Use VS Code Copilot with the GRIN MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with GRIN through the Model Context Protocol.

01

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

02

Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

03

Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

04

GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

GRIN + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the GRIN MCP Server delivers measurable value.

01

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

02

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

03

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

04

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

GRIN MCP Tools for VS Code Copilot (12)

These 12 tools become available when you connect GRIN to VS Code Copilot via MCP:

01

get_campaign

Get details for a specific campaign

02

get_contact

Get details for a specific creator

03

get_me

Get details for the current GRIN account

04

list_activations

Track creator participations within a campaign

05

list_campaigns

List active and past influencer campaigns

06

list_contacts

List all creators/influencers in the CRM

07

list_content

Access the library of posts and stories generated by creators

08

list_conversions

Track sales and ROI attributed to influencers

09

list_orders

Manage product seeding and fulfillment orders

10

list_partnerships

Manage formal brand-creator relationships

11

list_payments

List and manage creator payouts

12

update_contact

Update properties for a specific creator

Example Prompts for GRIN in VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot agent to start working with GRIN immediately.

01

"List my influencer campaigns in GRIN"

02

"Show the conversion data for @janesmith"

03

"Check the status of seeding order #GF-88392"

Troubleshooting GRIN MCP Server with VS Code Copilot

Common issues when connecting GRIN to VS Code Copilot through the Vinkius, and how to resolve them.

01

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

GRIN + VS Code Copilot FAQ

Common questions about integrating GRIN MCP Server with VS Code Copilot.

01

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.
02

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.
03

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.
04

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.

Connect GRIN to VS Code Copilot

Get your token, paste the configuration, and start using 12 tools in under 2 minutes. No API key management needed.