Build solutions, not workarounds.
What do you want Particle and Railway to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.
Set it up in your client
Claude Code
Run this in the directory you want to work in.
claude mcp add --transport http -s project apiant-ai https://mcp.apiant.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)Claude, web and desktop
Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.
Setup guide (opens in a new tab)Cursor
Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.
Setup guide (opens in a new tab)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)Codex and the ChatGPT desktop app
Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.
Setup guide (opens in a new tab)Any other MCP client
Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.
Setup guide (opens in a new tab)Example flows
What Particle can start in Railway
When New device event (instant) in Particle
then Add domain in Railway
When New device event (instant) in Particle
then Add environment in Railway
Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.
Everything your agent can do with Particle and Railway
Triggers and actions 1 trigger · 21 actions
Trigger
New device event (instant)Fires when a matching device event is published, delivered via a Particle webhook integration.
Action
Execute a logic functionRun a configured Particle Logic function and return its result.
Action
Get ledger instanceRetrieve the current data for a ledger instance (shared cloud/device key-value state).
Action
List devicesList all devices in your account or product fleet.
Action
Publish an eventPublish a custom event to the device cloud so other devices or integrations can subscribe to it.
Action
Set ledger instance dataUpdate the data stored in a ledger instance.
Action
Add domainAdds a Railway-provided or custom domain to a service instance.
Action
Add environmentCreates a new environment in a project.
Action
Add serviceCreates a new service in a project, from a GitHub repo, Docker image, or empty.
Action
Delete deploymentRemoves a deployment from a Railway service's deployment history.
Action
Delete environmentDeletes a Railway environment and all of its deployments.
Action
Get deploymentFetches a deployment by ID.
Action
Get projectFetches a project by ID including its services.
Action
Get serviceFetches a service by ID.
Action
Get variablesFetches variables for a service/environment.
Action
List deploymentsLists the deployments of a Railway service in an environment (up to the 100 most recent).
Action
List domainsReturns the custom domains and Railway-provided domains attached to a service in one environment, with each custom domain's DNS and certificate status.
Action
List environmentsLists all environments for a project.
Action
List projectsLists all projects accessible to the token.
Action
Rollback deploymentRolls a Railway service back to a previous deployment.
Action
Update serviceUpdates a Railway service's name or icon.
Action
Update variablesCreates or updates several variables at once for a Railway service, or the shared variables of an environment.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from Particle
Particle to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Particle to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Particle to Google SheetsGoogle Sheets
Particle to StripeStripe is a payment processing platform for online businesses.
Particle to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Particle to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
More into Railway
HubSpot to RailwayHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to RailwaySalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to RailwaySlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to RailwayGoogle Sheets
Gmail to RailwayGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to RailwayGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Particle and Railway, answered
What can start an automation from Particle?
Any of Particle's 1 trigger in the catalog, including New device event (instant). Describe the moment in plain language and your agent picks the right one.
What can your agent do in Railway when something happens in Particle?
Any of Railway's 16 actions, including Update service, Update variables, Add domain and Add environment. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Railway to Particle?
Railway has no triggers in the catalog today, so automations start in Particle. If you need the other direction, ask: your agent reads Railway's API documentation and adds it.
Do I have to build a connector for Particle or Railway?
No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.
What happens when something fails?
Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.
Is there a free plan?
Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.