get_testcasesLABSCO SUMMARY
The reason this works is what Pie puts inside an issue, not what the endpoint does.
Every issue carries reproduction steps, expected versus observed behaviour with specific assertions, screenshots and DOM snapshots — the context a senior QA engineer would hand you. A coding agent given a generic bug report guesses; given that, it can locate the code and write a targeted fix. Their documented batch pattern is to pull every approved issue and open a separate PR for each, which is only sane because the context per issue is that complete. Note the human gate stays in the loop: you approve issues before anything gets fixed.
What it is
Pie is an autonomous end-to-end QA platform that tests your app like a user. The endpoint is how a coding agent reaches the results — the vendor's own framing is that this is the point of the integration, not a side feature.
What you get
- Test cases — list, create in plain English, run, update, archive, add to a suite, find duplicates, import from CSV
- Issues — review, filter, approve, reject, resolve, and cross-run duplicate analysis
- Results and findings, test runs, discovery triggers, suites and feature groups
- Credentials and scripts for test data, plus app config, health check and reporting
- Admin-only tools sit on top of the regular user surface
Requirements
An X-API-Key header. Passwords are never returned — get_credentials gives back ids, names and usernames only. Full parameter schemas are in their tool reference.
Setup effort
Paste a URL with a key — add the endpoint to your client
USE CASES
01
Fixing one bug
Pull the issue with its repro steps and screenshots, fix, open a PR.
02
Clearing the backlog
Iterate every approved issue, one isolated PR each.
03
Triaging first
Review pending issues, reject the false positives, fix what you approve.
04
Writing a test in English
Create a custom test case by describing it, then run it.
35 tools
Listed in project docs. Your client may show a different list.
create_custom_testcaserun_specific_testcasesupdate_testcasearchive_testcasesunarchive_testcasesadd_testcase_to_suiteget_issuesget_issueapprove_issuesreject_issuesresolve_issuesget_resultsget_findingsapprove_findingsreject_findingscreate_runrun_discoveryget_runscreate_test_suiteget_test_suitesupdate_test_suitedelete_test_suitemanage_key_featuresget_available_iconsget_credentialscreate_credentialget_scriptscreate_scripttrigger_rediscoveryget_step_domsgenerate_tests_on_localstart_test_monitoringget_apphealth_checkBEFORE YOU INSTALL
What to know first
Tools you get
The project says 40; its docs name 35.
Requires
- an MCP client that can reach a remote endpoint
- An API key in the X-API-Key header — nothing works without it
INSTALLATION
Connect your client
Add the endpoint to your client.
Server setup
ENDPOINT URL
https://mcp.pie.incRequirements
- An API key in the X-API-Key header — nothing works without it
