Brazilian legal stack in one MCP: lawsuits, court publications, case law, tenders, certificates.
Scored across 7 tools
marketplace and search_tools both cover catalog search, describe, and invoke, making their boundaries unclear. connect and toolkit_info also overlap on reporting connection status, so an agent could easily select the wrong tool for the same task.
All names use lowercase snake_case, but the patterns vary: single-word verbs (authenticate, connect), a noun (marketplace), and compound nouns (toolkit_info). There is no consistent verb_noun convention, though the names remain reasonably readable.
Seven tools is a reasonable size for an MCP platform-management server, and most tools cover distinct operational areas. However, marketplace and search_tools overlap significantly, so the count could be trimmed without losing functionality.
The set covers authentication, connection status, catalog search and execution, toolkit state, version info, and bug reporting, which supports the core platform workflows. The main weakness is that install/uninstall/billing operations are buried inside the marketplace tool description rather than exposed as first-class tools.
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: "" } after the user pastes, or with no args to get the link.
Inputs: token.
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.
Inputs: no named parameters.
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/ link that opens without login.
Inputs: limit, query, action, mcp_id, +19 more.
Report a bug, missing feature, or send feedback. Include the conversation array with recent messages for reproduction.
Inputs: message (required), context, conversation.
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.
Inputs: query, action, queries, tool_id, +3 more.
Show the current MCP platform and adapter versions.
Inputs: no named parameters.
Returns the current toolkit state: installed MCPs, their connection status, the accounts connected to each one, and how many catalog tools each exposes.
Inputs: no named parameters.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Brazilian legal search and jurimetria: 115M+ court decisions from 90+ courts across 14 MCP tools.
Full lookup of a person's or company's lawsuits from the CPF or CNPJ, with per-case detail. Platform
Open-source alternative to Jusbrasil for AI: find lawsuits by name, CPF, CNPJ or case number and bui
Case law search, court decisions and súmulas, across indexed public sources (STF, STJ, TST, state co
Add one secure layer between your agents and this server.