Plugin System

CloudBase MCP uses a plugin-based architecture that supports enabling tool modules on demand. The plugin names, default enabled set, and compatible aliases are subject to DEFAULT_PLUGINS, AVAILABLE_PLUGINS, and PLUGIN_ALIASES in mcp/src/server.ts.

Currently Available Plugins

Plugin Name	Default Enabled	Description	Compatible Aliases
env	Yes	Environment login, environment queries, security domain management	-
database	Yes	NoSQL / SQL / data model capabilities	-
functions	Yes	Cloud function queries, creation, updates, invocation	-
hosting	Yes	Static hosting and domain management	-
storage	Yes	Cloud storage file management	-
setup	Yes	Project templates, IDE rules, and configuration downloads	-
rag	Yes	Knowledge base search and web search	-
cloudrun	Yes	CloudBase Run service initialization, deployment, and management	-
gateway	Yes	Cloud function access entry and route management	-
app-auth	Yes	App-side authentication configuration	auth-config
permissions	Yes	Permissions, roles, and security rule management	access-control, security-rule, security-rules, secret-rule, secret-rules, users
logs	Yes	Log service status and log search	-
agents	Yes	Agent list, details, logs, and management	-
download	Yes	Download remote files to local project	-
invite-code	Yes	AI coding incentive invite code activation	-
capi	Yes	Generic Cloud API calls	-
apps	No	CloudApp application and version management	-

It is recommended to consistently use the canonical names in the table above for new documentation, examples, and configurations; compatible aliases are only used for backward compatibility with old configurations or old prompts.

Plugin Configuration

Enable Specific Plugins

CLOUDBASE_MCP_PLUGINS_ENABLED is used to only enable specified plugins, with multiple plugins separated by commas:

{
  "mcpServers": {
    "cloudbase-mcp": {
      "command": "npx",
      "args": ["npm-global-exec@latest", "@cloudbase/cloudbase-mcp@latest"],
      "env": {
        "CLOUDBASE_MCP_PLUGINS_ENABLED": "env,database,functions,permissions,logs"
      }
    }
  }
}

Disable Specific Plugins

CLOUDBASE_MCP_PLUGINS_DISABLED is used to disable specified plugins from the default plugin set, with multiple plugins separated by commas:

{
  "mcpServers": {
    "cloudbase-mcp": {
      "command": "npx",
      "args": ["npm-global-exec@latest", "@cloudbase/cloudbase-mcp@latest"],
      "env": {
        "CLOUDBASE_MCP_PLUGINS_DISABLED": "rag,download,agents"
      }
    }
  }
}

Hosted Mode URL Parameters

In Hosted Mode, you can control the plugin scope via URL query parameters:

• enable_plugins: only enable specified plugins
• disable_plugins: disable specified plugins from the default plugin set
• Multiple plugin names use comma separation

See connection-modes.mdx for complete examples.

Common Configurations

Scenario	Recommended Plugins
Basic Development	env,database,functions,hosting,storage
App Authentication	env,app-auth,permissions
Backend Only	env,database,functions,permissions,logs
AI Application	env,database,functions,hosting,rag,agents
CloudBase Run Services	env,cloudrun,gateway,logs
WeChat Mini Program Project	Enable env,database,functions,storage,permissions as needed; for project initialization and development workflow, see Project Templates and WeChat Mini Program Skill

Related Documentation

• MCP Tools Reference - View parameter details and descriptions for each tool
• Quick Start - Getting started guide
• Connection Modes - Local Mode and Hosted Mode explanation
• Project Templates - Template download and initialization instructions
• FAQ - Plugin configuration questions