Skip to main content
Glama
PCDCK

ozon-mcp

by PCDCK
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to ozon-mcp

No user-submitted related servers found.

    Related Servers

    • OZON MCP

      wbcyclist
      A
      license
      A
      quality
      B
      maintenance
      A knowledge-based MCP server for Ozon sellers, enabling AI agents to search a 42-lesson Chinese operations playbook and discover/call over 460 Seller and Performance API methods for real business actions.
      6
      15
      2
      MIT

    • OZON MCP

      yifan4243-sketch
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for Ozon sellers with a built-in Chinese operations knowledge base and 466 API methods, enabling AI agents to discover, understand, and execute Ozon Seller and Performance API operations safely and efficiently.
      1
      MIT

    • ozon-mcp-server

      DeviceIngineering
      A
      license
      C
      quality
      A
      maintenance
      MCP server for the Ozon Seller and Performance API: 151 tools for prices, promotions, ads, orders, returns, finance and analytics. Multi-store, encrypted keys, web dashboard and self-diagnostics; Docker with SSE or stdio.
      156
      172 PyPI
      5
      MIT

    • wildberries-mcp

      shndo1337
      F
      license
      Not graded
      quality
      D
      maintenance
      MCP server that turns Wildberries marketplace into a toolkit for LLM agents, enabling product search, detailed card inspection, price history, reviews, and cross-product comparison.
      -

    • Avito MCP

      elchin92
      A
      license
      A
      quality
      A
      maintenance
      Universal MCP server for the Avito API (Russia's largest classifieds marketplace), built for autonomous AI agents to operate an account hands-free — 145 tools across 18 domains (listings, messenger, orders, delivery, promotion, autoload, reviews, analytics). Safe-by-default: dry-run, idempotency, structured errors, confirmation flow.
      144
      257 npm
      21
      MIT

    • ozon-mcp-ru

      ilyautov
      A
      license
      A
      quality
      A
      maintenance
      Ozon Seller API in your AI assistant: products, FBS and FBO orders, prices, stocks, finance and reviews. 441 methods live in a YAML catalog the server executes, the agent searches it in plain language and calls a method through three generic tools, and every method carries an access class so writes and irreversible calls ask for confirmation.
      25
      38 PyPI
      3
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.2/5.0

    Scored across 15 tools

    Disambiguation4/5

    Most tools are clearly distinct: listing sections, searching methods, describing methods, workflows, rate limits, errors, examples, and calling methods all have separate purposes. The only mild overlap is between ozon_list_sections and ozon_get_section (both navigate the API structure), but their roles are differentiated enough by description.

    Naming Consistency4/5

    The tools follow a consistent ozon_verb_noun pattern (list_sections, search_methods, describe_method, get_section, get_related_methods, list_workflows, get_workflow, get_rate_limits, get_error_catalog, get_examples, get_swagger_meta, list_methods_for_subscription, get_subscription_status, call_method, fetch_all). Minor deviation: ozon_fetch_all uses a verb+adverb instead of verb_noun, and ozon_call_method is a generic verb rather than a resource-specific one, but the pattern is otherwise highly predictable.

    Tool Count5/5

    15 tools is well-scoped for an Ozon API MCP server that needs to cover discovery, documentation, workflows, rate limits, errors, examples, and execution. Each tool serves a distinct function in the API exploration and calling lifecycle, and none feel redundant.

    Completeness5/5

    The server covers the full API interaction lifecycle: orientation (list_sections), search (search_methods), deep documentation (describe_method), related methods, curated workflows, rate limits, errors, examples, subscription gating, direct calling, and pagination. There are no obvious dead ends—an agent can discover, understand, and execute any Ozon API method.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources