Integration
Connect DevCycle and Parseur
When New Feature Created fires in DevCycle, your agent runs Create Document in Parseur, or New Document Export Failed in Parseur to Add project in DevCycle. Describe the whole flow 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 DevCycle and Parseur 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 DevCycle and Parseur can do together
From DevCycle to Parseur
When New Feature Created in DevCycle
then Create Document in Parseur
When New Feature Created in DevCycle
then Create Document From File in Parseur
From Parseur to DevCycle
When New Document Export Failed in Parseur
then Add project in DevCycle
When New Document Not Processed in Parseur
then Add feature in DevCycle
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 DevCycle and Parseur
Triggers and actions 7 triggers · 22 actions
Trigger
New Feature CreatedTriggers when a new feature is created in a DevCycle project.
Action
Add featureCreates a new feature flag in a DevCycle project, with optional variations, variables and per-environment targeting.
Action
Add projectCreates a new project in your DevCycle organization.
Action
Add variableCreates a new variable in a DevCycle project, optionally attached to a feature.
Action
Delete featureDeletes a DevCycle feature from a project, optionally deleting its associated variables too.
Action
Get featureReturns a DevCycle feature, including its variations, variables and environment targeting configurations.
Action
List environmentsReturns the environments (development, staging, production, etc.) in a DevCycle project, including their keys and SDK keys.
Action
List featuresReturns the features in a DevCycle project, optionally filtered by type, status, staleness, keys or a search term.
Action
List projectsReturns the DevCycle projects the connected account has permission to view.
Action
List variablesReturns the variables in a DevCycle project, optionally filtered by feature, type, status or search text.
Action
Update EdgeDBTurns EdgeDB on or off for a DevCycle project and returns the updated project.
Action
Update featureUpdates an existing feature in a DevCycle project, such as its name, description, type, tags, variations, variables or environment targeting.
Action
Update variableUpdates an existing variable in a DevCycle project, such as its name, description, type, tags or key.
Trigger
New Document Export FailedTriggered when Parseur fails to export a document to its destination.
Trigger
New Document Not ProcessedTriggered when Parseur receives a document it cannot extract data from, so you can follow it up.
Trigger
New Document ProcessedTriggered when Parseur finishes extracting data from a document, with the extracted fields.
Trigger
New Document Processed (With List Items)Triggered when Parseur finishes extracting data from a document, including any table or list fields it found (line items, rows).
Trigger
New MailboxTriggers when a new mailbox is created in your Parseur account. Returns the mailbox's name, email prefix, AI engine and document counts.
Trigger
New Table Field ProcessedTriggers once for every row of a table or list field when Parseur finishes processing a document. Returns the row's values along with the document and mailbox it came from.
Action
Create DocumentSends text or HTML content to a Parseur mailbox as a new document, so Parseur can extract its data. Returns the new document's ID.
Action
Create Document From FileUploads a file (PDF, DOCX, image and so on) to a Parseur mailbox as a new document, so Parseur can extract its data. Returns the new document's ID.
Action
Delete DocumentDeletes a document from Parseur by its ID.
Action
Delete MailboxDeletes a Parseur mailbox and everything in it. This cannot be undone.
Action
Get DocumentReturns one document from Parseur by its ID, including its processing status and the data Parseur extracted from it.
Action
Get MailboxReturns one Parseur mailbox by its ID, with its email address, document counts and settings.
Action
List DocumentsReturns the documents in Parseur, optionally narrowed to one mailbox or one processing status.
Action
List MailboxesReturns the mailboxes in your Parseur account, with the email address to send documents to and how many documents each holds.
Action
Reprocess DocumentSends an existing document back through parsing, for example after you update its template. Returns the document's ID, name and processing status.
Action
Update MailboxUpdates a Parseur mailbox's settings. Only the values you supply are changed — anything you leave blank keeps its current setting.
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 DevCycle
DevCycle to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
DevCycle to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
DevCycle to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
DevCycle to Google SheetsGoogle Sheets
DevCycle to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
DevCycle to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Parseur
HubSpot to ParseurHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to ParseurGoogle Sheets
Gmail to ParseurGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to ParseurGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to ParseurGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Mailchimp to ParseurMailchimp marketing automation and email platform.
Questions
DevCycle and Parseur, answered
What can start an automation from DevCycle?
Any of DevCycle's 1 trigger in the catalog, including New Feature Created. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Parseur when something happens in DevCycle?
Any of Parseur's 10 actions, including Create Document, Create Document From File, Update Mailbox and Get Document. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Parseur to DevCycle?
Yes. When something happens in Parseur, your agent can act in DevCycle too. This page covers both directions: Parseur's triggers and DevCycle's actions are listed here as well.
Do I have to build a connector for DevCycle or Parseur?
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 DevCycle and Parseur 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.