Skip to main content

Integration Accounts + MCP Marketplace

This is the operational bridge from private credentials to publicly consumable tooling.

Routes

  • /integration-accounts (authenticated)
  • /mcp/marketplace
  • /mcp/marketplace/:itemId
  • /mcp/publish (authenticated)

Integration Account Console

The console supports:

  • account CRUD through typed ThorAPI services
  • template-driven account setup
  • module-aware binding workflows
  • service/category search and filtering
  • status handling with IntegrationAccountStatusEnum
  • SageChat-driven prefill via UI-intent event payloads

The key goal: keep credentials and account metadata explicit, reusable, and attached to the right execution modules.

MCP Marketplace Surfaces

Marketplace UI includes:

  • trending/recommended discovery lanes
  • category- and trust-signal visibility
  • listing detail pages
  • publish form (McpMarketplaceItemForm) for new entries

This creates a clean handoff from internal automations to externally discoverable services.

  1. Create/verify integration accounts in /integration-accounts.
  2. Bind them to workflows/modules in Workflow Studio.
  3. Package and publish reusable capability in /mcp/publish.
  4. Validate discoverability and metadata quality in /mcp/marketplace.

Quality Bar Before Publish

  • credentials verified
  • error behavior documented
  • input/output contract clear
  • category/tags accurate
  • ownership and maintenance path defined