Platform migration
Moving to Conduit
The WYRE MCP Gateway at mcp.wyre.ai is being retired on
30 September 2026. Your organisation, your team,
and your service accounts move to Conduit. This page covers what we do for you, what you
need to do yourself, and by when.
The two addresses that change
| Today | From 30 September | |
|---|---|---|
| Signing in | mcp.wyre.ai | conduit.wyre.ai |
| MCP client URL | mcp.wyre.ai/v1/mcp | conduit.wyre.ai/v1/mcp |
What we migrate for you
No action needed on any of this.
Your organisation
Name, plan, and settings move across. You do not create a new org or a new subscription.
Members and roles
Everyone on your team comes with you, keeping the role they have today. No re-inviting.
Service accounts
Your service clients are recreated on Conduit against the same organisation.
What does not come across
These are the pieces you re-do yourself, once.
Vendor credentials
API keys, tokens, and OAuth grants for Autotask, IT Glue, Huntress, and every other connection are not transferred. You enter them once in Conduit.
MCP client connections
Claude and any other MCP client hold an access token issued by the old gateway. Each connection has to be added again pointing at Conduit.
What you need to do
- 1
Sign in at conduit.wyre.ai
Use the same email address you use today. Your organisation is already there waiting for you, with your team and their roles in place.
Go to Conduit - 2
Re-enter your vendor credentials
Open each connection in Conduit and enter its API key, token, or OAuth login again. We do not transfer credentials between platforms, so this is the one piece of real work in the move. Have your PSA, RMM, and security tool credentials to hand before you start, and set up shared org connections first so your team is not blocked.
- 3
Repoint your MCP clients
In Claude, or wherever you use the gateway, add the connector again using the new URL and complete the sign-in prompt:
https://conduit.wyre.ai/v1/mcpRemove the old
mcp.wyre.aiconnector once the new one is listing tools, so nobody is left calling the platform that is going away. - 4
Update anything running unattended
Service accounts are recreated for you on Conduit, but expect to re-verify their credentials and update the endpoint in whatever runs them — scheduled agents, scripts, or integrations built on the gateway. Check each one actually authenticates against Conduit rather than assuming it carried over.
What happens on 30 September
mcp.wyre.ai starts redirecting to
conduit.wyre.ai, and the old gateway stops serving MCP
traffic.
Do not rely on the redirect.
It is a safety net for browser traffic, not a migration path. Your MCP client holds an
access token issued by the old gateway, and Conduit will not accept it — the connection
has to be added again and re-authorised regardless of where the old URL points. Anything
still calling mcp.wyre.ai/v1/mcp at the cutoff stops
working.
Both platforms run in parallel until then, so there is no forced switchover day. Move when it suits you, verify it works, and leave yourself room before the end of September.
Questions
Do I need a new subscription?
No. Your plan and billing move with your organisation. Nothing to re-purchase, and you are not billed twice during the changeover.
Can I move before 30 September?
Yes, and we would rather you did. Both platforms run side by side until the cutoff, so you can set up Conduit, confirm your connections work, and switch your team over at your own pace.
What happens to my usage history and audit log?
Historical request logs and audit entries stay on the old platform and are not carried into Conduit. If you need a copy for compliance, email us before 30 September and we will export it for you.
Will my automations break?
Anything calling https://mcp.wyre.ai/v1/mcp stops working at the cutoff, so update the URL and re-authenticate before then. Treat this the same as any other endpoint change in your automation stack.
Is Conduit the same product?
Same connections, same MCP tooling, same team. Conduit is where the platform is being developed from here, which is why we are consolidating onto it rather than running two gateways.
Need a hand with the move?
If you have a lot of connections, unattended automations, or a compliance export to sort out, tell us and we will walk it through with you.