# Project creation API, redesigned PR picker, and custom-field configs > 5 updates: Claude Desktop removed from MCP install options, Create projects via the API, Pass custom key-value data to tests via configs, Redesigned… Source: https://qa.tech/changelog/2026-06-09 --- 5 updates shipped on June 9, 2026. In this release 1. 01[Claude Desktop removed from MCP install options](#2026-06-09-claude-desktop-removed-from-mcp) 2. 02[Create projects via the API](#2026-06-09-create-projects-via-the-api) 3. 03[Pass custom key-value data to tests via configs](#2026-06-09-custom-fields-config-type) 4. 04[Redesigned GitHub and GitLab PR picker in chat](#2026-06-09-redesigned-pr-picker-in-chat) 5. 05[Status badge links now filter to the right test plan](#2026-06-09-status-badge-links-filter-test-plan) 1. Update 01 of 05 ## Claude Desktop removed from MCP install options Claude Desktop recently switched to OAuth-only MCP authentication, which is incompatible with API key configs, so it has been removed from the in-app install options. The Claude Desktop tab is no longer shown under Settings → Integrations → API → MCP clients, and the `--client claude-desktop` example has been removed from the CLI section. Claude Code, Cursor, Codex, and Continue are unaffected – they still use API key–based configs. [\# Direct link](#2026-06-09-claude-desktop-removed-from-mcp) 2. Update 02 of 05 ## Create projects via the API The public API now supports project creation, so you can automate project setup from CI/CD pipelines or provisioning scripts. Send a `POST /v1/projects` request with your project name and settings, and QA.tech will create the project in your organization. This joins the existing endpoints for triggering runs, reading results, and managing configurations – making fully automated project-to-run workflows possible without touching the dashboard. [\# Direct link](#2026-06-09-create-projects-via-the-api) 3. Update 03 of 05 ## Pass custom key-value data to tests via configs A new "Custom Fields" config type lets you supply arbitrary name/value pairs – test credentials, addresses, account numbers – that the agent reads during a run. Go to Settings → Configs, click Add config, and choose the Custom Fields card. Add as many rows as you need; the agent receives the values automatically without any changes to your test steps. Use it for structured data you'd otherwise hardcode into steps or manage separately per environment. Values are shown in plaintext in the config UI. [\# Direct link](#2026-06-09-custom-fields-config-type) 4. Update 04 of 05 ## Redesigned GitHub and GitLab PR picker in chat Attaching a pull request to a chat conversation now uses a searchable dropdown with status badges instead of a flat list. Click + in the chat input to open the attachment menu. GitHub Pull Requests and GitLab Merge Requests each open a submenu with a search field that queries the provider directly – results include status badges (open, merged, closed) and load incrementally. If you haven't connected a provider yet, an Add Integrations option links you to the connection settings. The old flat-list submenus are replaced entirely. [\# Direct link](#2026-06-09-redesigned-pr-picker-in-chat) 5. Update 05 of 05 ## Status badge links now filter to the right test plan Clicking a status badge in a README or pull request now opens the results page filtered to that badge's test plan. Previously the badge linked to your general results view. Now it opens directly to the runs belonging to the test plan the badge was configured for, so teammates who click through from a README or PR see only the relevant results. The preview and embed links in Settings → Project → Status badges are updated the same way. [\# Direct link](#2026-06-09-status-badge-links-filter-test-plan) ## Your team moves fast. Can your testing keep up? QA.tech agents test your product autonomously, so moving fast never means shipping broken. See how it works in a 30-minute demo. [Get a demo](https://qa.tech/demo) [QA.tech](https://qa.tech/) SOC 2 Type 2 compliant ![Sensiba SOC 2 Type 2 compliant](https://qa.tech/assets/soc2-type2-badge-DPb1j9VX.png) ### Product - [Platform overview](https://qa.tech/product) - [AI QA Testing](https://qa.tech/ai-qa-testing) - [Web Testing](https://qa.tech/product/web-testing) - [Mobile Testing](https://qa.tech/product/mobile-testing) - [PR Testing](https://qa.tech/product/pr-testing) - [MCP](https://qa.tech/product/mcp) - [Use cases](https://qa.tech/use-cases) - [Changelog](https://qa.tech/changelog) ### Compare - [QA.tech vs Cypress](https://qa.tech/compare/qa-tech-vs-cypress) - [QA.tech vs Playwright](https://qa.tech/compare/qa-tech-vs-playwright) - [QA.tech vs Mabl](https://qa.tech/compare/qa-tech-vs-mabl) - [QA.tech vs QA Wolf](https://qa.tech/compare/qa-tech-vs-qa-wolf) - [AI vs Human QA](https://qa.tech/saas) ### Resources - [Docs](https://docs.qa.tech/) - [Blog](https://qa.tech/blog) - [Events](https://qa.tech/events) - [Pricing](https://qa.tech/pricing) - [Case Studies](https://qa.tech/case-studies) ### Company - [About](https://qa.tech/about-us) - [Partnerships](https://qa.tech/partnerships) - [Press](https://qa.tech/press) - [Contact Us](https://qa.tech/contact) - [Privacy Policy](https://qa.tech/privacy-policy) - [Terms of Service](https://trust.qa.tech/resources?s=mb9w4yjb03i3t8bjsq4jx3&name=main-agreement.pdf) - [Security & Compliance](https://trust.qa.tech/) ### Social - [](https://www.linkedin.com/company/qa-tech-ai/) - [](https://x.com/getqatech) - [](https://www.instagram.com/getqatech/) © 2025 QA.tech. All rights reserved