Jiminny MCP Server for CursorGive Cursor instant access to 10 tools to Check Jiminny Status, Get Action Items, Get Activity, and more
Cursor is an AI-first code editor built on VS Code that integrates LLM-powered coding assistance directly into the development workflow. Its Agent mode enables autonomous multi-step coding tasks, and MCP support lets agents access external data sources and APIs during code generation.
Ask AI about this App Connector for Cursor
The Jiminny app connector for Cursor 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.
Cursor's Agent mode turns Jiminny into an in-editor superpower. Ask Cursor to generate code using live data from Jiminny and it fetches, processes, and writes. all in a single agentic loop. 10 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
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 Cursor 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 Cursor
When Cursor 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 Cursor via MCP
Follow these steps to wire Jiminny into Cursor. The entire setup takes under two minutes — your credentials stay safe behind the Vinkius.
Open MCP Settings
Cmd+Shift+P (macOS) or Ctrl+Shift+P (Windows/Linux) → search "MCP Settings"Add the server config
mcp.json file that opensSave the file
Start using Jiminny
Why Use Cursor with the Jiminny MCP Server
Cursor AI Code Editor provides unique advantages when paired with Jiminny through the Model Context Protocol.
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
Jiminny + Cursor Use Cases
Practical scenarios where Cursor combined with the Jiminny MCP Server delivers measurable value.
Code generation with live data: ask Cursor to generate a security report module using live DNS and subdomain data fetched through MCP
Automated documentation: have Cursor query your API's tool schemas and generate TypeScript interfaces or OpenAPI specs automatically
Infrastructure-as-code: Cursor can fetch domain configurations and generate corresponding Terraform or CloudFormation templates
Test scaffolding: ask Cursor to pull real API responses via MCP and generate unit test fixtures from actual data
Example Prompts for Jiminny in Cursor
Ready-to-use prompts you can give your Cursor 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 Cursor
Common issues when connecting Jiminny to Cursor through the Vinkius, and how to resolve them.
Tools not appearing in Cursor
Server shows as disconnected
Jiminny + Cursor FAQ
Common questions about integrating Jiminny MCP Server with Cursor.
What is Agent mode and why does it matter for MCP?
Where does Cursor store MCP configuration?
mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.