Skip to main content
Glama

CPlug (ConnectPlug)

by io.github.mcp-dir

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
NameRequiredDescriptionDefault
limitNo
queryNo
actionNosearch
mcp_idNo
messageNo
tool_idNo
argumentsNo{}
immediateNo
tier_slugNo
prompt_bodyNo
prompt_slugNo
prompt_toolNo
prompt_varsNo{}
conversationNo[]
prompt_titleNo
request_nameNo
cancel_reasonNo
cancel_commentNo
prompt_targetsNo
report_contextNo
prompt_categoryNo
request_detailsNo
prompt_descriptionNo

Schema Changelog

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

  1. Changed9 schema fields changed
    • 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"
+}
  2. Changed1 schema field changed
    • 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"
+]
  3. Changed2 schema fields changed
    • 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"
+}
  4. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Discloses non-obvious behaviors: invoke works even when the MCP is not installed and runs a one-off without bloating the toolkit; auth and payment edge cases are described with connect/checkout links and retry logic; writes require workspace owner/admin; publish_prompt returns a shareable login-free link. These go well beyond the annotation flags and have no contradictions.

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

Conciseness5/5

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

The description is long but every sentence adds distinct value, structured into core flow, key caveats, usage guidance, permissions, and prompt library. It is front-loaded with the primary purpose and uses clear signal words like 'KEY' and 'prefer'.

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

Completeness5/5

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

Covers discovery, execution, installation vs one-off, auth, billing, permissions, and the prompt library in sufficient detail. There is no output schema, but the description explains what key actions return (e.g., connect/checkout links, shareable prompt links, full MCP profiles), making it complete for a complex multi-action tool.

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?

The description effectively explains the core parameters (action, query, mcp_id, tool_id, arguments) through the flow and examples, and references prompt_vars/prompt_slug via the prompt-library actions. However, with 23 parameters and zero schema descriptions, it does not detail several action-specific parameters (cancel_reason, tier_slug, immediate, prompt_category, request_details, etc.), so an agent would need to infer some usage.

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 explicitly identifies the tool as 'the official mcp.ai marketplace — the in-platform catalog of every MCP/tool, AND the way to run them' and details the core flow from search to describe to invoke. It clearly distinguishes the marketplace's broad role from narrower sibling tools.

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?

Offers explicit when-to guidance: 'prefer invoke for a single/occasional use' and 'Use install only to make an MCP PERMANENT'. It also explains each action's purpose (list_tools, subscribe/cancel, report_bug, request_mcp) and contrasts the prompt library vs MCP catalog with clear action paths.

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

All CPlug (ConnectPlug) toolsInspect
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.8/5.0
Disambiguation2/5

marketplace and search_tools both provide search/describe/invoke capabilities for the MCP catalog, creating significant overlap. Additionally, connect and toolkit_info both report connection status, leading to boundary confusion between these pairs.

Naming Consistency3/5

All tool names use lowercase with underscores, but the structural pattern varies: one-word verbs (authenticate, connect), a noun (marketplace), and verb_noun compounds (report_bug, search_tools, show_version, toolkit_info). This is readable but lacks a consistent convention.

Tool Count5/5

Seven tools is well within the ideal 3-15 range for this platform management server, and each tool earns its place in the workflow without feeling bloated or sparse.

Completeness4/5

The toolkit covers authentication, connection status, catalog discovery/execution, installation/subscription (through marketplace actions), feedback, and versioning. Minor gaps exist in dedicated management operations, but core lifecycle coverage is strong.

Resources