Connect your AI tools to ArtifactBridge

Browser assistants

These run in a browser tab and reach ArtifactBridge from the vendor's cloud, so there is nothing to install. Most ask for the MCP server URL, then sign you in; ChatGPT uses its official app instead. Several need an administrator to add the connector, noted in each section. Your workspace's app permissions still apply.

Self-hosted or on another deployment? Copy that deployment's endpoint from Settings → Connect AI tools instead.

https://app.artifactbridge.com/mcp

https://app.artifactbridge.com/mcp

https://app.artifactbridge.com/mcp

https://app.artifactbridge.com/mcp

https://app.artifactbridge.com/mcp

https://app.artifactbridge.com/mcp

Local tools

These run on your computer. Add the server from the tool's command line or config file, then sign in; no desktop app is needed. Each command below carries the endpoint. Add and sign-in are separate steps, so copy them one at a time.

Or let the desktop app do it: it finds the supported tools on this computer (Claude Code, Codex, Grok, OpenCode, and Hermes), sets each one up after you review the plan, and stays in your menubar. If you have it, skip to Did it work?

Any other MCP client

Using a tool that is not listed above? Most MCP clients read a mcpServers map. Paste this config; it names the same endpoint and carries no token, and the client signs you in on first connect. Change the name or URL if your deployment is self-hosted.

{
  "mcpServers": {
    "artifact-bridge": {
      "type": "http",
      "url": "https://app.artifactbridge.com/mcp"
    }
  }
}

Connect an external A2A service

A workspace member can register an external agent that speaks the A2A protocol over HTTPS (JSON-RPC binding) in Settings → Agent Sharing (the in-product name for the feature the API and configuration keys call Agent Gateway). ArtifactBridge validates the service's Agent Card and endpoint before it publishes the service, keeps a sanitized copy of the card, and issues the service one credential. The service uses that credential only to obtain short-lived access for a specific delegated task. If the service needs its own bearer token, ArtifactBridge stores it encrypted and never shows it again.

Register a service

1. Open Settings → Agent SharingSelect Register service.
2. Describe the serviceEnter a service name, the Agent Card URL (HTTPS on a public host), the authentication the endpoint needs, and the concurrency limit. The default is 1; extra requests queue.
3. Validate and publishSelect Validate & publish. If the card is unreachable or requires an unsupported feature, the URL field shows the reason and you can retry.
4. Hand the credential to the runtimeCopy the service credential and the bootstrap URL from the one-time reveal and give them to the runtime that operates the service. The credential is shown once. The runtime presents it at the bootstrap URL, with the delegation locator it receives in each A2A request, to obtain a short-lived credential scoped to that one task.

Manage a service

• Every member sees the catalog with workspace-level counts (limit, running, queued). Private Room titles, briefs, and document contents are never shown on this page.
• ArtifactBridge re-reads each service's Agent Card on a schedule. Descriptive changes (name, description, skills) are applied automatically and appear in the change history. A changed endpoint or security requirement is never applied automatically: the service shows Refresh stale with the cached card in use until the maintainer confirms the change. A service that stops answering shows Unreachable; no new work is sent to it until a later check passes, and queued work waits.
• The registering maintainer or a workspace admin can edit the description and concurrency, refresh the card, confirm a changed endpoint or token (running delegations keep the connection they started on), rotate the credential, and disable the service. Other members see View only.
• Disabling a service blocks new work, cancels queued work, requests cancellation of running work, and posts a system update in each affected Room. Remote cancellation stays requested until the service responds.
• Members find published services through their connected agent and delegate tasks from Rooms. See Delegate work to an external service.

Server setup

Agent Sharing needs two server settings: PUBLIC_BASE_URL, so the bootstrap and tools URLs given to services are absolute, and AGENT_GATEWAY_SECRET_KEY, a base64 32-byte key that encrypts stored service tokens. Without the key, registering a service that needs a token is refused with a clear message instead of storing the token in plain text.

Did it work?

1. Start a new conversation in the toolA conversation that was open before you connected does not see the server.
2. Send the check promptCopy it below.
3. Read the replyIt names the workspace you chose at sign-in and lists the documents you can open, or reports that the workspace has none yet. Either reply names the workspace, so it confirms the whole path works, even in a brand-new, empty workspace with no documents.

Read the current ArtifactBridge workspace name and list the documents I can access.

Manage access

Open Settings → Members & access → Access to see every connected tool and revoke one. Revoke the affected access if a device is lost or a tool should no longer connect. Removing a Skill does not revoke a credential. A second tool does not gain broader permission because the first one can read an item; access follows the identity that signed in.

Running without a browser, for example in CI? Use a workspace API token from the same page instead of sign-in, and inject it from a secret store. Never paste a token into a chat.