Most of the time, your AI assistant and your test management tool live in completely separate worlds. You're in Claude or Cursor, you want to know something about your test coverage, and you either have to go look it up yourself or paste a wall of data into the chat and hope the AI makes sense of it. The AI is smart but blind — it can't see your TestPlanIt data, so it can't actually help you with it.

The TestPlanIt MCP Server changes that.

Until now, the link between a TestPlanIt test case and a Jira ticket worked one direction at a time. You could click Sync to pull the latest status, or wait for the on-demand refresh. If a developer moved a ticket while you were running a test session, you wouldn't know until you went looking. And on the other side, telling Slack that a regression run failed, or letting a custom service know that a milestone closed, meant writing custom integration code that nobody had time to write.

This release ships webhooks. Issues sync the moment they change in your tracker, badges and lists update live without a page refresh, and TestPlanIt events fan out to Slack or any signed URL automatically.

If you've evaluated a test management tool lately, you've seen this pitch: "Generate automated tests inside the tool." "Codeless automation — no scripting required." "AI-powered test creation."

And honestly? The pitch lands. One system, one login, one place to look. For a small team on a greenfield project, it even works for a while.

But it creates problems that only become obvious once you're deep enough in to care.

TestPlanIt v0.22.0 introduces a dedicated Security page in the admin panel, giving administrators full control over password policy, account lockout rules, and enforcement actions — plus a real-time password strength indicator for end users.

TestPlanIt v0.21.0 adds a third source for AI-powered test case generation: any publicly accessible URL. Point the wizard at a web page, optionally crawl linked pages, and watch test cases stream in as the AI analyzes each page.

TestPlanIt v0.20.0 brings three features that make session-based and exploratory testing faster to set up and easier to share.

TestPlanIt v0.19.0 adds support for self-hosted Git servers — connecting your own Gitea, Forgejo, or Gogs instance as a code repository for AI-powered QuickScript generation.

TestPlanIt v0.18.0 ships Duplicate Detection — two complementary features that help you keep your test suite lean as it grows.

TestPlanIt v0.17.0 ships Copy/Move — select test cases or an entire folder, pick a target project, and transfer them directly. No export file, no import wizard, no field mapping. The cases arrive in the target project with their steps, custom fields, tags, issue links, and attachments intact.

Tags are one of those features that looks great in a demo and gets ignored in practice. The concept is solid: label your test cases, test runs, and sessions by area, type, or risk level so you can filter, group, and report on them meaningfully. The reality is that tagging is a manual chore, it's inconsistent across team members, and it's the first thing to slip when you're under pressure to get tests written and runs scheduled. So most repositories end up with either no tags or a sprawl of half-applied, differently-spelled labels that don't actually help anyone filter anything.

TestPlanIt v0.16.0 introduces Auto Tag — AI-powered tag suggestions that analyze your test cases, test runs, and sessions and propose relevant tags in bulk. Review the suggestions, accept what fits, and move on. Your existing tags are reused when they match; new ones are created when they don't.