Choose how you want to work
Connect an AI assistant
Use a remote MCP client to explore requirements, delivery work, tests and releases. Authorize draft changes when you need them.
Set up MCP →Use the command line
Read and edit workspace records, plan delivery work, download exports and import from Qualio, Jira and AIO Tests. Start with installation and authentication.
Get started with v9 →Bring your existing work
Upload a Jira CSV, review the mapping and import. AIO and OAuth are optional.
Import Jira files →Keep your source evidence
Import Qualio or portable document exports as drafts with original files and retained previews.
Import documents →The same records and permissions
Both tools use the Valid9 API. Access is checked against your current organization membership and role. An assistant or command-line session cannot grant itself broader access.
| Activity | MCP | CLI | Valid9 app |
|---|---|---|---|
| Read delivery and quality context | Yes | Yes | Yes |
| Prepare requirements, tasks, tests, sprints, draft releases and quality drafts | With write consent | With an eligible role | With an eligible role |
| Plan a sprint: move a backlog task to another team | With write consent | With an eligible role | With an eligible role, on Sprint planning |
| Move a task into a sprint (approving it) or classify a release | — | With an eligible role | With an eligible role |
| Import Jira files (AIO optional) | Review, map and apply retained jobs; no file bytes | Upload, review, map and apply | Guided file import |
| Import Qualio / portable documents | Review and apply retained jobs; no file bytes | Upload, preview and apply | Guided file import |
| Affirm that a stale test run’s evidence still holds, or move a stale draft run | Read whether runs are stale, and the change | Authors and administrators, as themselves | Authors and administrators |
| Attach evidence files to a draft test run | Reads evidence metadata; no file bytes | Authors and administrators | Authors and administrators |
| Correct a completed test run, including adding its evidence | — | The person who performed it, confirmed at the terminal | The person who performed it |
| Sign, complete test runs, decide reviews, approve or publish | — | — | Authorized people |
Complete, correct and retain test runs
In Releases, the green checkmark Complete passed test run completes a saved draft when every step has passed and has an actual result. Hover over or focus an icon for its tooltip. Completion needs no additional reason or signature; the same role, revision and approved test-protocol checks still apply.
Open incomplete, failed or blocked runs in the editor to record and complete them. Completing a failed run preserves the failure: release readiness still requires a current passing rerun or an approved deviation accepting the failure. Completing a run does not approve or publish its release.
The archive-box icon Archive test run asks for a reason and retains the run and its evidence. Select Show archived runs to find the Restore test run icon. Archived runs and published snapshots have no completion shortcut. Archiving cannot hide a failure from release checks.
Run completion remains a personal action in the app, unavailable through CLI or MCP. These compact list controls are part of the companion app update; until it is deployed to your environment, use the run editor and existing Archive button.
Add evidence and correct completed runs
Alpha rollout: adding evidence to a completed run, and the v9 runs evidence and v9 runs correct commands, need the matching app and API update and the next published v9 release. Until then, completed runs can’t gain evidence files.
Attach evidence files to a draft run’s steps in Evidence. Any author or administrator can do this, and the reason is optional. A completed run is never edited, only corrected. The person who performed it can add evidence by correcting it: open the completed run, select Correct this test run, enter the reason (required), then attach the file in Evidence. Archived runs can’t gain evidence.
Files are never replaced or removed; a wrong file still calls for a new run. Adding a file is audited as a correction of the run, before and after. The run’s existing second-person review is no longer current, so the run needs a new review. A published release that cites the run shows it as having corrected evidence; the release’s frozen snapshot is unchanged until Quality corrects the release.
The CLI lists, adds and downloads evidence files, and corrects a step’s recorded result and adds its missing files in one decision: see test-run evidence and corrections. MCP reads evidence metadata but carries no file bytes.
Cite automated CI tests
When a step cites automated tests that ran in CI, link each test at the exact commit that was tested and the CI run or job that passed, and attach a CI evidence report file to the step. See the example.
Find and share records by name
Organizations have permanent slugs such as acme. Requirements, tasks, tests, test runs, releases and CAPAs have permanent references such as REQ-12, TASK-34, TEST-8, TR-19, REL-3 and CAPA-7. Each record type is numbered within its organization; references are not recycled, and an organization’s slug stays the same when its name changes.
Use Copy link in a supported record editor to share a readable address such as /o/acme/REQ-12. Recipients must sign in and have access to that organization. Existing UUID links remain valid. A reference is an address, not a password or a release version name.
The current CLI and MCP server accept these slugs and references, with UUIDs still supported. Choose the organization explicitly in either client.
Search across records by text, native reference or imported Jira/AIO key. Search also covers imported document filenames and supported extracted content; scanned images have no OCR, and incomplete file coverage is reported. Narrow results by type, status, team or module, dates and archived records. See the search examples and limitations.
Before you connect
- Create your Valid9 account and complete authenticator setup.
- Confirm that you can access the intended organization in the app.
- Choose MCP or the CLI and follow its guide. Use separate connections and accounts for staging and production.
These guides cover the current alpha. If your client or command behaves differently, contact hello@valid9.com with the version and error message.