Build solutions, not workarounds.
What do you want Manus and Spike.sh 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 Manus can start in Spike.sh
When New Task Created in Manus
then Add alert rule in Spike.sh
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 Manus and Spike.sh
Triggers and actions 2 triggers · 41 actions
- New Task Created
Fires when a new Manus task is created (Manus task_created webhook event).
- Stopped Task
Triggers when a task reaches a stopping point, either because it completed successfully or needs user input to proceed.
- Add File
Uploads a file to Manus so it can be attached to a task. Returns the new file's id to use as an attachment when creating or continuing a task.
- Add Project
Creates a new project to group related tasks and apply shared instructions.
- Continue Task (Add a New Prompt)
Sends a follow-up prompt to an existing Manus task so the agent continues working on it, including answering a question the agent asked.
- Create Task
Creates a new task and returns a direct link to it.
- Delete File
Deletes an uploaded file from Manus before its automatic 48-hour expiry.
- Delete Task
Permanently delete a task by its ID. This action cannot be undone.
- Get Available Credits
Returns the Manus credit balance, subscription period and refresh information for the connected account (the team's shared pool for a team sub-account).
- Get current user
Returns the Manus user ID of the account this connection is authenticated as.
- Get File
Retrieves a file's upload status, size, expiration, and (if available) a temporary download URL.
- Get Task
Retrieves a Manus task's status and metadata.
- Get Tasks
Lists tasks in your Manus account, optionally filtered by type, agent, project or the credential that created them.
- List Credit Usage
Lists the account's credit change history (consumption, refunds and grants) per task, newest first.
- List Projects
Lists all projects in the Manus account.
- List Skills
Lists the skills available in your Manus account, optionally including a project's own skills.
- Stop Task
Stops a running Manus task. The task's status changes to stopped; it can be resumed later by sending it a new message.
- Update Task
Updates a Manus task's title, sharing visibility, or whether it appears in the task list.
- Acknowledge incident
Acknowledge one or more Spike.sh incidents by counter id or incident id.
- Add alert rule
Create a new alert routing/automation rule with conditions and actions.
- Add escalation
Creates a new escalation policy for a Spike.sh team, defining who is notified, through which channel, and how long to wait between steps.
- Add integration
Create a new integration for a team (source system that sends alerts into Spike).
- Add on-call
Create a new on-call schedule for a team.
- Add service
Create a new service in a team, with name and description.
- Create Incident
Creates a Spike incident through one of your integrations and sends alerts. The integration decides which service and escalation policy the incident is routed to.
- Delete alert rule
Archives (soft-deletes) a Spike alert rule so it no longer applies to incoming incidents.
- Delete escalation
Archives (soft-deletes) a Spike escalation policy by its ID.
- Escalate incident
Escalates one or more Spike incidents to the next step of their escalation policy.
- Get escalation
Get escalation policy details by id.
- Get incident
Fetch a single incident by counter id.
- Get integration
Fetches an integration by its token, including its name, type, service, escalation settings and webhook URL. An error occurs if the integration is not found.
- Get service
Get a Spike service's details, along with its incidents and open-incident count.
- List alert rules
Lists all alert rules (enabled and disabled) configured for a Spike team.
- List escalations
Lists the escalation policies that belong to a Spike team.
- List incidents
Lists the incidents for a Spike.sh team.
- List on-calls
Lists the on-call schedules for a team.
- List services
Lists the services in a Spike team.
- List teams
Lists every team in your Spike organisation. Use a team's ID from here wherever other Spike actions ask for a team.
- Resolve incident
Resolve one or more incidents by counter id array.
- Update alert rule
Replace an existing Spike alert rule's name, conditions and actions.
- Update escalation
Replaces an existing escalation policy's name, steps and start delay. The whole policy is replaced, so send every step you want to keep.
- Update on-call
Updates an on-call schedule's name and/or moves it to another team. Rotations and layers are not changed by this action.
- Update service
Updates the name and/or description of an existing Spike.sh service.
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 Manus
Manus to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Manus to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Manus to StripeStripe is a payment processing platform for online businesses.
Manus to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Manus to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
Manus to PipedrivePipedrive is a sales CRM and pipeline management tool.
More into Spike.sh
HubSpot to Spike.shHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to Spike.shGoogle Sheets
Gmail to Spike.shGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to Spike.shGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Manus and Spike.sh, answered
What can start an automation from Manus?
Any of Manus's 2 triggers in the catalog, including New Task Created and Stopped Task. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Spike.sh when something happens in Manus?
Any of Spike.sh's 25 actions, including Create Incident, Update alert rule, Update escalation and Update on-call. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Spike.sh to Manus?
Spike.sh has no triggers in the catalog today, so automations start in Manus. If you need the other direction, ask: your agent reads Spike.sh's API documentation and adds it.
Do I have to build a connector for Manus or Spike.sh?
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.