Skip to main content
The Marketplace is Cloosphere’s own (first-party) catalog of add-on services. Attach document generators (PPT, Word, Excel, HTML) and external SaaS integrations (Google Workspace, Microsoft 365) to your agents to extend their capabilities.
The Marketplace is a separately-priced add-on. Your license must include the Marketplace feature, and an administrator must complete the prerequisite setup.

What is the Marketplace?

The Marketplace has two kinds of services. Depending on the kind, the connection method and where they attach on an agent differ.

Document generators

Capabilities that produce PPT/Word/Excel/HTML documents. Specify palette, template, and format to create multiple capabilities (instances) and attach them to the agent’s Skills section.

External integrations (MCP)

Connect Google Workspace/Microsoft 365 as agent tools. Each user signs in with their own account (SSO), and they attach to the agent’s Marketplace Tools section.

Catalog services

Although the tab is called “Marketplace,” the first screen of Workspace > Marketplace is a list of the connections and capabilities you’ve created. To add a new one, click the + New Connection button at the top right to go to the catalog.

Administrator prerequisites

To use the Marketplace, an administrator must set up the following first. If any step is missing, services won’t appear or won’t work.
1

Register the license

In Admin Panel > Settings > License, register the Marketplace add-on feature key. The Marketplace is a separately-priced feature not included in any plan.
2

Deploy the service containers

Document generators require a code execution (Jupyter) container, and external integrations require each MCP service container. These are sidecar containers deployed separately from Cloosphere.
3

Configure connections

In Admin Panel > Settings > Marketplace, enter each service’s URL, run Test connection, and then Activate.
  • Document generators: enter Jupyter URL + token → enable the code execution engine
  • MCP services: enter the service URL → activate (creates the connection)
4

Grant permissions

In Admin Panel > Users > Groups & Permissions, grant groups the Marketplace Access permission (read/write). The default is None.
Document generators appear disabled in the catalog until the code execution engine is ready (with a “Set up the code execution engine in Admin Panel > Settings > Code Execution” hint). External integrations (MCP) appear in the catalog only after an administrator has configured their URL and connected them.

Creating a document generator

From a single generator (e.g. PPT Generator), you can create multiple document capabilities. For example, you can prepare a “company standard deck” and a “customer proposal deck,” each with different colors and templates.
1

Select a generator from the catalog

In Workspace > Marketplace > + New Connection, click the document-generator card you want.
2

Create the capability

Enter a name, description, and access permission, then save. You go straight to the settings screen.
3

Configure the format

On the settings screen, set colors, template, and format instructions.
Format instructions greatly affect generation quality. Be specific, e.g. “Cover → agenda → key summary → details → conclusion, with no more than 3 bullets per slide.”
The document capability you create also appears in the Workspace > Skills list (because it is internally a skill). Its settings such as colors and template can be edited only in the Marketplace edit screen.

Connecting an external integration (MCP)

Connect Google Workspace/Microsoft 365 as agent tools.
1

Select a service from the catalog

In + New Connection, click the Google Workspace or Microsoft 365 card.
2

Create the connection

Enter a name, description, and access permission to create the connection. The URL is inherited from the value the administrator configured.
3

Configure tools

On the detail screen, click Test Connection to load the available tool list, then select the tools to use.

User SSO authentication

An MCP connection automatically injects each user’s own SSO access token into every call. No separate API key is needed — users simply sign in with the matching provider (Google / Microsoft). That is, tools operate within each user’s own permission scope.

Read / write approval (HITL)

Each tool is classified as read or write.
Click the Classify with AI button in the tool list to auto-classify read/write. It also shows whether the OAuth scope for each category has been granted.

Attaching to an agent

Marketplace services attach in different sections of the agent editor depending on their type.
There is no single “add everything from the marketplace” button. Select document generators in the Skills section and MCP services in the Marketplace Tools section.

Using it in chat

Marketplace services attached to an agent are used automatically during a conversation.
Document generation results appear first as a 📎 Download link above the answer. If you follow up like “make slide 3 bold,” it precisely edits only that part instead of regenerating everything.
Write operations of external integrations (such as sending mail via Google Workspace) request user approval before running.

Access control and licensing


Troubleshooting

The code execution engine (Jupyter) must be ready. Check that the document-generator status in Admin Panel > Settings > Marketplace shows “Reachable.”
The OAuth scope for that category has not been granted. Admin consent or re-login may be required. Check the per-category scope indicators on the detail screen.
It’s blocked if agents are using it. The number of agents using it is shown, and to proceed anyway you go through a force-confirm step.

FAQ

A document-generator capability is internally an executable skill. That’s why it also appears in the Workspace > Skills list and is attached in the agent’s Skills section. The difference is that its settings — colors, template, etc. — are managed in the Marketplace edit screen.
Yes. From one PPT Generator you can create multiple capabilities (instances) with different palettes and templates. Attach each to an agent separately.
They operate only within each user’s permission scope using that user’s SSO token, and write operations go through user approval. No shared API keys are stored.
Documents are generated based on the uploaded template. If you upload a template with your company’s standard format and cover page, documents keep that format and just fill in the content.

Next steps

Skills

Standardize how agents work with reusable instruction playbooks you write yourself

Attach to an agent

Attach document generators and external integrations to your agents