Store

What is the Store?

The Store is deco Studio’s built-in marketplace for discovering and installing MCP servers. It aggregates items from multiple registries into a unified browsing experience, so you can find and add new capabilities without leaving the platform.

When you need a capability that isn’t already installed — a Shopify integration, a database connector, an email service — the Store is where you find it.

Registry Sources

The Store pulls from multiple registries — MCP connections that serve catalogs of other MCPs. Three types of registries exist:

Deco Store

The curated official registry. Always enabled. Contains verified, reliable integrations that are tested for compatibility with deco Studio.

This is the best first place to search when looking for common integrations.

Community Registry

A broader catalog with more variety, sourced from the community. Useful when the Deco Store doesn’t have what you need. Expect more variation in quality and maintenance.

Community results load after Deco Store results, so curated items appear first.

Private Registries

Organizations can add custom registry connections for internal MCP servers not published publicly. These are useful for proprietary tools or internal services that your team needs but shouldn’t be shared externally.

Private registries can be enabled or disabled per organization through Store settings.

How Discovery Works

When you browse the Store, deco Studio queries each enabled registry in parallel:

1. Non-community registries load first — Deco Store and private registries get priority
2. Community results load second — appear after all priority results are ready
3. Items are tagged with source metadata — you can see which registry each result comes from
4. Pagination — results load in pages with infinite scroll

Each registry item contains:

• Server metadata: name, description, icon, publisher information
• Transport endpoints: remote URLs (HTTP/SSE/Websocket) and/or package commands (STDIO)
• Authentication requirements: OAuth config, API keys, or no auth
• Tool listings: what capabilities the MCP server exposes
• Verification status: whether the item has been verified by the registry

Installing from the Store

Installing an MCP from the Store creates a Connection. The workflow:

1. Find the item via search or browse
2. Inspect full details — tools exposed, auth requirements, transport options
3. Select transport — prefer HTTP/SSE/Websocket over STDIO for production
4. Create the connection — deco Studio extracts the connection payload from the registry item
5. Verify — test the connection to confirm it’s healthy

Transport Selection

When an MCP server offers multiple transport options:

Managing Store Settings

Store configuration is organization-scoped. You can:

Enable/Disable Registries

Toggle which registries appear in your Store. Each registry can be independently enabled or disabled. Registries not explicitly configured default to enabled.

Block Specific MCPs

Add MCP servers to a blocklist to hide them from your organization’s Store. Useful for:

• Removing MCPs that conflict with internal tools
• Enforcing organizational policy on which integrations are allowed
• Reducing noise from irrelevant items

Evaluating Store Items

When browsing the Store, consider:

Capability fit: Does the MCP server expose the specific tools you need? Check the tool listings, not just the description.

Trust and maintenance: Prefer verified items from the Deco Store when available. For community items, check publisher information and maintenance signals.

Authentication requirements: Note whether the item requires OAuth, API keys, or works without authentication. Some integrations may need admin approval to set up.

Transport options: Items with HTTP endpoints are simpler to deploy than STDIO packages. Check what’s available before installing.

Next Steps