Monte Bravo MCP

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/ link that opens without login.

Input Schema

TableJSON Schema

Name	Required	Default
`limit`	No
`query`	No
`action`	No	search
`mcp_id`	No
`message`	No
`tool_id`	No
`arguments`	No	{}
`immediate`	No
`tier_slug`	No
`prompt_body`	No
`prompt_slug`	No
`prompt_tool`	No
`prompt_vars`	No	{}
`conversation`	No	[]
`prompt_title`	No
`request_name`	No
`cancel_reason`	No
`cancel_comment`	No
`prompt_targets`	No
`report_context`	No
`prompt_category`	No
`request_details`	No
`prompt_description`	No

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

AddedAug 29, 2026
RemovedAug 29, 2026
AddedAug 26, 2026
RemovedAug 26, 2026

Changed9 schema fields changedAug 10, 2026

changedInput schema / properties / action / enum

Previous value: -[
-  "search",
-  "describe",
-  "install",
-  "uninstall",
-  "subscribe",
-  "cancel",
-  "resume",
-  "report_bug",
-  "request_mcp",
-  "list_tools",
-  "invoke"
-]New value: +[
+  "search",
+  "describe",
+  "install",
+  "uninstall",
+  "subscribe",
+  "cancel",
+  "resume",
+  "report_bug",
+  "request_mcp",
+  "list_tools",
+  "invoke",
+  "search_prompts",
+  "get_prompt",
+  "publish_prompt"
+]

addedInput schema / properties / prompt_body

Added value: +{
+  "default": "",
+  "type": "string"
+}

addedInput schema / properties / prompt_category

Added value: +{
+  "default": "",
+  "type": "string"
+}

addedInput schema / properties / prompt_description

Added value: +{
+  "default": "",
+  "type": "string"
+}

addedInput schema / properties / prompt_slug

Added value: +{
+  "default": "",
+  "type": "string"
+}

addedInput schema / properties / prompt_targets

Added value: +{
+  "default": [],
+  "items": {
+    "enum": [
+      "claude",
+      "chatgpt",
+      "cursor",
+      "lovable"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / prompt_title

Added value: +{
+  "default": "",
+  "type": "string"
+}

addedInput schema / properties / prompt_tool

Added value: +{
+  "default": "",
+  "type": "string"
+}

addedInput schema / properties / prompt_vars

Added value: +{
+  "default": "{}",
+  "type": "string"
+}

Changed1 schema field changedJul 29, 2026

changedInput schema / properties / action / enum

Previous value: -[
-  "search",
-  "describe",
-  "install",
-  "uninstall",
-  "subscribe",
-  "cancel",
-  "report_bug",
-  "request_mcp",
-  "list_tools",
-  "invoke"
-]New value: +[
+  "search",
+  "describe",
+  "install",
+  "uninstall",
+  "subscribe",
+  "cancel",
+  "resume",
+  "report_bug",
+  "request_mcp",
+  "list_tools",
+  "invoke"
+]

Changed2 schema fields changedJul 10, 2026

addedInput schema / properties / cancel_comment

Added value: +{
+  "default": "",
+  "type": "string"
+}

addedInput schema / properties / cancel_reason

Added value: +{
+  "enum": [
+    "too_expensive",
+    "missing_features",
+    "switched_service",
+    "unused",
+    "customer_service",
+    "too_complex",
+    "low_quality",
+    "other"
+  ],
+  "type": "string"
+}

AddedJun 30, 2026
RemovedJun 22, 2026
First observedJun 11, 2026

TDQS

A4.6/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description discloses important behavioral traits beyond annotations: invoke works even when the MCP is not installed, credential/logins return a connect link, paid tools with empty wallet return a checkout/top-up link, and install makes an MCP permanent. It also notes that writes (install/uninstall/subscribe/cancel and the one-off install behind invoke) require owner/admin. Annotations provide readOnlyHint=false and destructiveHint=false, which do not contradict the description; the description adds meaningful operational context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single dense paragraph with several long, run-on sentences and many embedded clauses. It front-loads the core purpose and flow well, but the prompt-library section is tacked on at the end and the whole text is harder to parse than it should be. Some bolding or bullet structure would have earned a higher score; every sentence does carry information, but the overall structure lacks conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's high complexity (23 parameters, 14 actions, no output schema), the description is quite complete: it explains the main flows, write permissions, authentication/link behavior, and prompt-library operations. It does not describe the exact result format of search/list_tools or error conditions, but for a broad dispatcher tool it provides enough context for an agent to choose and invoke the appropriate action.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and no parameters have descriptions. The description compensates by mapping key action values to their semantics: search, describe, invoke with 'tool_id', install, subscribe/cancel, report_bug, request_mcp, and the prompt-related actions. It explains important argument roles (tool_id, prompt_vars, prompt_slug). However, it does not elaborate on many secondary parameters (limit, tier_slug, cancel_reason, conversation, etc.), so it is not a complete substitute for schema-level parameter documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a strong, specific statement: 'The official mcp.ai marketplace — the in-platform catalog of every MCP/tool, AND the way to run them.' It clearly names the resource and the core verbs (search, describe, invoke, install, list_tools, subscribe/cancel, prompts). It distinguishes itself from sibling openfinance tools and utility tools by establishing itself as the central MCP catalog and execution layer.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives explicit usage guidance: 'Core flow: action=search discovers MCPs by intent → describe returns one MCP's full profile ... → invoke RUNS that tool.' It also contrasts invoke vs install ('prefer invoke for a single/occasional use'), names list_tools for 'what is callable right now', assigns billing actions to subscribe/cancel, and states that writes require workspace owner/admin. This is far beyond generic guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Monte Bravo MCP tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0

Disambiguation3/5

Most openfinance_* tools target distinct resource/action pairs, but openfinance_list_connections and openfinance_get_item_status overlap on connection status/reconnect URLs, and openfinance_list_transactions vs openfinance_list_transactions_by_item can be confused. The long descriptions reduce ambiguity, but selection risk remains.

Naming Consistency3/5

The openfinance_* block is consistently verb_noun, but the platform tools mix bare verbs (authenticate, connect), nouns (marketplace), and noun_info (toolkit_info). No single naming convention spans the whole set, though each subgroup is internally readable.

Tool Count3/5

At 25 tools, this sits at the top of the heavy borderline range. The broad scope—MCP.AI platform management, prompt library, and Open Finance data—justifies many tools, but the set feels like a bundled suite rather than a tightly scoped single-purpose server.

Completeness4/5

The Open Finance side is well covered: accounts, balances, transactions, credit card bills, loans, investments, connections, sync, status, provider health, and category updates. The platform side has auth, toolkit info, marketplace, and feedback. Minor gaps exist, such as no explicit identity fetch or payment initiation, but those seem outside the intended read/analysis domain.

marketplace

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

TDQS

Resources