---
title: "Connect DevCycle to PractiTest - APIANT.ai"
description: "When \"New Feature Created\" fires in DevCycle, your agent runs \"Add Issue\" in PractiTest."
canonical: "https://apiant.ai/connect/devcycle-to-practitest"
---

# Connect DevCycle to PractiTest

When **New Feature Created** fires in [DevCycle](https://apiant.ai/connections/devcycle), your agent runs **Add Issue** in [PractiTest](https://apiant.ai/connections/practitest). Describe the whole flow and it is built, tested on every scenario and kept running.

DevCycle **1** trigger DevCycle **12** actions PractiTest **22** actions

What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.

## What do you want DevCycle and PractiTest to do together?

Give your AI client this address.

`https://mcp.apiant.ai`

One 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.ai`

Start Claude Code there, approve the server, and sign in in the browser page it opens.

[Claude Code guide (opens in a new tab)](https://apiant.ai/docs/mcp/claude-code)

### 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)](https://apiant.ai/docs/mcp)

### 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)](https://apiant.ai/docs/mcp)

### Zed

Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### 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)](https://apiant.ai/docs/mcp)

### 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)](https://apiant.ai/docs/mcp)

Example flows

## What DevCycle can start in PractiTest

- When **New Feature Created** in DevCycle then **Add Issue** in PractiTest
- When **New Feature Created** in DevCycle then **Update Issue** in PractiTest

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 PractiTest

## Triggers and actions 1 trigger · 34 actions

- Trigger

**New Feature Created**

Triggers when a new feature is created in a DevCycle project.

- Action

**Add feature**

Creates a new feature flag in a DevCycle project, with optional variations, variables and per-environment targeting.

- Action

**Add project**

Creates a new project in your DevCycle organization.

- Action

**Add variable**

Creates a new variable in a DevCycle project, optionally attached to a feature.

- Action

**Delete feature**

Deletes a DevCycle feature from a project, optionally deleting its associated variables too.

- Action

**Get feature**

Returns a DevCycle feature, including its variations, variables and environment targeting configurations.

- Action

**List environments**

Returns the environments (development, staging, production, etc.) in a DevCycle project, including their keys and SDK keys.

- Action

**List features**

Returns the features in a DevCycle project, optionally filtered by type, status, staleness, keys or a search term.

- Action

**List projects**

Returns the DevCycle projects the connected account has permission to view.

- Action

**List variables**

Returns the variables in a DevCycle project, optionally filtered by feature, type, status or search text.

- Action

**Update EdgeDB**

Turns EdgeDB on or off for a DevCycle project and returns the updated project.

- Action

**Update feature**

Updates an existing feature in a DevCycle project, such as its name, description, type, tags, variations, variables or environment targeting.

- Action

**Update variable**

Updates an existing variable in a DevCycle project, such as its name, description, type, tags or key.

- Action

**Add Instance**

Adds a test to a test set in a PractiTest project as a new instance.

- Action

**Add Issue**

Creates an issue in a PractiTest project.

- Action

**Add Test**

Create a new test case in a project.

- Action

**Create a Run**

Uploads a new run result for a test instance in a PractiTest project — typically automated test results from CI, or a manual run with step results.

- Action

**Create Requirement**

Creates a new requirement.

- Action

**Delete Issue**

Deletes a specific issue from a PractiTest project.

- Action

**Delete Requirement**

Deletes a specific requirement from a PractiTest project.

- Action

**Delete Test**

Deletes a specific test from a PractiTest project.

- Action

**Get Issue**

Retrieves a single issue from a PractiTest project, including its attributes and custom field values.

- Action

**Get Requirement**

Retrieves a single requirement from a PractiTest project by its system id.

- Action

**Get Run**

Retrieve a single test run by id.

- Action

**Get Test**

Retrieve a single test by id.

- Action

**List Instances**

Lists the test instances in a PractiTest project, optionally filtered by test set, test, name or display id.

- Action

**List Issues**

Lists the issues in a PractiTest project, optionally narrowed by filter, display ids, title or PTQL query.

- Action

**List Projects**

Lists the projects in the PractiTest account. With a personal API token, only the projects that user can access are returned.

- Action

**List Requirements**

Returns all requirements in a PractiTest project, optionally narrowed by filter, display ids, name or PTQL query.

- Action

**List Runs**

List all test runs in a project.

- Action

**List Tests**

List all tests in a project.

- Action

**List Users**

Lists the users in the PractiTest account, optionally filtered by email address or to active users only.

- Action

**Update Issue**

Updates an existing issue in a PractiTest project. Only the fields you fill in are changed.

- Action

**Update Requirement**

Update a requirement's fields.

- Action

**Update Test**

Updates a specific test in a PractiTest project. Only the fields you fill in are changed.

## Each app on its own

- [ **DevCycle** DevCycle is a feature flagging platform that's easy to use, scalable and lightning fast.](https://apiant.ai/connections/devcycle)
- [ **PractiTest** PractiTest QA and test management solution helps users to manage the development and testing process, with...](https://apiant.ai/connections/practitest)

Reviews

## What our customers say

## More from DevCycle

- [ **DevCycle to HubSpot** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/devcycle-to-hubspot)
- [ **DevCycle to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/devcycle-to-salesforce)
- [ **DevCycle to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/devcycle-to-slack)
- [ **DevCycle to Google Sheets** Google Sheets](https://apiant.ai/connect/devcycle-to-google-sheets)
- [ **DevCycle to Gmail** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/devcycle-to-gmail)
- [ **DevCycle to Google Calendar** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/devcycle-to-google-calendar)

## More into PractiTest

- [ **Salesforce to PractiTest** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-practitest)
- [ **HubSpot to PractiTest** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-practitest)
- [ **Slack to PractiTest** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-practitest)
- [ **Google Sheets to PractiTest** Google Sheets](https://apiant.ai/connect/google-sheets-to-practitest)
- [ **Gmail to PractiTest** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-practitest)
- [ **Google Calendar to PractiTest** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-practitest)

Questions

## DevCycle and PractiTest, 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 PractiTest when something happens in DevCycle?

Any of PractiTest's 22 actions, including Create a Run, Create Requirement, Update Issue and Update Requirement. Your agent maps the data both ways and tests every scenario before it ships.

###

### Can it also run from PractiTest to DevCycle?

PractiTest has no triggers in the catalog today, so automations start in DevCycle. If you need the other direction, ask: your agent reads PractiTest's API documentation and adds it.

###

### Do I have to build a connector for DevCycle or PractiTest?

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 PractiTest 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.
