Integration

Connect TestMonitor to DeskTime

When New Issue fires in TestMonitor, your agent runs Create Project in DeskTime. 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 TestMonitor and DeskTime to do together?

Ask the assistant

You'll sign in before anything runs. What you typed comes with you.

Examples

Pick one to fill the box, then change anything: the steps, the wording, even the apps. Go as long as you like.

Connect your AI client

Give your AI client this address.

https://mcp.apiant.ai

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)
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)

TestMonitor tracks what your testers find; DeskTime records the hours behind it. Connecting them means a new issue, test case, test run or test result in TestMonitor can check the DeskTime project list and open a matching project or task for time tracking, and note back in TestMonitor where the work should be logged.

Example flows

What TestMonitor can start in DeskTime

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 TestMonitor and DeskTime

Triggers and actions 4 triggers · 19 actions

Each app on its own

Reviews

What our customers say

More from TestMonitor

More into DeskTime

Questions

TestMonitor and DeskTime, answered

Can the agent avoid creating the same DeskTime project twice?

Yes. It can run List Projects in DeskTime first and only use Create Project when nothing matches the TestMonitor project or test run name. The agent tests every scenario, including the case where the project already exists.

Can anything in DeskTime start an automation in TestMonitor?

No, DeskTime offers actions only, so every automation here starts from TestMonitor with a new issue, test case, test run or test result. From there the agent can create projects in DeskTime or read the existing project list.

What can start an automation from TestMonitor?

Any of TestMonitor's 4 triggers in the catalog, including New Issue, New test case, New Test Result and New test run. Describe the moment in plain language and your agent picks the right one.

What can your agent do in DeskTime when something happens in TestMonitor?

Any of DeskTime's 2 actions, including Create Project and List Projects. Your agent maps the data both ways and tests every scenario before it ships.

Can it also run from DeskTime to TestMonitor?

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

Do I have to build a connector for TestMonitor or DeskTime?

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.