Olist MCP
Related Servers
Alternatives to Olist MCP
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityNot gradedmaintenanceAn MCP server that enables LLM agents to interact with PyerP ERP systems via a REST API. It allows users to search, read, create, and update ERP records such as inventory, clients, and users using natural language.-
- AlicenseNot gradedqualityDmaintenanceA generic MCP server that builds its tools at runtime from any OpenAPI specification, enabling interaction with any REST API through natural language.MIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server that exposes any REST API to LLMs through runtime discovery, providing tools to browse endpoints, fetch schemas, and apply business rules without hardcoding or schema duplication.MIT
- AlicenseNot gradedqualityDmaintenanceAn extensible MCP server that integrates Odoo with LLMs to enable querying and managing business data like partners, quotations, and sales orders. It supports custom tool registration and multiple transport protocols for both local and remote communication.2MIT
- AlicenseNot gradedqualityDmaintenanceA generic MCP server that dynamically converts OpenAPI-defined REST APIs into tools for LLMs like Claude. It supports multiple authentication methods and transport protocols, enabling seamless interaction with any OpenAPI-compliant API.23 npmMIT
- AlicenseNot gradedqualityDmaintenanceA universal MCP server that connects any REST API to AI assistants via OpenAPI or Postman specifications. It enables dynamic tool creation with GraphQL-style field selection and automatic schema inference for efficient data retrieval.14 npm6-
TDQS
Scored across 92 tools
Most tools target distinct resource-action pairs (e.g., contato vs produto vs pedido), but there are overlapping invoice operations (nota_fiscal_incluir, nota_fiscal_consumidor_incluir, incluir_nota_xml, pdv_incluir_nota_xml) and inconsistent search variants (expedicao_pesquisa vs expedicao_pesquisar_agrupamentos) that could mislead an agent. The 92-tool scale also makes it hard to select the right tool without deep inspection.
The 'olist_' prefix is consistent, but the pattern mixes noun forms (pesquisa, lista, excecoes, info) with infinitive verbs (pesquisar, incluir, obter, alterar) and sometimes places verbs before the object (incluir_nota_xml vs nota_fiscal_incluir). Some tools are pure nouns (pdv_pedidos, pdv_produtos), and 'pesquisar' appears only once while all other searches use 'pesquisa'.
92 tools is far beyond the practical range for a coherent MCP server, making discovery and selection extremely difficult. Even for a broad ERP API, the tool set should be consolidated (e.g., grouping operations by resource or using parameters) to remain navigable.
The server covers many domains (contracts, products, CRM, orders, invoices, expedition), but lifecycle coverage is inconsistent: many resources have create/get/update/search but no delete (products, contacts, orders, invoices), while others (vendedores, formas_recebimento) are read-only. This leaves dead ends and prevents full workflows without external workarounds.