Jiminny MCP Server for Claude DesktopGive Claude Desktop instant access to 10 tools to Check Jiminny Status, Get Action Items, Get Activity, and more
Claude Desktop is Anthropic's native application for interacting with Claude AI models on macOS and Windows. It was the first consumer application to ship with built-in MCP support, making it the reference implementation for the Model Context Protocol standard.
Ask AI about this App Connector for Claude Desktop
The Jiminny app connector for Claude Desktop 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": {
// Your Vinkius token. get it at cloud.vinkius.com
"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.
Claude Desktop is the definitive way to connect Jiminny to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 10 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.
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 Claude Desktop 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 Claude Desktop
When Claude Desktop 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 Claude Desktop via MCP
Follow these steps to wire Jiminny into Claude Desktop. The entire setup takes under two minutes — your credentials stay safe behind the Vinkius.
Open Claude Desktop Settings
claude_desktop_config.jsonAdd the MCP Server
mcpServers sectionRestart Claude Desktop
Start using Jiminny
Why Use Claude Desktop with the Jiminny MCP Server
Claude Desktop by Anthropic provides unique advantages when paired with Jiminny through the Model Context Protocol.
Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available
Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface
Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions
Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network
Jiminny + Claude Desktop Use Cases
Practical scenarios where Claude Desktop combined with the Jiminny MCP Server delivers measurable value.
Interactive data exploration: ask Claude to query DNS records, look up WHOIS data, and cross-reference results in a single conversation
Ad-hoc security audits: type a domain name and let Claude enumerate subdomains, check DNS history, and flag configuration anomalies. all through natural language
Executive briefings: generate comprehensive domain intelligence reports by asking Claude to compile findings into a formatted summary
Learning and training: new team members can explore API capabilities conversationally without needing to read documentation
Example Prompts for Jiminny in Claude Desktop
Ready-to-use prompts you can give your Claude Desktop 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 Claude Desktop
Common issues when connecting Jiminny to Claude Desktop through the Vinkius, and how to resolve them.
Server not appearing after restart
~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).Authentication error
Tools not showing in chat
Jiminny + Claude Desktop FAQ
Common questions about integrating Jiminny MCP Server with Claude Desktop.
How does Claude Desktop discover MCP tools?
claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.What happens if the MCP server is temporarily unavailable?
Can I connect multiple MCP servers simultaneously?
mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.