Conduit MCP server
Conduit is an AI integration platform for MSPs, built by WYRE AI. It connects ChatGPT, Claude, and Cursor to your PSA, RMM, documentation, and security tools, with admin controls.
Conduit is a hosted gateway. You do not install it. You point your AI client at one MCP endpoint, sign in with your Conduit organization login, and the vendor tools your organization has connected appear in that client.
This page is the public reference for Conduit’s own MCP server, https://conduit.wyre.ai/v1/mcp. Use it when connecting a client, reviewing the gateway tools, or evaluating Conduit for an AI app or connectors directory. More client setup detail lives in Connecting an AI client.
Pricing
Section titled “Pricing”Conduit is one flat plan at $39 per seat per month, with every feature included. There is no organization base fee, and no per-call metering.
- Human seats bill from the first seat, at $39 per month.
- The first two AI agent (service-client) seats are included. Additional agent seats are $39 per month.
- New organizations start with a 14-day free trial of the full platform.
- Annual billing is $33.15 per seat per month, a 15 percent savings.
See Pricing and Billing & Plans.
Connecting in Claude, ChatGPT, and Cursor
Section titled “Connecting in Claude, ChatGPT, and Cursor”For new setups, use this endpoint:
https://conduit.wyre.ai/v1/mcpThat /v1/mcp path is the unified endpoint. It exposes every vendor your organization has connected, behind one URL. Existing clients already configured against https://mcp.wyre.ai/v1/mcp continue to work (same gateway, same auth, no migration needed). Older per-vendor endpoints (/v1/{vendor}/mcp) are deprecated.
Australian and UK organizations use their region’s address instead:
- Australia:
https://au.conduit.wyre.ai/v1/mcp - United Kingdom:
https://uk.conduit.wyre.ai/v1/mcp
There is no per-organization slug in the URL. Your organization is selected when you sign in.
Claude
Section titled “Claude”Claude.ai (web) connects as a custom connector. On Free, Pro, and Max, open Customize, then Connectors, then Add custom connector. Name it Conduit, set the MCP server URL to https://conduit.wyre.ai/v1/mcp, and leave advanced or OAuth fields blank. Click Add, then sign in. On Team and Enterprise, an organization owner adds the connector once under Organization settings, then each member clicks Connect and signs in separately. After you are authorized, toggle Conduit on in a conversation from the + menu, under Connectors. Custom connectors are available on Free (limited to 1 custom connector), Pro, Max, Team, and Enterprise.
Claude Desktop on Pro, Max, Team, and Enterprise can use native Custom Connectors the same way: + next to the message input, Connectors, Manage connectors, Add custom connector, URL https://conduit.wyre.ai/v1/mcp, leave request headers empty, then sign in. On the Free plan, or if native connectors are not available, use the mcp-remote bridge described in Connecting an AI client.
Claude Code connects to the remote server directly:
claude mcp add --transport http conduit https://conduit.wyre.ai/v1/mcpThe --transport http flag must come before the server name. To use Conduit across every project, add --scope user. On first use, Claude Code opens a browser for sign-in.
ChatGPT
Section titled “ChatGPT”ChatGPT connects to Conduit as a custom MCP server, which ChatGPT adds as a plugin. The labels below follow OpenAI’s own help docs. ChatGPT’s interface changes often, so if a label differs, use OpenAI’s current article, Connecting custom MCP servers in ChatGPT.
Which ChatGPT plans can connect. According to OpenAI:
- Business and Enterprise/Edu: custom MCP server connections and full MCP support, including write and modify actions. On Business, only workspace admins and owners can create and publish plugins for custom MCP servers. On Enterprise/Edu, admins and owners can create connections, and admins can use role-based access control to grant the Create plugins with MCPs permission to selected members. Only admins and owners can publish for the workspace.
- Pro: can connect custom MCP servers with read/fetch permissions. Full MCP is limited to Business and Enterprise/Edu.
- Custom MCP servers are connected on ChatGPT web only, not mobile.
Add Conduit. In the current Plugins experience, you don’t need to turn on Developer Mode first.
- In ChatGPT on the web, go to Plugins.
- Select the plus button, then select Add custom MCP server.
- Enter a name, such as
Conduit, and optionally a description. - Under Connection, enter the server URL:
https://conduit.wyre.ai/v1/mcp. - Configure authentication: choose OAuth. Conduit supports dynamic client registration, so you don’t need to enter a client ID or secret. Do not paste an API key.
- Review the risk warning and select the I understand and want to continue checkbox.
- Select Create as a plugin, then review the discovered tools and metadata.
- When ChatGPT asks you to authorize, a Conduit sign-in window opens. Sign in with your Conduit organization login (email and password, or Microsoft / Entra ID) and allow access.
- Install the resulting plugin. It appears in your personal plugins or in the workspace where you created it.
Use Conduit in a chat. Start a new conversation, type @ in the prompt box, and select the Conduit plugin. App selection applies to the message where you use it, so @mention Conduit again when a follow-up needs new data. ChatGPT treats tools without a readOnlyHint annotation as write actions, and it asks you to confirm write actions before they run.
Make it available to your workspace. On Business and Enterprise/Edu, a workspace admin or owner publishes the connection after testing it. Members then find it under Settings, then Plugins. Enterprise/Edu admins can also choose which groups get access and which actions are allowed. See OpenAI’s article for the publishing steps.
Older ChatGPT workspaces. If your account still uses the legacy custom app setup, go to Apps, then Create, from user settings (admins and owners can also use Workspace settings, then Apps, then Create). Provide the endpoint https://conduit.wyre.ai/v1/mcp, pick OAuth as the authentication mechanism, select Scan Tools, complete the Conduit authorization prompt, and select Create.
Cursor
Section titled “Cursor”Cursor connects to a remote MCP server by URL with OAuth. No bridge is needed.
- Create or open
~/.cursor/mcp.json(available in every project) or.cursor/mcp.json(one project). - Add Conduit under
mcpServers:
{ "mcpServers": { "conduit": { "url": "https://conduit.wyre.ai/v1/mcp" } }}- Save the file and reload Cursor. The first time you use the server, a browser opens for the OAuth sign-in.
You can also add it from Settings, then MCP, then Add new MCP server.
Authentication
Section titled “Authentication”Interactive clients authenticate with OAuth 2.1 and PKCE, through your Conduit organization login. There is no API key to paste.
On first connection, the client registers itself with Conduit (dynamic client registration), a browser window opens, and you sign in with email and password or Microsoft / Entra ID. The token is cached and refreshed automatically, so you sign in once, not on every session.
If a client expects you to paste a bearer token and never opens a sign-in browser, use the mcp-remote bridge described in the connect guide. Unattended agents, which have no browser, connect as a service account with the device-code flow or a static agent key. See Connect an unattended agent.
Most tools you see through Conduit are the vendor tools your organization has connected, such as your PSA, RMM, documentation, and security tools. Which of those you can call depends on your access (see Permissions and admin controls).
Conduit’s MCP server also exposes its own gateway tools. Some are always listed, and others appear only when a feature is turned on for your organization.
| Tool | What it does | Read-only or changes data |
|---|---|---|
conduit__my_access |
Shows your own effective vendor access. With no arguments, you get a per-vendor summary, including vendors you are denied. With a vendor slug, you get the reason for the decision and which of that vendor’s tools you can and cannot call. Always listed. | Read-only |
conduit__audit_log |
Reads your organization’s audit log. Admins and owners only. Choose admin for organizational actions (members, roles, settings) or tool_calls for MCP tool-call history. Always listed; callers without admin or owner access are refused when they call it. |
Read-only |
conduit__list_skills |
Lists Agent Skills available to you, each with a {pack}/{skill} name and a description of when to use it. Listed when skills are enabled. |
Read-only |
conduit__get_skill |
Fetches the full SKILL.md instructions for a skill, by the {pack}/{skill} name returned by conduit__list_skills. Listed when skills are enabled. |
Read-only |
conduit__import_skill |
Imports a skill pack from a GitHub URL. The import is scanned and validated, but it is never turned on automatically. An org admin must enable it afterward (the org owner, for a high-risk skill). Requires the skill-authoring permission. Owners and admins always have it; others need an explicit grant. Listed when skill import is enabled. | Changes data |
Each of these tools declares MCP tool annotations (readOnlyHint, destructiveHint, idempotentHint, and openWorldHint), so clients such as ChatGPT and Claude can tell read-only tools from tools that change data.
Other Conduit tools you may see
Section titled “Other Conduit tools you may see”conduit__submit_support_ticketfiles a support ticket with the WYRE team from your AI client. Any signed-in member can use it when the feature is turned on. It changes data (it creates a ticket). See Filing a support ticket from your AI client.conduit__get_startedappears only when your account has no vendors connected. It points you to connecting a first vendor.conduit__memory_searchandconduit__memory_lookupappear when organization memory is enabled.
Permissions and admin controls
Section titled “Permissions and admin controls”Access is decided the same way for every identity, on every route. See Permissions and Managing access for the full model.
Organization roles. Every organization has owner, admin, billing, and member roles. Owners can manage members and roles, and they bypass vendor and tool access controls. Admins can manage members, vendor connections, teams, access grants, and org settings, and they can export the audit log, but they do not bypass access grants. Billing members manage the subscription and invoices, and for vendor tools they are treated like members. Members can call the vendor tools their effective access permits.
The Access editor. Each connected vendor has an Access editor on its connection card under Connections (/org/catalog). From there you set who can use the vendor and at what level, using grouped Read, Write, and Admin checkboxes (Delete is a display grouping of write tools that delete records; enforcement is still read, write, or admin). You can set a default for Everyone, then add exceptions for a team or a member. The most specific grant wins: a member exception overrides a team exception, which overrides the organization default. A persistent Check a member’s access panel shows the same decision the gateway will make on the next tool call.
Audit Log. Conduit records every MCP tool call and administrative action. Admins and owners can review the log in the dashboard and, with a paid plan that is not suspended, through conduit__audit_log.
Data handling
Section titled “Data handling”WYRE AI’s Privacy Policy explains how Conduit collects, uses, and protects information. In short, as documented there and in Conduit’s security and prompt-capture docs:
- Account information comes from your sign-in, including email, display name, and organization identifier.
- Vendor API credentials are encrypted at rest and used only to proxy your requests.
- Conduit records audit metadata about tool calls, such as who called which tool, when, and with what status. It does not record your prompts, tool arguments, or the data a vendor returns. See Prompt capture & privacy.
- Vendor data is proxied in real time and is not stored beyond the duration of a request, per the Privacy Policy.
Related pages: Security, Subprocessors, and the public Security at Conduit page.
Support
Section titled “Support”Email hello@wyre.ai. It works whether or not you are signed in, and it is the best option for attachments such as screenshots or logs.
While you are signed in, click the chat bubble in the bottom corner of any Conduit dashboard page. If your organization has it turned on, you can also ask a connected AI client to call conduit__submit_support_ticket. See Getting support for details.
Related
Section titled “Related”- Connecting an AI client — step-by-step client setup, including OAuth and unattended agents.
- Supported clients — which AI clients are documented today.
- Managing access — the Access editor for Read, Write, and Admin.
- Permissions — org roles and how tool-call access is decided.
- Security — credential isolation, tenant boundaries, and the audit log.
- Prompt capture & privacy — what Conduit records, and what it never captures.
- Getting support — how to reach the WYRE team.

