Connects an assistant to the Olist Tiny e-commerce ERP REST API v3 for read-only queries on products, stock, orders, invoices, and finances.
What you can do
Exposes the official Olist Tiny (formerly Tiny ERP) REST API v3 through a single hosted MCP entrypoint, described as a catalog search tool. It covers products, stock, sales orders, NF-e/NFC-e invoices, accounts payable and receivable, contacts, shipping, purchase and service orders, CRM, and price lists. The README states it is read-only and that no tool changes data at the source. It can be paired with a separate banking MCP for reconciliation.
When to use it
Use it when an assistant needs to look up Olist Tiny ERP records such as recent sales orders, current stock for a product, or open receivables for the month. It suits teams already running Olist Tiny who want conversational read access instead of logging into the ERP.
Requirements
A remote MCP-over-HTTP endpoint; no local package or runtime. You create an application in your own Olist account and authorize it with OAuth, and the README mentions magic-link login without a password. Works with any MCP client that supports MCP over HTTP, including Claude, Cursor, VS Code, and ChatGPT.
Before you install
The README says the server is read-only and no tool alters source data, but it also states that data returned by the tools is sent to whichever LLM host you choose, which is a sub-processor outside the provider's control. OAuth authorization grants access to your Olist account, and pricing starts from a free tier with paid plans above it. Review the privacy and LGPD documentation before connecting business data.
Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.mcp-dir%2Folist-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.
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.
Show the current MCP platform and adapter versions.
Takes no parameters.
report_bug
Report Bug
Report a bug, missing feature, or send feedback. Include the conversation array with recent messages for reproduction.
Parameterscontextmessagerequiredconversation
connect
Connection Status
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.
Takes no parameters.
authenticate
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.
Parameterstoken
toolkit_info
Toolkit Info
Returns the current toolkit state: installed MCPs, their connection status, the accounts connected to each one, and how many catalog tools each exposes.
Takes no parameters.
marketplace
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. It also carries the mcp.ai PROMPT LIBRARY, which is about ready-made prompt TEXT rather than MCPs: search_prompts finds one, get_prompt returns its full text with {{variables}} filled, and publish_prompt saves a prompt and returns a shareable mcp.ai/p/<slug> link that opens without login.
Parameterslimitqueryactionmcp_idmessagetool_idargumentsimmediatetier_slugprompt_bodyprompt_slugprompt_tool+11 more
Version history
1
v0.1.0LatestSep 16, 2026
Score
75%
75% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
License10 pts
Declare a license in the repository or the registry entry.