Operate Customer Workspaces Through the Hosted MCP

Use one remote endpoint to manage a customer workspace without installing a SchemaBounce binary: https://mcp.schemabounce.com/mcp. It is served by the SchemaBounce core API and uses browser OAuth. Workspace membership, consented scopes, role permissions, rate limits and audit events apply to every tool call.

This page is for operating a workspace the client has granted you. It does not publish marketplace listings. For that, see Bring your n8n work.

Connect an MCP client

codex mcp add schemabounce --url https://mcp.schemabounce.com/mcp
codex mcp login schemabounce

1. Choose the customer workspace during browser authorization.
2. Approve only the read and write scopes the engagement needs.
3. List environments and workflows before changing anything, to confirm the workspace boundary.
4. Keep the remote hosted entry as the production connection. The local stdio binary is for compatibility and development.

Import and operate an inbound sales workflow

The same session can complete customer setup and collect proof.

1. Call sb_automation with workflow_import_analyze and the unchanged n8n JSON. Review the compatibility and credential report before creating anything.
2. Call sb_automation with workflow_import to create the native draft. It does not deploy or run it.
3. Call sb_source with public_form_create to create the CAPTCHA-protected lead endpoint.
4. Call sb_sink with create, sink_type agent_datastore and a config of entity_type leads and primary_key_field id.
5. Call sb_route with create, source_type webhook, source_config.source_id set to the public-form source ID, and the agent datastore sink binding.
6. Call sb_access to create and validate the client-owned HubSpot connection, grant it to the selected workflow agent and restrict its tool allowlist.
7. Update the imported HubSpot action with that agent, deploy the workflow and submit a non-production lead.
8. Use sb_source webhook_events for the ingress receipt. Use sb_automation workflow_runs and workflow_run_get for step, token, cost, credit and reconciliation details.

An imported lead webhook becomes a data trigger for new leads. A node that references HubSpot becomes a workspace-owned connection requirement. The importer never copies credential values.

Two MCP surfaces

Surface	Used by	For
Hosted platform MCP	Builders and operators	Managing workspaces, sources, routes, workflows, agents and customer-owned connections
Agent live tools	Deployed agents	Calling HubSpot, GitHub, Slack and other external systems while a workflow runs

Related

• Clients, handover and support
• Maintenance subscriptions