Build solutions, not workarounds.
What do you want Copper 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 Copper can start in Spike.sh
When New Activity in Copper
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 Copper and Spike.sh
Triggers and actions 17 triggers · 47 actions
- New Activity
Triggers when a new activity is created.
- New Company
Triggers when a new Company is created in Copper.
- New Lead
Triggers when a Lead is created in Copper.
- New Opportunity
Triggers when an Opportunity is created in Copper.
- New Person
Triggers when a new Person is created in Copper.
- New Project
Triggers when a new Project is created in Copper.
- New Task
Triggers when a new Task is created in Copper.
- Updated Company
Triggers when a Person's Company is changed.
- Updated Contact Type
Triggers when a Person's Contact Type is changed.
- Updated Lead
Triggers when a Lead is changed.
- Updated Lead Status
Triggers when a Lead's status is changed.
- Updated Opportunity
Triggers when an Opportunity is changed.
- Updated Opportunity Stage
Triggers when an Opportunity's stage is changed.
- Updated Opportunity Status
Triggers when an Opportunity's status is changed.
- Updated Person
Triggers when a Person is changed.
- Updated Project
Triggers when a Project is changed.
- Updated Task
Triggers when a Task is changed.
- Associate to Project
This Action allows you to relate an existing Project to and existing CRM object; both objects have to exist before you run this Action. This Action expects two ID's for input: the ID of the CRM record you want to relate to and the Project ID you want to relate it with. This Action was designed to be used in multi-step Zaps, where you already have a Project ID and an related record ID (e.g. a Person) from previous steps.
- Create Activity
Logs a new Activity on a Person, Company, Opportunity, or Lead.
- Create Company
Creates a new Company.
- Create Lead
Creates a new Lead.
- Create Opportunity
Creates a new Opportunity.
- Create Person
Creates a new Person.
- Create Project
Creates a new Project.
- Create Task
Creates a new Task.
- Create/Update Company
Creates or Updates a Company depending on the match criteria.
- Create/Update Lead
Creates or Updates a Lead depending on the match criteria.
- Create/Update Opportunity
Creates or Updates an Opportunity based off of a match criteria.
- Create/Update Person
Creates or Updates a Person depending on the match criteria.
- Create/Update Project
Creates or Updates a Project depending on the match criteria.
- Search for a Company
Searches for an existing company in Copper.
- Search for an Activity
Searches for an existing activity in Copper.
- Search for a Opportunity
Searches for an existing opportunity in Copper.
- Search for a Person
Searches for an existing person in Copper.
- Search for a Project
Searches for an existing project in Copper.
- Update Company
Updates a Company depending on the match criteria.
- Update Opportunity
Updates an Opportunity based off of a match criteria.
- Update Person
Updates a Person depending on the match criteria.
- Update Project
Updates a Project depending on the match criteria.
- 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 Copper
Copper to LeadSimpleLeadSimple is the CRM that property management and real estate companies use to scale and grow.
Copper to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Copper to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Copper to Google SheetsGoogle Sheets
Copper to Google DriveGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Copper to StripeStripe is a payment processing platform for online businesses.
More into Spike.sh
Slack to Spike.shSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
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
Copper and Spike.sh, answered
What can start an automation from Copper?
Any of Copper's 17 triggers in the catalog, including New Activity, New Company, New Lead and New Opportunity. 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 Copper?
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 Copper?
Spike.sh has no triggers in the catalog today, so automations start in Copper. 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 Copper 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.