Skip to main content

Connect an Orchestrator

A hosted SchemaBounce agent can take work from an external orchestrator while runs, approvals, cost, and context stay in your workspace. Open Agents → Orchestrators in a workspace to set up each connection; this page covers what each card does and where its credentials come from.

Paperclip​

The @schemabounce/paperclip-adapter package runs a SchemaBounce agent as a Paperclip employee.

  1. Open Agents → Orchestrators in the workspace, choose the agent to expose, then select Create adapter config. This creates an agent-scoped service account (a credential limited to that one agent) and reveals a config object once. Copy it immediately; the client secret is not shown again.

  2. Install the adapter package in your Paperclip deployment:

    npm install @schemabounce/paperclip-adapter

  3. Configure a Paperclip agent with adapterType: schemabounce and the copied apiUrl, workspaceId, agentId, clientId, and clientSecret.

  4. Point Paperclip's server-side webhook or polling loop at the adapter. Each heartbeat sends the work item to the SchemaBounce agent, streams progress back into the Paperclip transcript, and reports cost once the run completes.

You can also add the SchemaBounce platform MCP endpoint as a Paperclip generic remote connection using the URL and credential from the MCP section below, so a Paperclip agent can call SchemaBounce tools directly in addition to being run as one.

Linear​

Workspaces with the Linear bridge enabled can route Linear AgentSession activity (issue assignment, comments) to a SchemaBounce agent. Install the bridge from the workspace's Connections page and map Linear teams to agents; unmapped teams fall back to the workspace default agent when one is set. A task created from Linear shows "Linked from Linear" on the task board and its activity streams back into the Linear issue.

A2A​

Every hosted agent has an Agent-to-Agent (A2A) card at a fixed URL scoped to that agent:

{apiUrl}/api/v1/a2a/{workspaceId}/{agentId}/agent-card.json

Give this URL to another A2A-compatible system to let it send tasks to the agent over the standard A2A JSON-RPC methods (message/send, tasks/get, tasks/stream). Authenticate with an API token from Workspace Settings → Service Accounts; a token scoped to one agent can only call that agent's endpoints.

MCP​

SchemaBounce also exposes itself as a remote MCP server, separate from being a worker: connecting an MCP client to the platform lets it operate the workspace directly (create tasks, query schemas, read pipeline state) rather than being assigned work. See SchemaBounce in the MCP Registry for the registry identity, the remote endpoint, and both the browser-OAuth and service-account authentication paths.

Credential handling​

Every credential shown on the Orchestrators page (the Paperclip adapter config, API tokens) is revealed once at creation time and never re-displayed. Store it in a secret manager, not in source control or a shared document. If a credential is lost, revoke it from Workspace Settings → Service Accounts and create a new one.