Build solutions, not workarounds.
What do you want COR and Luma to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any 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 COR can start in Luma
When Create Brand in COR
then Add ticket type in Luma
When Create Client in COR
then Add event in Luma
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 COR and Luma
Triggers and actions 12 triggers · 43 actions
Trigger
Create BrandTriggers when a new brand is created in COR.
Trigger
Create ClientTriggers when a new client is created in COR.
Trigger
Create HourTriggers when a new time entry is logged in COR.
Trigger
Create InvoiceTriggers when a new transaction is recorded in COR. COR has no separate invoice record, so this watches all transactions, invoices included; use the type field to tell them apart.
Trigger
Create ProductTriggers when a new product is created in COR.
Trigger
Create ProjectTriggers when a new project is created in COR.
Trigger
Create TaskTriggers when a new task is created in COR. Returns the new task's details.
Trigger
Create UserTriggers when a new user is created in COR.
Trigger
Updated ClientTriggers when an existing client is changed in COR.
Trigger
Updated ProjectTriggers when an existing project is updated in COR.
Trigger
Updated TaskTriggers when a task is changed, such as a new title, status, priority or deadline. Also fires when a new task appears.
Trigger
Updated UserTriggers when a user in COR is created or changed, such as their name, email, role, position or labels.
Action
Add brandCreates a new brand under a client in COR.
Action
Add teamCreates a new team in COR with a name and, optionally, a description and workspace. Returns the team that was created.
Action
Create ClientCreates a new client in COR with its company details and primary contact, and returns the new client's id.
Action
Create FeeCreates a fee for a client in COR, with its name, estimate and work order, and optional details such as dates, status and currency. Returns the new fee.
Action
Create HourLogs a time entry against a task in COR and returns the new entry's id.
Action
Create InvoiceCreates an invoice (a COR transaction) for the given date, total and currency, optionally linked to a client, and returns the new transaction.
Action
Create ProjectCreates a new project for a client in COR and returns the created project.
Action
Create TaskCreates a new task in COR, optionally within a project, and returns the created task.
Action
Delete ProjectDeletes a project in COR by its ID.
Action
Delete taskDeletes a task in COR by its ID.
Action
Find clients by nameReturns the clients whose name matches the specified name.
Action
Find projects by nameReturns the COR projects whose name matches the name you search for, including each project's client, project manager, status and budget details.
Action
Get clientReturns a single COR client by its id, including its business name, contact details, website and description.
Action
Get projectReturns a single COR project by its id, including its client, project manager, dates, status, budget figures and assigned labels. An error occurs if the project is not found.
Action
Get taskReturns a single COR task by its id, including its title, project, deadline, status and priority.
Action
List clientsReturns all clients in the COR account, optionally narrowed by filter criteria.
Action
List feesReturns the fees in the COR account, including each fee's name, estimate, status and dates.
Action
List hoursReturns the time entries logged in the COR account, optionally narrowed by date range, client, project, user, label or team, and sorted as you choose.
Action
List productsReturns all products in the COR account, each with its name, client and brand.
Action
List projectsReturns the company's projects, optionally narrowed by client, team, user, brand, product, dates, status, health or archived state.
Action
List tasksReturns the tasks in your COR account, optionally narrowed by project, project manager, status and other criteria, and sorted the way you choose.
Action
List teamsReturns the teams in the COR workspace, including each team's name and description.
Action
Update ProjectUpdates an existing project in COR, changing only the fields you fill in, and returns the updated project.
Action
Update TaskUpdates an existing task by its id, changing its title, project, description, deadline, status, priority or archived state, and returns the updated task.
Action
Add eventAdds an existing event to your Luma calendar — either a Luma event you manage or an event hosted on another platform. The event is approved right away unless you choose to keep it pending for admin review.
Action
Add guestsAdds one or more guests to a Luma event, optionally assigning ticket types, an approval status, and whether Luma emails them. Returns any guests Luma skipped.
Action
Add hostAdds a host to a Luma event, as a manager or as check-in staff, by email address.
Action
Add ticket typeCreates a new ticket type (free or paid) for a Luma event. Paid ticket types require the calendar to have a connected Stripe account.
Action
Apply contact tagApplies a contact tag to existing contacts on your Luma calendar, identified by user ID or email. Does not create new contacts.
Action
Block contactBlocks a contact on your Luma calendar so they can't follow it or join its events, and stop receiving your invites and newsletters.
Action
Cancel eventCancels a Luma event. The event is permanently deleted, all guests are notified, and paid guests can optionally be refunded.
Action
Create Calendar PersonAdds a person to your Luma calendar as a contact by email, optionally with a name and contact tags, so you can invite them to events and send newsletters.
Action
Get calendarReturns the details of the Luma calendar your connected API key belongs to, including its name, URL, location, social handles and default event settings.
Action
Get eventReturns the details of a Luma event, including its schedule, location, visibility, hosts and, for events you manage, guest counts by status.
Action
Get guestReturns one guest of a Luma event, looked up by guest ID, ticket key, guest key or email, including their approval status, registration answers and tickets.
Action
Import contactsImports contacts into your Luma calendar so you can invite them to events and send them newsletters, optionally tagging them.
Action
List contactsReturns the contacts (people) on your Luma calendar, optionally filtered by a name/email search, tags or membership status.
Action
List eventsReturns the events on your Luma calendar, optionally filtered by date range, submission status, platform and access level.
Action
List guestsReturns the guests who have registered for or been invited to a Luma event, with their approval status, contact details, registration answers and tickets.
Action
List ticket typesReturns every ticket type set up for a Luma event, including its name, price and capacity.
Action
Send invitesSends people an email invite (and an SMS if their phone is linked to Luma) to a Luma event. Returns any invitees who were skipped because they unsubscribed, were removed, or are blocked.
Action
Update eventUpdates an existing Luma event's details, such as its name, time, location, description, capacity, registration settings and page appearance. Fields left blank keep their current values.
Action
Update guest statusChanges a guest's registration status for a Luma event — approve (Going), decline, move back to pending approval, or waitlist — optionally refunding a paid guest and adding a personal note to the notification email.
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 COR
COR to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
COR to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
COR to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
COR to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
COR to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
COR to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Luma
HubSpot to LumaHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to LumaSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to LumaSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to LumaGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to LumaGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to LumaGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
COR and Luma, answered
What can start an automation from COR?
Any of COR's 12 triggers in the catalog, including Create Brand, Create Client, Create Hour and Create Invoice. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Luma when something happens in COR?
Any of Luma's 19 actions, including Create Calendar Person, Send invites, Update event and Update guest status. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Luma to COR?
Luma has no triggers in the catalog today, so automations start in COR. If you need the other direction, ask: your agent reads Luma's API documentation and adds it.
Do I have to build a connector for COR or Luma?
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.
Can my AI client use COR and Luma without building an automation?
Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both.
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.