Skip to main content

AI Documentation β€” Skills & MCP

Welcome to ANYMARKET's AI & Automation documentation hub. This space brings together, in a single place, everything the company offers for people who want to work with AI assistants in their day-to-day β€” from end users who want to query information in natural language to developers who want to automate technical workflows.

Two main categories​

The documentation is organized into two big groups:

🧩 Skills​

A skill is a package of instructions that teaches an AI assistant (like Claude Code) how to run a specific workflow from start to finish, always the same way. Think of it as a well-defined "recipe" the assistant follows when you trigger it.

Examples of what a skill can do:

  • Investigate the root cause of a bug (RCA) by pulling data from Azure DevOps, Kibana and the JVM.
  • Generate a PRD (Product Requirements Document) from a User Story.
  • Review a Pull Request following the team's rules.
  • Run QA on a feature against a set of acceptance criteria.

You trigger a skill by typing /skill-name in the assistant, or by using a natural-language phrase (for example, "run the RCA for bug 12345").

β†’ Start with: Skills overview

πŸ”Œ MCP servers​

An MCP server (Model Context Protocol) is a bridge that gives the AI assistant access to external data and tools β€” internal systems, APIs, databases, dashboards. Once connected, the assistant can query those sources in real time and answer based on them.

Examples of what an MCP server enables:

  • "List the 10 most recent ANYMARKET products."
  • "How many orders came in today from Mercado Livre?"
  • "Show me the latest alerts from Kibana."

Each MCP server has its own catalog of available commands, but the user never has to memorize anything β€” just ask in natural language.

β†’ Start with: MCP overview

Who this documentation is for​

The content is designed for three main profiles:

  • Business users who want to use AI to query information and speed up day-to-day tasks (focus on read-only MCPs like the ANYMARKET MCP).
  • Product and QA teams who want to speed up spec, documentation and validation routines using ready-made skills.
  • Developers who want to plug in new MCP servers, build custom skills, or understand the internal mechanics.

Every page notes upfront who it targets, so you can quickly tell what's relevant to you.

How to use this hub​

  1. If you're an end user and just want to start talking to ANYMARKET through Claude/ChatGPT/Gemini, go straight to ANYMARKET MCP.
  2. If you want to see what's available before choosing, take a look at the Skills and MCP overviews.
  3. If you're a developer and will build/maintain skills or MCP servers, start with the overviews β€” each one covers patterns, best practices and extension points.

Support and access​

  • Usage questions, access requests, or production issues: reach out to the team responsible for the product or tool inside your company.
  • Suggesting a new skill or MCP server: open a discussion with the AI & Automation team for evaluation and prioritization.
  • Reporting a documentation bug: every page has an "edit" link at the bottom; open a PR or log the inconsistency for correction.

Where to start​