# Olist Tiny ERP MCP server

Olist Tiny e-commerce ERP (formerly Tiny ERP) with the full official REST API v3, products, stock, o

## Links
- Registry page: https://www.getdrio.com/mcp/io-github-mcp-dir-olist-mcp
- Repository: https://github.com/mcp-dir/olist-mcp

## Install
- Endpoint: https://api.mcp.ai/p_olist
- Auth: Not captured

## Setup notes
- Remote endpoint: https://api.mcp.ai/p_olist

## Tools
- search_tools - Single entrypoint for MCP catalog. action=search returns available tools ordered by relevance. action=describe returns tool schema. action=invoke executes a tool by ID. Endpoint: https://api.mcp.ai/p_olist
- show_version - Show the current MCP platform and adapter versions. Endpoint: https://api.mcp.ai/p_olist
- report_bug - Report a bug, missing feature, or send feedback. Include the conversation array with recent messages for reproduction. Endpoint: https://api.mcp.ai/p_olist
- connect - Returns connection status and URLs. When all providers are connected, returns authenticated:true and empty pending[]. When credentials are missing, returns connect_url for the toolkit and per-install URLs. Endpoint: https://api.mcp.ai/p_olist
- authenticate - MCP.AI for IDE agents (Cursor, etc.): log in in the browser, copy the access token. Best: add it to this server's config as a header `Authorization: Bearer <token>` for a permanent, non-expiring connection. Or paste it here for a session-only login: call with { token: "<jwt>" } after the user pastes, or with no args to get the link. Endpoint: https://api.mcp.ai/p_olist
- toolkit_info - Returns the current toolkit state: installed MCPs, their connection status, and how many catalog tools each exposes. Endpoint: https://api.mcp.ai/p_olist
- marketplace - The official mcp.ai marketplace — the in-platform catalog of every MCP/tool, AND the way to run them. Covers capability requests like "find an MCP that does X", "consulta um CPF", "is there a tool for Y". Core flow: action=search discovers MCPs by intent → describe returns one MCP's full profile (every tool with its id + params, pricing, auth) so you pick the right tool_id → invoke RUNS that tool. KEY: invoke works even when the MCP is NOT installed — it runs the tool pontualmente (one-off), without adding the MCP to the toolkit and without bloating the tool list. If the MCP needs a credential/login, invoke returns a connect link; if it is paid and the wallet is empty, invoke returns a checkout/top-up link (the user opens it, then you retry). Use install only to make an MCP PERMANENT in the active toolkit (its tools then show up natively in future sessions); prefer invoke for a single/occasional use. list_tools lists what is callable right now. subscribe/cancel handle per-MCP billing; report_bug sends feedback; request_mcp asks us to build a NEW MCP when nothing fits. Search/describe flag installed_in_toolkit vs installed_in_workspace. Writes (install/uninstall/subscribe/cancel and the one-off install behind invoke) require workspace owner/admin. Endpoint: https://api.mcp.ai/p_olist

## Resources
Not captured

## Prompts
Not captured

## Metadata
- Owner: io.github.mcp-dir
- Version: 0.1.0
- Runtime: Streamable Http
- Transports: HTTP
- License: Not captured
- Language: Not captured
- Stars: Not captured
- Updated: Jun 12, 2026
- Source: https://registry.modelcontextprotocol.io