Jiminny MCP Server for VS Code CopilotGive VS Code Copilot instant access to 10 tools to Check Jiminny Status, Get Action Items, Get Activity, and more
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.
Ask AI about this App Connector for VS Code Copilot
The Jiminny app connector for VS Code Copilot is a standout in the Artificial Intelligence category — giving your AI agent 10 tools to work with, ready to go from day one.
Vinkius delivers Streamable HTTP and SSE to any MCP client
Vinkius Desktop App
The modern way to manage MCP Servers — no config files, no terminal commands. Install Jiminny and 3,400+ MCP Servers from a single visual interface.




{
"mcpServers": {
"jiminny": {
"url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
}
}
}
* 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 Jiminny MCP Server
Connect your Jiminny account to any AI agent and take full control of your sales conversation intelligence and automated coaching workflows through natural conversation.
GitHub Copilot Agent mode brings Jiminny data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 10 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.
What you can do
- Call Portfolio Orchestration — List and manage your entire database of call recordings and transcripts programmatically, retrieving detailed speaker metadata
- Meeting Intelligence Architecture — Programmatically query and monitor meeting insights and key moments to maintain a perfectly coordinated sales audit trail
- Rep Performance Monitoring — Access real-time activity metrics for your sales team and track improvement trends directly through your agent for instant reporting
- Metadata Management — Programmatically retrieve talk-to-listen ratios and filler word counts to maintain a perfectly coordinated coaching record
- Operational Monitoring — Verify account-level API connectivity and monitor call ingestion volume directly through your agent for perfectly coordinated service scaling
The Jiminny MCP Server exposes 10 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.
All 10 Jiminny tools available for VS Code Copilot
When VS Code Copilot connects to Jiminny through Vinkius, your AI agent gets direct access to every tool listed below — spanning conversation-intelligence, sales-coaching, call-recording, and more. Every call is secured with network, filesystem, subprocess, and code evaluation entitlements inside a sandboxed runtime. Beyond a simple connection, you get a full AI Gateway with real-time visibility into agent activity, enterprise governance, and optimized token usage.
Verify Jiminny API connectivity
Get action items from a call
Get activity details
Get aggregate call analytics
Get coaching stats for a user
Get call transcript
Get user details
List all calls and meetings
List all teams
List all team members
Connect Jiminny to VS Code Copilot via MCP
Follow these steps to wire Jiminny into VS Code Copilot. The entire setup takes under two minutes — your credentials stay safe behind the Vinkius.
Create MCP config
.vscode/mcp.json file in your project rootAdd the server config
Enable Agent mode
Start using Jiminny
Why Use VS Code Copilot with the Jiminny MCP Server
GitHub Copilot for Visual Studio Code provides unique advantages when paired with Jiminny through the Model Context Protocol.
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
Jiminny + VS Code Copilot Use Cases
Practical scenarios where VS Code Copilot combined with the Jiminny MCP Server delivers measurable value.
Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step
DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review
Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses
Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples
Example Prompts for Jiminny in VS Code Copilot
Ready-to-use prompts you can give your VS Code Copilot agent to start working with Jiminny immediately.
"List all calls recorded today in Jiminny."
"Get the transcript and action items from call ACT-9421."
"Show coaching stats for user USR-201."
Troubleshooting Jiminny MCP Server with VS Code Copilot
Common issues when connecting Jiminny to VS Code Copilot through the Vinkius, and how to resolve them.
MCP tools not available
Jiminny + VS Code Copilot FAQ
Common questions about integrating Jiminny MCP Server with VS Code Copilot.
Which VS Code version supports MCP?
How do I switch to Agent mode?
Can I restrict which MCP tools Copilot can access?
Does MCP work in VS Code Remote or Codespaces?
.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.