2,500+ MCP servers ready to use
Vinkius

Griffin 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 Griffin 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": {
    "griffin": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}
Griffin
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 Griffin MCP Server

Connect your Griffin Banking-as-a-Service account to any AI agent and take full control of your embedded finance operations through natural conversation.

GitHub Copilot Agent mode brings Griffin 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

  • Index Orchestration — Discover all available API resources and navigate your organization's banking infrastructure natively
  • Account Oversight — List and inspect all bank accounts, including available balances and account numbers flawlessy
  • Live Transaction Monitoring — Retrieve detailed transaction histories and resolve specific payment details including status and amounts flawlessly
  • Verification Workflow — Manage KYC and KYB verifications by listing and inspecting individual verification records natively
  • Financial Transfers — Trigger internal transfers between accounts to manage liquidity across your organization synchronously
  • Payee Management — List and verify saved payees to ensure secure and accurate payment orchestration natively

The Griffin 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 Griffin to VS Code Copilot via MCP

Follow these steps to integrate the Griffin 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 Griffin

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

Why Use VS Code Copilot with the Griffin MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with Griffin 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

Griffin + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the Griffin 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

Griffin MCP Tools for VS Code Copilot (12)

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

01

create_internal_transfer

Transfer money between internal accounts

02

get_account

Get details for a specific bank account

03

get_index

Get the root index of resources from the Griffin API

04

get_me

Get details of the current authenticated user

05

get_organization

Get details for a specific organization

06

get_transaction

Get details for a specific transaction

07

get_verification

Get details for a specific verification

08

list_accounts

List bank accounts for an organization

09

list_organizations

List all accessible organizations

10

list_payees

List saved payees for an organization

11

list_transactions

Retrieve transaction history for a bank account

12

list_verifications

List KYC/KYB verifications for an organization

Example Prompts for Griffin in VS Code Copilot

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

01

"List my organizations in Griffin"

02

"Show the recent transactions for account ID acc_93021"

03

"Check the KYC verification status for ID ver_88392"

Troubleshooting Griffin MCP Server with VS Code Copilot

Common issues when connecting Griffin 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.

Griffin + VS Code Copilot FAQ

Common questions about integrating Griffin 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 Griffin to VS Code Copilot

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