Getting started

This guide takes you from signup to a working Conduit organization with one vendor integration connected and an AI client making tool calls through it. Expect 20–40 minutes the first time.

Before you start

You need:

• A login for your organization.
• API credentials for at least one vendor you want to connect (for example a ConnectWise Automate API key pair or a Datto RMM API key and secret).

Note

All steps below are shown against the web UI. Every action also has an API equivalent — see the API reference.

1. Create your organization

1. Visit https://conduit.wyre.ai/signup, enter your business name. If the hosted trial requires a card, add one when prompted, then complete sign-in. There is no charge during the 14-day trial, and you can cancel any time.
2. Conduit provisions your organization using the business name you entered — this is what your team sees on invite emails and consent screens. A free 14-day trial of the full platform starts automatically. See the Billing & Plans guide for the pricing detail.

After creation you land on the dashboard.

2. Invite teammates

Getting Started is where you bring colleagues in — not only later in the MSP onboarding playbook.

1. Open Invite teammates (same surface as /org/invitations).
2. Click Create Invite Link, choose max uses and expiration, then Create.
3. Copy the invitation URL (shown once) and send it to your teammate. When they visit the link and sign in, they join as a member.

The owner can promote a member to admin or billing from /org/members after they join.

3. Connect your first vendor

A vendor connection is Conduit’s adapter to a third-party vendor API (ConnectWise, Datto RMM, IT Glue, and others). Connect it once at the organization level.

1. Go to the Connections page (/org/catalog).
2. Pick the vendor. API-key vendors show a credential form; OAuth vendors (Xero, QuickBooks Online, Calendly) redirect to the vendor for consent.
3. Submit. Conduit encrypts the credential and runs a health check. A green status means the connection is ready.

For credential scopes, rotation, and OAuth specifics, see the vendor connections guide.

4. Connect an AI client

Conduit works with any MCP-compatible client — Claude Desktop, Claude Code, Cursor, Cline, Continue, and Perplexity Computer among them. The examples below use Claude Desktop and Claude Code; see Connecting an AI client and Supported clients for the rest. Point your client at Conduit’s MCP endpoint:

Conduit endpoint

Use https://conduit.wyre.ai/v1/mcp. Existing clients configured against https://mcp.wyre.ai/v1/mcp continue to work without changes (same gateway, same auth — no migration needed).

Claude Desktop (claude_desktop_config.json):

{
  "mcpServers": {
    "conduit": {
      "url": "https://conduit.wyre.ai/v1/mcp"
    }
  }
}

Claude Code:

claude mcp add --transport http conduit https://conduit.wyre.ai/v1/mcp

First use opens a browser for sign-in. After sign-in the JWT is cached and refreshed automatically.

5. Verify the setup

• Make a test tool call from Claude against one of the connected vendors.
• Open the Audit log in the dashboard and confirm the call is recorded with the correct user and vendor.
• Open the vendor health view and confirm every connected vendor shows green.

Frequently asked questions

What is Conduit?

Conduit is a hosted MCP gateway. It connects any tool-calling AI assistant to the vendor MCP servers your organization relies on (RMM, PSA, documentation, security, and more), behind one auditable, permissioned endpoint.

What is an MCP gateway?

An MCP gateway sits between AI assistants and the tools they call. It speaks the Model Context Protocol (a provider-neutral standard for connecting AI to tools) and brokers each tool call — handling authentication, credentials, permissions, and audit — so an AI assistant can use your business systems without each system being wired to each AI client. Conduit is an MCP gateway for your organization: it gives an AI the access and visibility it needs into the business; it is not a workflow-automation tool.

Do I need to install anything to use Conduit?

No. Conduit is a hosted gateway — you connect an AI client to it, you don’t install Conduit itself. Setup is pointing your AI client at your Conduit MCP endpoint and signing in once.

Which AI clients work with Conduit?

Any MCP-capable client. Conduit speaks the standard Model Context Protocol, so Claude Desktop, Claude Code, Cline, Continue, Cursor, and other MCP clients all connect. See Supported clients.

How long does first-time setup take?

About 20–40 minutes the first time — create your organization, connect one vendor, connect an AI client, and make a test tool call.

What do I need before I start?

A login for your organization, API credentials for at least one vendor you want to connect, and a card at hosted signup. The 14-day trial starts automatically with no charge during the trial; you can cancel any time. Self-hosted deployments can skip the card field.

Where to go next

• Vendor connections — connection scopes, rotation, and OAuth specifics.
• API reference — every flow above has an API equivalent.
• Growing your team — inviting teammates, connecting more vendors, and setting access, for your own organization.
• MSP onboarding — the end-to-end discovery, provisioning, and handoff playbook if you’re reselling Conduit to your own customers.