{"id":"workos-meeting-mcp-server","name":"workos-meeting-mcp-server","homepage":"https://pypi.org/project/workos-meeting-mcp-server/","repo_url":"https://github.com/workos/workos-meeting-mcp-server","category":"automation","subcategories":[],"tags":["mcp","workos","meetings","agent-tools","automation"],"what_it_does":"workos-meeting-mcp-server is an MCP server package intended to expose WorkOS meeting-related capabilities to agent runtimes via the Model Context Protocol, likely translating agent tool calls into WorkOS Meeting API operations.","use_cases":["Letting an AI agent create/manage meetings through WorkOS using MCP tool calls","Automating meeting scheduling workflows (e.g., generate links, invite flows, sync events) via agent actions","Integrating WorkOS meeting functionality into agentic assistants with minimal custom glue code"],"not_for":["Direct end-user web UI or interactive scheduling without an API layer","Scenarios requiring an existing REST/GraphQL/SDK integration pattern if you explicitly need HTTP/SDK-only access","Production use without validating authentication, permissions, and error behavior in the deployment you plan to run"],"best_when":"You are building an agent-driven workflow and want WorkOS meeting actions available as MCP tools with consistent tool calling.","avoid_when":"You cannot provide/handle the WorkOS authentication required by the underlying service, or you require a fully documented REST/SDK interface instead of MCP tool abstractions.","alternatives":["Use WorkOS meetings REST API directly (if available) from your own backend","Use official WorkOS SDKs (if available for your language) instead of MCP","Build your own thin MCP server wrapper around the WorkOS API with stricter validation and observability"],"af_score":44.0,"security_score":60.5,"reliability_score":22.5,"package_type":"mcp_server","discovery_source":["pypi"],"priority":"low","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-04-04T21:38:41.144085+00:00","interface":{"has_rest_api":false,"has_graphql":false,"has_grpc":false,"has_mcp_server":true,"mcp_server_url":null,"has_sdk":false,"sdk_languages":[],"openapi_spec_url":null,"webhooks":false},"auth":{"methods":["WorkOS authentication (exact mechanism not confirmed from provided data)"],"oauth":false,"scopes":false,"notes":"The exact auth method, required credentials, and any scope model are not observable from the information provided in this prompt. Expect some form of WorkOS API credentials/keys to be required by the underlying meeting API."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"Pricing for WorkOS is not provided in the supplied content, and MCP server runtime costs (hosting) are also not specified."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":44.0,"security_score":60.5,"reliability_score":22.5,"mcp_server_quality":55.0,"documentation_accuracy":40.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":55.0,"rate_limit_clarity":20.0,"tls_enforcement":80.0,"auth_strength":60.0,"scope_granularity":50.0,"dependency_hygiene":50.0,"secret_handling":60.0,"security_notes":"Security posture depends heavily on how credentials are supplied to the MCP server and whether the server logs request/response payloads. TLS enforcement is assumed typical for networked services but cannot be verified from the provided information. Scope granularity and secret-handling practices are not observable here.","uptime_documented":0.0,"version_stability":50.0,"breaking_changes_history":0.0,"error_recovery":40.0,"idempotency_support":"false","idempotency_notes":null,"pagination_style":"none","retry_guidance_documented":false,"known_agent_gotchas":["MCP tool semantics can hide underlying API retry/idempotency requirements; agents may re-run tool calls after transient failures unless the server explicitly supports idempotency","Rate limiting and backoff behavior may not be clear to the agent unless exposed via structured errors and retry guidance"]}}