{"id":"superghazi-nuxeo-mcp-server","name":"nuxeo-mcp-server","homepage":null,"repo_url":"https://github.com/SuperGhazi/nuxeo-mcp-server","category":"infrastructure","subcategories":[],"tags":["mcp","nuxeo","content-management","documents","folders","retrieval","automation","sdk-less-integration","agent-tools"],"what_it_does":"Provides an MCP (Model Context Protocol) server for the Nuxeo platform, enabling agents to create/modify/delete and search folders and documents, and to extract document text content.","use_cases":["Agent-assisted content operations on Nuxeo (CRUD)","Retrieval-augmented generation (RAG) using extracted Nuxeo document text","Automating document/folder organization and indexing workflows in Nuxeo","Information discovery via folder/document search in Nuxeo"],"not_for":["Public, unauthenticated deployment of a content-management integration","Use cases requiring strict SLA guarantees without monitoring/ops setup","Environments that require vendor-provided SDKs or OpenAPI/REST contracts for agent tooling"],"best_when":"When you want an MCP-native integration so LLM agents can directly operate on Nuxeo content for search, retrieval, and document management.","avoid_when":"When the MCP server’s auth model, error contracts, and rate-limit behavior are unknown or cannot be validated in a staging environment.","alternatives":["Nuxeo REST APIs directly (manual tool integration)","Other existing Nuxeo integration libraries/SDKs (if available in your stack)","Custom REST wrapper with OpenAPI and structured errors for agent tooling","Direct search/retrieval via Nuxeo query/search endpoints plus document text extraction pipeline"],"af_score":35.0,"security_score":44.0,"reliability_score":22.5,"package_type":"mcp_server","discovery_source":["github"],"priority":"low","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-04-04T20:02:10.850313+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":["Java"],"openapi_spec_url":null,"webhooks":false},"auth":{"methods":["(Not specified in provided data)"],"oauth":false,"scopes":false,"notes":"Repository description mentions an MCP server for Nuxeo but provided metadata does not specify authentication mechanism, required credentials, or scope model. Auth-related scores are therefore estimated conservatively."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"Self-hosted/open-source style integration; no pricing details present in provided metadata."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":35.0,"security_score":44.0,"reliability_score":22.5,"mcp_server_quality":45.0,"documentation_accuracy":35.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":40.0,"rate_limit_clarity":20.0,"tls_enforcement":60.0,"auth_strength":40.0,"scope_granularity":30.0,"dependency_hygiene":40.0,"secret_handling":50.0,"security_notes":"Only repository metadata is available, so security posture cannot be fully validated. As an MCP server that can mutate content, it should be protected with strong authentication, least-privilege authorization, TLS-only transport, and careful logging to avoid leaking credentials or document contents.","uptime_documented":0.0,"version_stability":35.0,"breaking_changes_history":35.0,"error_recovery":20.0,"idempotency_support":"false","idempotency_notes":null,"pagination_style":"none","retry_guidance_documented":false,"known_agent_gotchas":["Content-management operations (create/modify/delete) can have side effects; without explicit idempotency or safety checks, agents may duplicate work on retries.","Search and text extraction may be expensive; agents may need explicit constraints (query limits, result limits) to avoid large responses/timeouts.","Unknown authentication and Nuxeo-side permission requirements may cause 403/404-like failures that require agent-specific remediation steps."]}}