Bring Conversation Intelligence
to LlamaIndex
Learn how to connect Jiminny to LlamaIndex 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 LlamaIndex?
LlamaIndex agents combine Jiminny tool responses with indexed documents for comprehensive, grounded answers. Connect 10 tools through Vinkius and query live data alongside vector stores and SQL databases in a single turn. ideal for hybrid search, data enrichment, and analytical workflows.
- —
Data-first architecture: LlamaIndex agents combine Jiminny tool responses with indexed documents for comprehensive, grounded answers
- —
Query pipeline framework lets you chain Jiminny tool calls with transformations, filters, and re-rankers in a typed pipeline
- —
Multi-source reasoning: agents can query Jiminny, a vector store, and a SQL database in a single turn and synthesize results
- —
Observability integrations show exactly what Jiminny tools were called, what data was returned, and how it influenced the final answer
Jiminny in LlamaIndex
Jiminny and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Jiminny to LlamaIndex 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 LlamaIndex
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 LlamaIndex 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 LlamaIndex
Every tool call from LlamaIndex 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.
How does LlamaIndex connect to MCP servers?
Use the MCP client adapter to create a connection. LlamaIndex discovers all tools and wraps them as query engine tools compatible with any LlamaIndex agent.
Can I combine MCP tools with vector stores?
Yes. LlamaIndex agents can query Jiminny tools and vector store indexes in the same turn, combining real-time and embedded data for grounded responses.
Does LlamaIndex support async MCP calls?
Yes. LlamaIndex's async agent framework supports concurrent MCP tool calls for high-throughput data processing pipelines.
BasicMCPClient not found
Install: pip install llama-index-tools-mcp