{"id":"otobo-mcp-server","name":"otobo-mcp-server","homepage":"https://pypi.org/project/otobo-mcp-server/","repo_url":null,"category":"devtools","subcategories":[],"tags":["mcp","ai-agents","it-automation","itsm","otoBo","helpdesk","integration"],"what_it_does":"MCP server package intended to expose OTOBO functionality to an AI agent via the Model Context Protocol, allowing the agent to call MCP tools for actions/data retrieval related to an OTOBO (request/helpdesk/ITSM) instance.","use_cases":["Connect an LLM/agent to an OTOBO instance through MCP tools","Automate ITSM/helpdesk workflows (querying tickets, creating/updating records) via agent-driven tool calls","Build agent assistants for support operations where the agent needs controlled access to OTOBO systems"],"not_for":["Direct public-facing exposure of OTOBO without proper network/auth controls","High-assurance environments where strict auditability, sandboxing, and least-privilege are not clearly supported","Use cases requiring a full REST/GraphQL SDK experience (this is MCP-focused)"],"best_when":"When you already run an OTOBO backend and want an agent-friendly integration through MCP rather than building bespoke REST integrations.","avoid_when":"When you need standardized REST/SDK/OpenAPI contracts for broad client compatibility, or when you cannot ensure secure handling of OTOBO credentials and transport to the MCP server.","alternatives":["Generic MCP-to-HTTP gateway patterns (build MCP tools that wrap your existing REST API)","Direct OTOBO REST API integration if available","Other agent integration layers (custom tool wrappers, workflow automation like n8n/Make + OTOBO APIs)"],"af_score":43.5,"security_score":38.0,"reliability_score":7.5,"package_type":"mcp_server","discovery_source":["pypi"],"priority":"low","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-04-04T21:49:41.202002+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":[],"oauth":false,"scopes":false,"notes":"No authentication details were provided in the prompt; MCP servers typically require some form of upstream authentication/authorization to reach OTOBO, but this cannot be confirmed from the given information."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"Pricing not specified; treated as self-hosted/open-source package unless otherwise documented (not provided here)."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":43.5,"security_score":38.0,"reliability_score":7.5,"mcp_server_quality":65.0,"documentation_accuracy":45.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":50.0,"rate_limit_clarity":20.0,"tls_enforcement":50.0,"auth_strength":40.0,"scope_granularity":20.0,"dependency_hygiene":40.0,"secret_handling":40.0,"security_notes":"Security cannot be fully assessed from the provided prompt. MCP servers typically act as a bridge to an internal system (OTOP/ITSM); key risks include credential exposure, overly-permissive tool actions, lack of request authorization, and insufficient transport/security headers. TLS enforcement, secret handling practices, and least-privilege scope design are not verifiable from the given information.","uptime_documented":0.0,"version_stability":0.0,"breaking_changes_history":0.0,"error_recovery":30.0,"idempotency_support":"false","idempotency_notes":null,"pagination_style":"none","retry_guidance_documented":false,"known_agent_gotchas":["Agents may unintentionally trigger state-changing actions (ticket creation/updates) unless the MCP tool permissions and descriptions are very explicit.","If tool outputs include large/verbose payloads, agents may struggle with context limits; pagination or summarization guidance would be important but is not confirmed.","Without clear rate-limit and retry semantics, agents may re-issue expensive calls repeatedly."]}}