Bring Conversation Intelligence
to VS Code Copilot
Learn how to connect Jiminny to VS Code Copilot and start using 10 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the 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.
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
How it works
1. Subscribe to this server
2. Retrieve your API Key from your Jiminny dashboard (Settings > API)
3. Start orchestrating your sales growth from Claude, Cursor, or any MCP client
No more manual reviewing of long call recordings or missing coaching opportunities. Your AI acts as your dedicated sales coach and conversation architect.
Who is this for?
- Sales Managers — instantly retrieve call summaries and monitor rep improvement using natural language commands
- Enablement Leads — verify individual meeting metadata and track coaching activity without leaving your creative workspace
- Developers — integrate high-speed Jiminny conversation data into custom CRM and BI tools through simple AI queries
Built-in capabilities (10)
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
Why VS Code Copilot?
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.
- —
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 in VS Code Copilot
Jiminny and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Jiminny to VS Code Copilot through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Jiminny in VS Code Copilot
The Jiminny 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. All 10 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in VS Code Copilot only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* 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
How Vinkius secures
Jiminny for VS Code Copilot
Every tool call from VS Code Copilot to the Jiminny MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How do I access call transcripts via AI?
Use the get_transcript tool with the activity ID to retrieve the full transcript with speaker identification and timestamps.
Can my agent extract action items from calls?
Yes. Use get_action_items to retrieve all AI-detected follow-ups and tasks from any recorded conversation.
How do I review coaching metrics for my team?
Use get_coaching_stats with the user ID to see call scores, framework ratings, and improvement trends for any team member.
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.
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.
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.
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.
MCP tools not available
Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.