What Is the Marketplace
MCP servers are lightweight services that expose tools to the Creor agent via the Model Context Protocol. Each server provides one or more tools that the agent can call during a conversation -- for example, a Supabase server provides tools to query databases, manage tables, and deploy edge functions.
The Marketplace is a curated directory of community-built and officially maintained MCP servers. You can browse available servers, install them to your workspace with one click, and manage their configuration from the dashboard.
Note
Browsing Servers
Access the Marketplace from Dashboard > Marketplace or from the IDE via Settings > Tools & MCP > Browse Marketplace.
Search and Filter
- Search by name, description, or tool name (e.g., "database", "slack", "github").
- Filter by category: Databases, Cloud, DevOps, Productivity, Communication, Design, Analytics.
- Sort by: popularity (installs), rating, recently updated, or alphabetical.
- View tags for quick filtering (e.g., "official", "community", "beta").
Server Detail Page
Each server has a detail page showing:
- Description and screenshots.
- List of tools provided with parameter schemas.
- Configuration requirements (API keys, environment variables).
- Install count, rating, and reviews.
- Author information and source code link.
- Version history and changelog.
Installing Servers
Install a server from its detail page or from the search results.
One-Click Install
- Click "Install" on the server's card or detail page.
- If the server requires configuration (API keys, etc.), a setup form appears.
- Enter the required configuration values.
- Click "Activate" to start the server.
- The server's tools are now available to the agent in your next conversation.
Manual Install via creor.json
You can also install servers by adding them to your project's creor.json file. This is useful for team-wide configurations that should be version-controlled.
Tip
Managing Servers
Manage installed servers from Dashboard > Marketplace > Installed or from the IDE settings.
Server Status
| Status | Meaning | Action |
|---|---|---|
| Running | Server is active and tools are available | No action needed. |
| Stopped | Server is installed but not running | Click "Start" to activate. |
| Error | Server failed to start or crashed | Check logs. Common causes: missing config, port conflict. |
| Update available | A newer version is published | Click "Update" to install the latest version. |
Configuration
Update a server's configuration from its settings page. Changes take effect after restarting the server.
Uninstalling
- Click the three-dot menu on the installed server.
- Select "Uninstall".
- Confirm the removal. The server process is stopped and its tools are no longer available.
- Configuration data is retained for 30 days in case you reinstall.
Featured Servers
These are some of the most popular MCP servers available in the Marketplace.
| Server | Tools | Description |
|---|---|---|
| Supabase | execute_sql, apply_migration, list_tables, deploy_edge_function | Full Supabase management from the agent. |
| GitHub | create_issue, create_pr, list_repos, search_code | GitHub operations without leaving the editor. |
| Slack | send_message, list_channels, search_messages | Send Slack messages and search channel history. |
| Notion | search, create_page, update_page, get_comments | Read and write Notion pages and databases. |
| PostgreSQL | query, list_tables, describe_table, explain | Direct PostgreSQL database access. |
| Sentry | list_issues, get_issue, resolve_issue | View and manage Sentry error reports. |
| Figma | get_file, get_components, export_images | Read Figma designs for implementation reference. |
| Linear | list_issues, create_issue, update_issue | Manage Linear project issues. |
Publishing
Publish your own MCP servers to the Marketplace to share tools with the Creor community.
Requirements
- Server must implement the MCP protocol (see docs.creor.ai/mcp for the spec).
- Must include a manifest file (mcp-server.json) with name, description, tools, and configuration schema.
- Must be published as an npm package, Docker image, or standalone binary.
- Must include a README with setup instructions and tool documentation.
- Source code link is required. Closed-source servers are labeled accordingly.
Submission Process
- Go to Dashboard > Marketplace > Publish.
- Enter the package name or repository URL.
- The system validates the manifest and tests tool definitions.
- Submit for review. The Creor team reviews for quality and security (typically 1-3 business days).
- Once approved, the server appears in the Marketplace.