Bring Screen Sharing
to Pydantic AI
Learn how to connect join.me to Pydantic AI 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 Pydantic AI?
Pydantic AI validates every join.me tool response against typed schemas, catching data inconsistencies at build time. Connect 10 tools through Vinkius and switch between OpenAI, Anthropic, or Gemini without changing your integration code. full type safety, structured output guarantees, and dependency injection for testable agents.
- —
Full type safety: every MCP tool response is validated against Pydantic models, catching data inconsistencies before they reach your application
- —
Model-agnostic architecture. switch between OpenAI, Anthropic, or Gemini without changing your join.me integration code
- —
Structured output guarantee: Pydantic AI ensures tool results conform to defined schemas, eliminating runtime type errors
- —
Dependency injection system cleanly separates your join.me connection logic from agent behavior for testable, maintainable code
join.me in Pydantic AI
join.me and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect join.me to Pydantic AI 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 Pydantic AI
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 Pydantic AI 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 Pydantic AI
Every tool call from Pydantic AI 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 Pydantic AI discover MCP tools?
Create an MCPServerHTTP instance with the server URL. Pydantic AI connects, discovers all tools, and generates typed Python interfaces automatically.
Does Pydantic AI validate MCP tool responses?
Yes. When you define result types as Pydantic models, every tool response is validated against the schema. Invalid data raises a clear error instead of silently corrupting your pipeline.
Can I switch LLM providers without changing MCP code?
Absolutely. Pydantic AI abstracts the model layer. your join.me MCP integration works identically with OpenAI, Anthropic, Google, or any supported provider.
MCPServerHTTP not found
Update: pip install --upgrade pydantic-ai