{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"awesome-webex","slug":"webex","name":"Webex","type":"mcp","url":"https://github.com/Kashyap-AI-ML-Solutions/webex-messaging-mcp-server","page_url":"https://unfragile.ai/webex","categories":["mcp-servers"],"tags":[],"pricing":{"model":"open_source","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"awesome-webex__cap_0","uri":"capability://tool.use.integration.webex.message.sending.via.mcp.protocol","name":"webex message sending via mcp protocol","description":"Enables AI assistants to send messages to Webex spaces and direct conversations through the Model Context Protocol, translating natural language intents into Webex API calls. The MCP server acts as a bridge between LLM tool-use requests and Webex's REST API, handling authentication via bearer tokens and message formatting for both plain text and markdown content.","intents":["Send notifications or alerts from an AI agent to a Webex space without manual intervention","Automate message delivery to specific team members or channels as part of a workflow","Enable an LLM to proactively communicate task completion or status updates to Webex users"],"best_for":["Teams using Webex as their primary collaboration platform who want AI agents to participate in messaging workflows","Developers building LLM agents that need to notify users across Webex without custom API integration code"],"limitations":["Requires valid Webex API bearer token with messaging scopes; token expiration or revocation will break message delivery","No built-in message queuing or retry logic — failed sends are not automatically retried","Message formatting limited to Webex's supported markdown subset; complex formatting may not render as expected","No support for message threading or reply-to semantics — all messages are top-level"],"requires":["Webex API bearer token with 'spark:messages_write' scope","Valid Webex space ID or person ID for message recipient","MCP client implementation (e.g., Claude Desktop, custom LLM framework with MCP support)","Network access to Webex API endpoints (api.webex.com)"],"input_types":["text (plain message content)","structured JSON (room/person ID, message body, markdown flag)"],"output_types":["structured JSON (message ID, timestamp, delivery status)","error responses with HTTP status codes"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-webex__cap_1","uri":"capability://memory.knowledge.webex.message.retrieval.and.conversation.history.access","name":"webex message retrieval and conversation history access","description":"Allows AI assistants to fetch and read messages from Webex spaces and direct conversations through MCP, enabling context-aware responses based on conversation history. The server queries Webex's message API with pagination support, returning message metadata (sender, timestamp, content) that LLMs can analyze for context or decision-making.","intents":["Retrieve recent conversation history from a Webex space to provide context-aware responses","Search or analyze past messages in a space to answer questions about prior discussions","Build conversation context for an AI agent before generating a response in a Webex thread"],"best_for":["AI agents that need to understand prior context before responding in Webex conversations","Teams building knowledge-base or FAQ bots that reference historical Webex discussions"],"limitations":["Message retrieval is limited by Webex API rate limits (typically 100 requests per minute per token)","Pagination requires manual iteration; no built-in streaming or bulk export of large message sets","Cannot retrieve deleted messages or access message edit history","Requires 'spark:messages_read' scope; cannot access messages from spaces the token's user is not a member of"],"requires":["Webex API bearer token with 'spark:messages_read' scope","Valid Webex space ID or person ID","MCP client with support for resource-based retrieval (not just tool-calling)"],"input_types":["structured JSON (space/person ID, optional pagination parameters, optional timestamp filters)"],"output_types":["structured JSON array of message objects (id, personId, personEmail, text, created, updated)","pagination metadata (nextUrl for fetching additional pages)"],"categories":["memory-knowledge","search-retrieval"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-webex__cap_2","uri":"capability://tool.use.integration.webex.space.and.membership.management.via.mcp","name":"webex space and membership management via mcp","description":"Provides AI assistants with the ability to list, create, and manage Webex spaces and room memberships through MCP tool calls. The server translates LLM intents into Webex API operations for space CRUD, member addition/removal, and space metadata queries, with schema validation for space properties like title and description.","intents":["Automatically create a new Webex space for a project or team without manual UI interaction","Add or remove members from a space based on AI-driven logic (e.g., onboarding workflows)","Query space metadata and membership lists to understand team structure or space status"],"best_for":["Organizations automating team onboarding or project setup workflows via AI agents","Developers building Webex workspace management tools that integrate with LLM decision-making"],"limitations":["Space creation and member management require elevated API scopes ('spark:rooms_write', 'spark:memberships_write'); not all tokens have these permissions","No support for space moderation features (e.g., setting message retention policies, encryption settings)","Bulk member operations require iterative API calls; no batch endpoint for adding/removing multiple members at once","Space deletion is not supported via this MCP server (Webex API limitation for safety)"],"requires":["Webex API bearer token with 'spark:rooms_read', 'spark:rooms_write', 'spark:memberships_read', 'spark:memberships_write' scopes","Appropriate Webex organization permissions (admin or space creator role)","MCP client with tool-calling support"],"input_types":["structured JSON (space title, description, member emails, space ID for queries)"],"output_types":["structured JSON (space objects with id, title, created, updated; membership objects with personId, personEmail, membershipId)"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-webex__cap_3","uri":"capability://tool.use.integration.mcp.protocol.translation.and.schema.validation.for.webex.operations","name":"mcp protocol translation and schema validation for webex operations","description":"The MCP server implements the Model Context Protocol specification to translate between LLM tool-use requests and Webex API calls, including schema validation, error handling, and response formatting. It uses MCP's tool and resource definitions to expose Webex capabilities with typed parameters, ensuring that LLM-generated requests conform to Webex API requirements before execution.","intents":["Ensure that AI-generated Webex API calls are valid and safe before execution","Provide LLMs with clear, typed schemas for Webex operations so they understand required and optional parameters","Translate between MCP's standardized request/response format and Webex's REST API conventions"],"best_for":["Developers building LLM agents that need type-safe, validated access to Webex APIs","Teams using MCP-compatible LLM clients (Claude Desktop, custom frameworks) who want Webex integration without custom code"],"limitations":["Schema validation is limited to MCP's JSON Schema support; complex Webex API constraints (e.g., conditional required fields) may not be fully expressible","Error messages from Webex API are passed through with minimal translation; developers need Webex API documentation to debug failures","No built-in request/response logging or audit trail; integrators must implement their own logging if needed","MCP protocol overhead adds latency (~50-100ms per request) compared to direct Webex SDK calls"],"requires":["MCP server implementation (Node.js or Python SDK)","MCP client that supports tool-calling and resource protocols","Webex API documentation to understand schema constraints and error codes"],"input_types":["MCP tool call requests (JSON with tool name and parameters)","MCP resource read requests (JSON with resource URI)"],"output_types":["MCP tool result responses (JSON with success/error status and data)","MCP resource content responses (JSON with resource data and metadata)"],"categories":["tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-webex__cap_4","uri":"capability://safety.moderation.webex.authentication.and.token.management.via.mcp","name":"webex authentication and token management via mcp","description":"Handles Webex API authentication by accepting bearer tokens and managing their lifecycle within the MCP server context. The server validates tokens, handles authentication errors, and provides clear error messages when tokens are invalid or lack required scopes, without exposing token details in logs or responses.","intents":["Securely authenticate to Webex API using bearer tokens without embedding credentials in LLM prompts","Detect and report authentication failures (invalid tokens, insufficient scopes) to the LLM for error handling","Ensure that all Webex API calls include proper authorization headers"],"best_for":["Developers deploying Webex MCP servers in shared environments who need secure token handling","Teams using Webex OAuth flows and need a secure way to pass tokens to AI agents"],"limitations":["Tokens are passed as environment variables or configuration; no built-in token refresh mechanism (requires manual token rotation)","No support for OAuth 2.0 authorization code flow; tokens must be obtained separately and provided to the server","Token expiration is not proactively detected; expired tokens will cause API calls to fail with 401 errors","No audit logging of authentication attempts or token usage; integrators must implement their own monitoring"],"requires":["Valid Webex API bearer token (obtained from Webex developer portal or OAuth flow)","Token must have appropriate scopes for intended operations (spark:messages_read, spark:messages_write, etc.)","Environment variable or configuration file to store token securely"],"input_types":["bearer token (string, typically 100+ characters)"],"output_types":["authentication status (success/failure), error messages with scope requirements"],"categories":["safety-moderation","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-webex__cap_5","uri":"capability://tool.use.integration.webex.file.attachment.and.media.handling.via.mcp","name":"webex file attachment and media handling via mcp","description":"Enables AI assistants to upload and reference files in Webex messages through MCP, translating file paths or URLs into Webex-compatible attachments. The server handles file type validation, size limits, and Webex's file upload API, allowing LLMs to attach documents, images, or other media to messages without manual file handling.","intents":["Attach generated reports, documents, or images to Webex messages sent by an AI agent","Upload files to a Webex space as part of an automated workflow (e.g., daily reports, alerts)","Reference external files or URLs in Webex messages with proper attachment formatting"],"best_for":["AI agents that generate or process files and need to share them with Webex users","Automation workflows that produce reports or artifacts and need to deliver them via Webex"],"limitations":["File size limits enforced by Webex API (typically 1GB per file); large files will fail to upload","Supported file types are limited by Webex's content policy; certain file types may be blocked or quarantined","File uploads are synchronous; no support for background uploads or progress tracking","No built-in file versioning or replacement; uploading a file with the same name creates a duplicate","Requires file to be accessible to the MCP server (local filesystem or accessible URL); cannot directly access files from LLM context"],"requires":["Webex API bearer token with 'spark:messages_write' scope","File path or URL accessible to the MCP server","Sufficient Webex storage quota in the space or organization"],"input_types":["file path (local filesystem)","URL (external file reference)","structured JSON (file metadata, target space/person ID)"],"output_types":["structured JSON (file ID, upload status, file URL in Webex)"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-webex__cap_6","uri":"capability://search.retrieval.webex.user.and.person.lookup.via.mcp","name":"webex user and person lookup via mcp","description":"Provides AI assistants with the ability to search for and retrieve Webex user information (email, display name, user ID) through MCP, enabling context-aware addressing of messages and membership operations. The server queries Webex's people API with optional filters, returning user metadata that LLMs can use to identify recipients or validate user existence.","intents":["Look up a Webex user's ID or email to send them a direct message without manual user ID lookup","Verify that a user exists in the Webex organization before adding them to a space","Search for users by name or email to populate membership lists or recipient lists dynamically"],"best_for":["AI agents that need to dynamically identify Webex users for messaging or space management","Automation workflows that add team members to spaces based on user lookup results"],"limitations":["User search is limited by Webex API rate limits and may not return all matching users if result sets are large","Cannot search by arbitrary user attributes; limited to email, display name, and user ID","User information returned is limited to publicly visible fields; sensitive user data (phone, location) requires additional API scopes","Search results may include inactive or deprovisioned users; no built-in filtering for active users only"],"requires":["Webex API bearer token with 'spark:people_read' scope","User email, display name, or user ID to search for"],"input_types":["structured JSON (search query: email, displayName, or userId)"],"output_types":["structured JSON array of person objects (id, emails, displayName, avatar, created)"],"categories":["search-retrieval","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":30,"verified":false,"data_access_risk":"high","permissions":["Webex API bearer token with 'spark:messages_write' scope","Valid Webex space ID or person ID for message recipient","MCP client implementation (e.g., Claude Desktop, custom LLM framework with MCP support)","Network access to Webex API endpoints (api.webex.com)","Webex API bearer token with 'spark:messages_read' scope","Valid Webex space ID or person ID","MCP client with support for resource-based retrieval (not just tool-calling)","Webex API bearer token with 'spark:rooms_read', 'spark:rooms_write', 'spark:memberships_read', 'spark:memberships_write' scopes","Appropriate Webex organization permissions (admin or space creator role)","MCP client with tool-calling support"],"failure_modes":["Requires valid Webex API bearer token with messaging scopes; token expiration or revocation will break message delivery","No built-in message queuing or retry logic — failed sends are not automatically retried","Message formatting limited to Webex's supported markdown subset; complex formatting may not render as expected","No support for message threading or reply-to semantics — all messages are top-level","Message retrieval is limited by Webex API rate limits (typically 100 requests per minute per token)","Pagination requires manual iteration; no built-in streaming or bulk export of large message sets","Cannot retrieve deleted messages or access message edit history","Requires 'spark:messages_read' scope; cannot access messages from spaces the token's user is not a member of","Space creation and member management require elevated API scopes ('spark:rooms_write', 'spark:memberships_write'); not all tokens have these permissions","No support for space moderation features (e.g., setting message retention policies, encryption settings)","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.05,"quality":0.39,"ecosystem":0.39999999999999997,"match_graph":0.25,"freshness":0.6,"weights":{"adoption":0.25,"quality":0.25,"ecosystem":0.15,"match_graph":0.23,"freshness":0.12}},"observed_outcomes":{"matches":0,"success_rate":0,"avg_confidence":0,"top_intents":[],"last_matched_at":null},"maintenance":{"status":"active","updated_at":"2026-06-17T09:51:04.689Z","last_scraped_at":"2026-05-03T14:00:15.503Z","last_commit":null},"community":{"stars":null,"forks":null,"weekly_downloads":null,"model_downloads":null,"model_likes":null}},"distribution":{"claim_url":"https://unfragile.ai/submit?claim=webex","compare_url":"https://unfragile.ai/compare?artifact=webex"}},"signature":"WD6uyMM/pQmPHcETe/rVLOnfkBRxm6/JhLfUJmalSPemH7xfQX2r5B2iYeqf+p40uAdagUPfGQk+TJa31kPSDg==","signedAt":"2026-06-21T20:02:05.703Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/webex","artifact":"https://unfragile.ai/webex","verify":"https://unfragile.ai/api/v1/verify?slug=webex","publicKey":"https://unfragile.ai/api/v1/trust-passport-public-key","spec":"https://unfragile.ai/trust","schema":"https://unfragile.ai/schema.json","docs":"https://unfragile.ai/docs"}}