Integration
Connect CRUSH to Meteosource
When something happens in CRUSH, your agent does the next thing in Meteosource. Describe it and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want CRUSH and Meteosource 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 CRUSH can start in Meteosource
When Receive Note in CRUSH
then Find nearest place in Meteosource
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 CRUSH and Meteosource
Triggers and actions 1 trigger · 5 actions
- Receive Note
Triggers when a new note is captured in CRUSH. Returns the note's transcript and the date it was created.
- Create Note
Creates a new note in CRUSH from the transcript text you provide. Returns the id of the note that was created.
- Find nearest place
Find the nearest known place to a given set of coordinates.
- Find places
Search for places matching a free-text query.
- Find places by prefix
Search for places whose name starts with a given prefix.
- Get weather data
Get current, hourly, and daily weather forecast for a place or coordinates.
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 CRUSH
CRUSH to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
CRUSH to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
CRUSH to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
CRUSH to Google SheetsGoogle Sheets
CRUSH to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
CRUSH to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Meteosource
Questions
CRUSH and Meteosource, answered
What can start an automation from CRUSH?
Any of CRUSH's 1 trigger in the catalog, including Receive Note. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Meteosource when something happens in CRUSH?
Any of Meteosource's 4 actions, including Find nearest place, Find places, Find places by prefix and Get weather data. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Meteosource to CRUSH?
Meteosource has no triggers in the catalog today, so automations start in CRUSH. If you need the other direction, ask: your agent reads Meteosource's API documentation and adds it.
Do I have to build a connector for CRUSH or Meteosource?
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.