Bring Screen Sharing
to LlamaIndex
Learn how to connect join.me 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 join.me MCP Server?
Connect your join.me account to any AI agent and manage video meetings through natural conversation.
What you can do
- Meeting Scheduling — Create, update, and cancel meetings with customizable settings
- Participant Management — Invite participants, track attendance, and manage access
- Recording Access — List and retrieve meeting recordings
- Meeting History — Browse past meetings with duration and participant data
- Settings Configuration — Manage account and meeting preferences
How it works
1. Subscribe to this server
2. Enter your join.me Access Token
3. Start managing meetings from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Teams — schedule meetings and manage invites through AI
- Managers — review meeting history and recording availability
- Assistants — coordinate calendars and meeting logistics
Built-in capabilities (10)
Register a new webhook
Cancel/Delete a meeting
Get details of a specific meeting
me user profile. Get account information
me account. List your join.me meetings
me account. List registered webhooks
Schedule a future meeting
Start an instant meeting
Start a scheduled meeting
Update a scheduled meeting
Why LlamaIndex?
LlamaIndex agents combine join.me 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 join.me tool responses with indexed documents for comprehensive, grounded answers
- —
Query pipeline framework lets you chain join.me tool calls with transformations, filters, and re-rankers in a typed pipeline
- —
Multi-source reasoning: agents can query join.me, a vector store, and a SQL database in a single turn and synthesize results
- —
Observability integrations show exactly what join.me tools were called, what data was returned, and how it influenced the final answer
join.me in LlamaIndex
join.me and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect join.me 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 join.me in LlamaIndex
The join.me 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
join.me for LlamaIndex
Every tool call from LlamaIndex to the join.me MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I schedule meetings and invite participants?
Yes. Create meetings with date, time, duration, and participant list. Update existing meetings and cancel when needed. Each meeting generates a join link for easy sharing.
Can I access meeting recordings?
Yes. List all available recordings and retrieve download links. Recordings include meeting metadata, duration, and participant information.
Can I view past meeting history and attendance?
Yes. Browse meeting history with details including duration, participant count, attendees, and whether the meeting was recorded.
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 join.me 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