Bugasura

Open Claude Desktop → Settings → Connectors → Add Custom Connector

• Name: Bugasura
• URL: https://mcp.bugasura.io/mcp

Click Connect, sign in to Bugasura, and click Allow on the consent page.

Install in VS Code, or add to your VS Code MCP config:

{  "servers": {    "bugasura": {      "type": "http",      "url": "https://mcp.bugasura.io/mcp"    }  }}

VS Code detects the OAuth sign-in and opens the browser the first time a tool is used.

VS Code MCP Documentation

claude mcp add --transport http bugasura https://mcp.bugasura.io/mcp

Then run /mcp inside Claude Code, choose Bugasura → Authenticate, and complete the sign-in in the browser.

Claude Code MCP Documentation

Settings → Apps & Connectors → Advanced → turn on Developer mode, then Create:

• Name: Bugasura
• MCP Server URL: https://mcp.bugasura.io/mcp
• Authentication: OAuth

Click Create, sign in to Bugasura, and click Allow.

Add to Cursor, or add to ~/.cursor/mcp.json:

{  "mcpServers": {    "bugasura": {      "url": "https://mcp.bugasura.io/mcp"    }  }}

Cursor shows a Needs login badge next to the server; click it to sign in.

Add to your Windsurf MCP config:

{  "mcpServers": {    "bugasura": {      "serverUrl": "https://mcp.bugasura.io/mcp"    }  }}

Windsurf opens the sign-in page on first use.

Windsurf MCP Documentation

1. Open Cline
2. Click ☰ → MCP Servers → Remote Servers tab
3. Click Edit Configuration
4. Add:

{  "mcpServers": {    "bugasura": {      "url": "https://mcp.bugasura.io/mcp",      "type": "streamableHttp"    }  }}

{  "mcpServers": {    "bugasura": {      "type": "streamable-http",      "url": "https://mcp.bugasura.io/mcp"    }  }}

Roo Code MCP Documentation

• bugasura_get_user_context - Get all teams and projects in one call
• bugasura_find_team_by_name - Search teams by name
• bugasura_find_project_by_name - Search projects across all teams
• bugasura_list_teams - List all teams you belong to
• bugasura_get_team - Get detailed team information including settings and subscription details (supports team_id or team_name)
• bugasura_create_team - Create a new team (creator becomes owner/admin)
• bugasura_update_team - Update team name (admin-only, supports team_id or team_name)
• bugasura_delete_team - Delete team permanently (admin-only, DESTRUCTIVE, supports team_id or team_name)
• bugasura_list_team_members - List team members with IDs, names, emails, and roles
• bugasura_list_projects - List projects for a specific team
• bugasura_get_project_details - Get detailed project information
• bugasura_create_project - Create a new project (supports interactive team selection) (NEW)
• bugasura_update_project - Update project name, prefix, and settings (supports project_id or project_name, admin privileges may be required) (NEW)
• bugasura_delete_project - Delete project permanently (supports project_id or project_name, admin-only, DESTRUCTIVE) (NEW)

Smart Team Resolution: The bugasura_get_team, bugasura_update_team, and bugasura_delete_team tools support both team_id (numeric ID) and team_name (text name with partial matching). Use whichever is more convenient.

Smart Project Resolution: The bugasura_update_project and bugasura_delete_project tools support both project_id (numeric ID) and project_name (text name with partial matching) for flexible identification. (NEW)

Note: Team deletion is permanent and removes all associated projects, sprints, issues, test cases, and requirements. Project deletion is also permanent and removes all associated sprints, issues, and test cases. Use with extreme caution!

• bugasura_add_team_members - Invite users to a team by email addresses (supports team_id or team_name)
• bugasura_update_team_member - Change team member role (admin/member) (supports team_id or team_name)
• bugasura_delete_team_user - Remove a user from team (supports team_id or team_name, auto-resolves user by ID/email/name)

Smart Team Resolution: All team member tools support both team_id (numeric ID) and team_name (text name with partial matching). Use whichever is more convenient.

Smart User Resolution: The bugasura_delete_team_user tool can identify users by:

• User IDs (e.g., "123")
• Email addresses (e.g., "[email protected]")
• Names or partial names (e.g., "John", "John Doe")

Note: Only team admins can manage team members. Team owner cannot be removed.

• bugasura_list_sprints - List all sprints for a project
• bugasura_get_sprint_details - Get sprint info and statistics
• bugasura_create_sprint - Create a new sprint
• bugasura_update_sprint - Update sprint details (partial updates supported)
• bugasura_delete_sprint - Delete a sprint permanently (supports ID or name)

Note: All sprint tools support interactive context selection. Delete operations can be performed using either numeric IDs or names.

• bugasura_list_issues - List issues with optional sprint filter
• bugasura_get_issue - Get detailed issue information
• bugasura_create_issue - Create a new bug/issue, optionally with attachments (upload_id / file_paths)
• bugasura_add_issue_attachments - Attach files (screenshots, logs, recordings) to an existing issue
• bugasura_delete_issue_attachments - Delete issue attachments by file name (DESTRUCTIVE; names are checked against the issue first)
• bugasura_update_issue - Update issue details (partial updates supported)
• bugasura_delete_issue - Delete an issue permanently (supports ID, issue key like "ISS09", or summary/title)
• bugasura_get_issue_assignees - Get list of assignees for an issue with names, emails, and profile images
• bugasura_add_issue_assignees - Add assignees by name, email, or ID
• bugasura_remove_issue_assignees - Remove assignees by name, email, or ID

Note: All issue tools support interactive context selection. Delete operations can be performed using numeric IDs, issue keys (e.g., "ISS09"), or issue summaries.

• bugasura_list_issue_comments - List comments for an issue with pagination and filtering (supports creator_id filter, exclude system comments)
• bugasura_get_issue_comment - Get single comment details with full content and metadata
• bugasura_add_issue_comment - Create a new comment on an issue (supports public/private visibility, HTML formatting, attachments)
• bugasura_update_issue_comment - Update existing comment text and add attachments (author-only, supports interactive comment selection)
• bugasura_delete_issue_comment - Delete comment permanently (author or admin, supports interactive comment selection)

Key Features:

• Pagination: List comments with start_at and max_results parameters (default: 10 results, max: 100)
• Filtering: Filter by comment author (creator_id) or exclude system comments (get_user_comments_only)
• Interactive Selection: Prompts for team → project → issue → comment if not provided
• Comment Types: User comments (editable) vs System comments (auto-generated, read-only)
• Visibility Control: Public comments (visible to all) vs Private comments (team members only)
• HTML Support: Comments support HTML formatting and user mentions (@username)

Note: All comment tools support full interactive context selection, including comment selection for update/delete operations. System comments cannot be edited or deleted.

• bugasura_list_test_cases - List test cases for a project
• bugasura_get_test_case - Get detailed test case information
• bugasura_create_test_case - Create a new test case
• bugasura_update_test_case - Update test case (partial updates supported, assignees by name/email/ID)
• bugasura_delete_test_case - Delete a test case permanently (supports ID, test case key like "TES5", or scenario name)
• bugasura_link_test_cases_to_sprint - Add existing test cases to a sprint (comma-separated test case IDs)
• bugasura_unlink_test_cases_from_sprint - Remove test cases from a sprint; they stay in the project
• bugasura_list_agents - List the AI agents (API, Browser, Mobile) enabled on a project and what each one runs
• bugasura_assign_test_cases_to_agent - Assign sprint test cases to the agent for their platform, in the sprint or in a test run
• bugasura_run_agent_test_cases - Queue a test run's agent test cases (action='start') or report their progress (action='status')

Note: All test case tools support interactive context selection. Delete operations can be performed using numeric IDs, test case keys (e.g., "TES5"), or scenario names.

• bugasura_list_test_run_environments - List test data environments and app builds for a project (use to pick an environment / app build by name)
• bugasura_list_test_runs - List test run executions and schedulers for a test suite (report)
• bugasura_get_test_run_details - Get details for a single test run execution
• bugasura_create_test_run - Create a run — one-time or scheduled (recurring) with friendly recurrence options, environment, app build, and seeded test cases
• bugasura_update_test_run - Update a single execution run (name, status, environment, app build)
• bugasura_update_test_run_scheduler - Edit a run/scheduler (rename, environment/build, switch single↔scheduled, change frequency/recurrence, pause/resume)
• bugasura_rerun_test_run - Trigger a fresh execution from an existing scheduler
• bugasura_add_test_cases_to_run - Add (copy) test cases into an existing run
• bugasura_delete_test_run - Delete one or more execution runs (soft by default, permanent with is_permanent_delete=1)
• bugasura_delete_test_run_scheduler - Delete one or more schedulers (soft by default, permanent with is_permanent_delete=1)

Note: All test run tools support interactive context selection. Reports/suites, environments, app builds, runs, and schedulers can be referenced by name or numeric ID (names resolved automatically, with disambiguation when needed). Recurrence is set with friendly options (frequency, repeat_value/repeat_unit, selected_days, recurrence_type) rather than raw JSON.

API endpoints used:

Names are resolved via bugasura_list_sprints (report ↔ sprint), bugasura_list_test_run_environments (environment / app build), and /v1/testrunsExecution/getList (run / scheduler).

• bugasura_list_test_data_environments - List a project's test data environments with their baseUrl / apiBaseUrl (optionally with the Globals scope)
• bugasura_get_test_data_environment - Get one environment (or Globals) with all its active variables and files
• bugasura_create_test_data_environment - Create an environment (starts with empty baseUrl / apiBaseUrl variables)
• bugasura_rename_test_data_environment - Rename an environment
• bugasura_duplicate_test_data_environment - Copy an environment, or the Globals scope, with its variables and files into a new environment
• bugasura_delete_test_data_environment - Delete an environment with its variables and files (DESTRUCTIVE; needs delete_contents=true when it is not empty)
• bugasura_list_test_data_variables - List the variables of an environment or Globals (filter by key or active state)
• bugasura_create_test_data_variable - Add a variable to an environment or Globals
• bugasura_update_test_data_variable - Change a variable's value, key, description or active state (partial update)
• bugasura_delete_test_data_variable - Delete one variable (DESTRUCTIVE; default variables are protected)
• bugasura_list_test_data_files - List the files of an environment or Globals (filter by category or name), with download URLs and the project's categories
• bugasura_upload_test_data_files - Upload one or more files to an environment or Globals under a category, from an upload link, a share link or local paths (terminal)
• bugasura_get_test_data_file - Get one file's details, download link and (Office files) preview link; optionally read a text file's content
• bugasura_download_test_data_file - Get a file's direct download link, optionally saving it to the server's disk (terminal)
• bugasura_list_test_data_app_builds - List the app builds (App Build category) across all environments and Globals
• bugasura_delete_test_data_file - Delete one file (DESTRUCTIVE)
• bugasura_list_test_data_categories - List the built-in and custom file categories
• bugasura_create_test_data_category - Add a custom file category

Key Features:

• Environments, variables and files accept a name or numeric ID; "Globals" names the project-wide global scope
• Deletes always target a single resolved ID, never a whole scope
• Update keeps every field you do not pass; the default baseUrl / apiBaseUrl variables only take value and active-state changes, as in the web app

Note: All test data tools require team_id and project_id; the create/update variable and upload tools also require environment (pass "Globals" for the global scope). File types follow the web app: the 'App Build' category takes apk, aab, ipa, apks, apkm, xapk; other categories take documents, spreadsheets, csv/json/xml/yaml, images, audio/video and app builds, up to 1024MB per file.

Uploading. bugasura_upload_test_data_files sends the files themselves to /v1/projectTestDataFiles/add as multipart testData[] parts, so it works wherever the server runs. Local paths (file_paths) are STDIO-only; on the hosted server the user uploads their own file through bugasura_create_upload_link(purpose='test_data') and the tool takes its upload_id (up to 100 MB per link), or passes a Google Drive, Dropbox or other public link as source_url (up to 1024 MB). Large builds get a longer timeout, and if Bugasura is still slower than that, the tool checks whether the files arrived before reporting the upload as unconfirmed, so a retry does not create duplicates.

API endpoints used:

• bugasura_list_testcase_comments - List comments for a test case with pagination and filtering (supports creator_id filter, exclude system comments)
• bugasura_get_testcase_comment - Get single test case comment details with full content and metadata
• bugasura_add_testcase_comment - Create a new comment on a test case (supports public/private visibility, HTML formatting)
• bugasura_update_testcase_comment - Update existing test case comment text (author-only, supports interactive comment selection)
• bugasura_delete_testcase_comment - Delete test case comment permanently (author or admin, supports interactive comment selection)

Key Features:

• Pagination: List comments with start_at and max_results parameters (default: 10 results, max: 100)
• Filtering: Filter by comment author (creator_id) or exclude system comments (get_user_comments_only)
• Interactive Selection: Prompts for team → project → test case → comment if not provided
• Comment Types: User comments (editable) vs System comments (auto-generated, read-only)
• Visibility Control: Public comments (visible to all) vs Private comments (team members only)
• HTML Support: Comments support HTML formatting and user mentions (@username)
• Attachments: upload_id / file_paths attach files to a new comment or add them to an updated one; a comment is the only place a test case holds files. An update keeps the comment's existing attachments unless comment_attachments lists the ones to keep.

Note: All test case comment tools support full interactive context selection, including comment selection for update/delete operations. System comments cannot be edited or deleted.

• bugasura_list_requirements - List all requirements for a project or sprint
• bugasura_get_requirement_details - Get detailed requirement information including parent/child hierarchy
• bugasura_create_requirement - Create a new requirement with interactive folder selection, optionally with attachments
• bugasura_add_requirement_attachments - Attach files to an existing requirement
• bugasura_update_requirement - Update requirement details (partial updates supported, preserves all fields)
• bugasura_delete_requirement - Delete a requirement permanently
• bugasura_link_requirement_testcases - Link test cases to a requirement (comma-separated IDs)
• bugasura_unlink_requirement_testcases - Unlink test cases from a requirement; the test cases are kept
• bugasura_create_requirement_folder - Create a folder for organizing requirements
• bugasura_list_requirement_folders - List all folders in a project
• bugasura_list_requirement_comments - List a requirement's comments (paginated)
• bugasura_get_requirement_comment - Get one comment with its attachment URLs
• bugasura_add_requirement_comment - Comment on a requirement, with optional attachments or as a threaded reply
• bugasura_update_requirement_comment - Edit a comment and add attachments (existing ones are kept unless comment_attachments says otherwise)
• bugasura_delete_requirement_comment - Delete a comment and its attachments (DESTRUCTIVE)

Key Features:

• Folder Organization: Requirements must be organized in folders. Interactive folder selection helps you choose or create folders during requirement creation.
• Parent-Child Hierarchy: Requirements can have parent requirements for multi-level organization (EPICs → STORYs → TASKs).
• Smart Assignee Resolution: Assign by name, email, or user ID (automatically resolved).
• Field Preservation: Update operations fetch existing data and preserve all fields not being updated.
• Test Case Linking: Link requirements to test cases for traceability.

Note: All requirement tools support interactive context selection. The folder_id field is required for all requirement operations and will be auto-fetched or interactively selected.

The knowledge base is a project-level document library, organized in folders and shown on the project's Knowledge Base page. It is separate from a TestPert sprint's own knowledge base (see the Testpert tools below).

Documents

• bugasura_list_knowledge_base_documents - List documents in a folder or across the whole project (supports starred_only and pagination)
• bugasura_download_knowledge_base_document - Get a direct download link for an uploaded document, and optionally save it to disk
• bugasura_star_knowledge_base_document - Star or unstar a document (starred=False removes the star)
• bugasura_delete_knowledge_base_document - Delete a document permanently (admin-only, DESTRUCTIVE)

Imports (all in tools/knowledge_base.py)

The six entries in the Knowledge Base page's "+" menu, plus the document editor's own Import menu. Everything except the file upload runs in the background — the tool returns as soon as the crawl/sync is queued, and bugasura_list_knowledge_base_documents shows its progress in stage. Connector credentials are supplied per call and are never stored by this server.

Local (STDIO) only: the Coda, Jira, Confluence and Figma imports and their listing tools take that service's API token as an argument, so the hosted server (/mcp) does not offer them: a token typed into a hosted chat would pass through the conversation. Run the server locally to use them; on the hosted server, import a website or upload a file instead.

• bugasura_create_upload_link - A short-lived, single-use upload link on this server for a file on the user's own computer (hosted server only). purpose picks the consuming tool: knowledge_base, document_import, testpert_kb, attachment (issues, issue/test case comments, requirements; any file type), or test_data (bugasura_upload_test_data_files)
• bugasura_upload_knowledge_base_document - Upload document(s) (.txt, .pdf, .doc, .docx, .md) from an upload link, a share link or a local path
• bugasura_import_website_to_knowledge_base - Crawl a website (max_pages, include_linked_pages)
• bugasura_import_coda_to_knowledge_base - Import a Coda doc's pages ("Superhuman Import"); needs a Coda API key and the doc's URL, id or name
• bugasura_import_jira_to_knowledge_base - Import Jira issues, one page per Jira project; whole projects by default, or specific issue_keys
• bugasura_import_confluence_to_knowledge_base - Import Confluence spaces, one page tree per space; whole spaces by default, or specific page_ids
• bugasura_import_figma_to_knowledge_base - Import Figma frames as design context (DESTRUCTIVE — see Key Features below)
• bugasura_import_file_to_knowledge_base_document - The document editor's Import menu: a .md file becomes a new page, a .csv/.xlsx/.xls file becomes a Markdown table appended to an existing page

Pick what a connector should import with the listing tools first:

• bugasura_list_coda_docs / bugasura_list_coda_pages - The docs a Coda API key can see, and one doc's page tree
• bugasura_list_jira_projects / bugasura_list_jira_issues - The projects an account can see (with issue counts), and one project's issues
• bugasura_list_confluence_spaces / bugasura_list_confluence_pages - The spaces an account can see, and one space's pages

Folders

• bugasura_list_knowledge_base_folders - List the top-level knowledge base folders (paginated), each with its sub-folder tree and documents
• bugasura_create_knowledge_base_folder - Create a folder, optionally nested under an existing one
• bugasura_rename_knowledge_base_folder - Rename a folder in place (keeps its parent and its contents)
• bugasura_delete_knowledge_base_folder - Delete a folder (admin-only, DESTRUCTIVE)

Page Documents

A page document is written in Bugasura instead of uploaded — the web app's "Create Document" flow. Its body is a tree of pages, each with its own markdown content. Documents synced from Coda, Jira, Confluence or a URL are stored in the same shape, so the page tools work on those too.

• bugasura_create_knowledge_base_document - Create a page document (starts with one empty page)
• bugasura_rename_knowledge_base_document - Rename a page document
• bugasura_list_knowledge_base_pages - List a document's pages, with page_path, depth and has_content
• bugasura_create_knowledge_base_page - Add a page, optionally nested under a page or placed after one, with its content
• bugasura_rename_knowledge_base_page - Rename a page
• bugasura_get_knowledge_base_page_content - Read a page's current markdown body (call before editing one)
• bugasura_update_knowledge_base_page_content - Write a page's markdown: replace the whole body ('' clears it), or mode='append' / mode='prepend' to add to it
• bugasura_duplicate_knowledge_base_page - Copy a page, with or without its sub pages
• bugasura_move_knowledge_base_page - Re-parent or reorder a page (parent_page / after_page / to_root)
• bugasura_delete_knowledge_base_page - Delete a page and its sub pages (DESTRUCTIVE)

Key Features:

• Automatic Folder Handling: Pass folder_name to file the document in that folder — it is matched case-insensitively and created when the project doesn't have one by that name. Omit it and the project's first knowledge base folder is used, or a Knowledge Base folder is created when the project has none.
• Three Ways to Provide a File: Files are never encoded by the assistant.
  • upload_id (hosted server): bugasura_create_upload_link returns a link on this server, /upload/<upload_id>, bound to the signed-in user. It works once and expires after 30 minutes. The user opens it and uploads the file through a plain form, or a terminal client runs curl -sS -F [email protected] <upload_url>. The bytes go through the browser or the shell, never through the model. The file is staged under UPLOAD_STAGING_PATH for up to an hour, until bugasura_upload_knowledge_base_document(upload_id=...) (or bugasura_import_file_to_knowledge_base_document for purpose='document_import') sends it to Bugasura and deletes it. Only the user who created the link can use its upload_id.
  • source_url: a Google Drive, Dropbox or any public download link. The server fetches it.
  • file_paths: absolute paths, local STDIO servers only.
• Multiple Files: Several paths, or up to 10 files in one upload link (100 MB in total), are uploaded into the same folder.
• Folder Names: A folder name cannot contain <, >, / or \, and two folders cannot share a name under the same parent — bugasura_rename_knowledge_base_folder reports both cases up front, and renaming a folder to the name it already has is answered without a write.
• Smart Document Resolution: Documents are identified by file name (exact match, then partial) or by numeric id. Ambiguous names come back with the matching documents so the user can pick one; add folder_name to narrow the search.
• Background Processing: Bugasura processes uploaded documents automatically; they become searchable project context once processing finishes.
• Downloads Are Links First: Bugasura has no download endpoint — an uploaded file's bytes live on the CDN, and bugasura_download_knowledge_base_document turns the stored path into a direct, login-free download_url. That link is the answer for most clients; add save_to_path to also write the file to the machine running the server, which only helps when that is the user's own machine (terminal use). Set CDN_BASE_URL in the server's .env for deployments the known-host map doesn't cover — the CDN is a separate CloudFront/S3 host and cannot be derived from API_BASE_URL.
• Only Uploaded Files Are Downloadable: Page documents, website entries and Jira/Confluence imports have no file of their own, and Bugasura has no PDF export — so a page document cannot be handed over as a PDF. Read those with bugasura_list_knowledge_base_pages instead.
• Smart Page Resolution: Pages are identified by page name (exact match, then partial) or by page id (page_20250104120500). Ambiguous names come back with the matching pages so the user can pick one.
• Connector Credentials Are Per Call: Jira, Confluence, Coda and Figma credentials are asked for on every call and forwarded straight through — this server stores none of them. Jira Cloud and Confluence take an API token, a self-hosted Jira (deployment_type="SERVER") takes the account password, Coda takes an API key, and Figma takes a personal access token. Confluence is the one exception: leave its three credential arguments out and the listing tools fall back to the project's saved Confluence integration.
• Import Into an Existing Document: bugasura_import_jira_to_knowledge_base and bugasura_import_confluence_to_knowledge_base create a new document by default; pass document_identifier to merge the selection into an existing page document instead, the way the web app's "Import → Jira / Confluence" works from inside a document. A document that is already importing is reported rather than queued twice.
• Figma Replaces the Project's Frame Set: Bugasura keeps one set of Figma frames per project, and an import rewrites that set — any stored frame missing from the payload is deleted. bugasura_import_figma_to_knowledge_base reads the existing frames back and carries them forward, so an import only adds; replace_existing=True drops them, and is only for when the user has asked for that. Each link must point at a frame (carry a node-id, i.e. Figma's "Copy link to selection"); a link to a whole file is rejected.
• Editing a Page is Read-Modify-Write: The API only ever writes a page's markdown, so bugasura_get_knowledge_base_page_content reads it back off the CDN the way the web editor does (needs CDN_BASE_URL, same as downloads). Because the write replaces the whole body, changing part of a page means reading it, editing that text, and writing the full result back with mode='replace'. To only add to a page, mode='append' / mode='prepend' do the read for you — pass just the new text. A page too large to read safely is refused rather than truncated, so a partial copy can never be written back over the full one.

Note: Documents are limited to 100MB each, except bugasura_import_file_to_knowledge_base_document (the document editor's Markdown/CSV/Excel import), which is capped at 10MB. Call bugasura_prepare_kb_upload first when the user wants to share a file — it returns the instructions to show them. Deleting a document removes its file and everything the AI learned from it, and cannot be undone; deleting a folder that still holds documents requires delete_documents=True and takes its documents with it. Both deletes require team or project admin rights. Deleting a page that has sub pages likewise requires delete_sub_pages=True and takes them with it.

TestPert is a paid, project-level AI feature (is_testpert_enabled on the project). It generates a full test plan and test cases from your requirement documents or existing requirements.

Sprint creation

• bugasura_create_testpert_sprint - Create a TestPert sprint (confirms options before creating; set confirm_options=True to proceed)

Normal flow — upload documents → answer questions → edit plan → generate

• bugasura_testpert_upload_kb - Link project KB documents to the sprint, or upload docs/images to it (.txt, .pdf, .docx, .md, .json up to 100 MB; .png, .jpg, etc. up to 20 MB). Images come through an upload link with purpose='testpert_kb'.
• bugasura_testpert_list_kb - List documents currently in the knowledge base
• bugasura_testpert_delete_kb - Remove a document from the knowledge base
• bugasura_testpert_generate_sprint_context - Start requirement analysis (KB → SPRINT_CONTEXT)
• bugasura_testpert_get_kb_validation - See which uploaded documents the engine couldn't confidently classify, and why
• bugasura_testpert_resolve_kb_validation - Submit a role for each flagged document and resume sprint-context generation
• bugasura_testpert_get_sprint_context - Read the engine's guessed platform, user roles, and affected modules for review
• bugasura_testpert_confirm_sprint_context - Confirm the sprint context and advance to the deepen-requirement questions
• bugasura_testpert_answer_context_questions - Submit answers to the AI's deepen-requirement questions
• bugasura_testpert_get_requirement_contexts - Fetch deepen questions, missing requirements, and risks for user review
• bugasura_testpert_update_requirement_contexts - Write approve/reject/edit decisions back for missing requirements and risks (auto-advances to RISKS_IN_REQUIREMENTS by default)
• bugasura_testpert_add_context_question - Add a deepen-requirement question to the sprint (the 'Add Question' button)
• bugasura_testpert_delete_context_question - Remove a deepen-requirement question from the sprint
• bugasura_testpert_get_testplan - Fetch the generated test plan (focus areas + feature/sub-feature tree)
• bugasura_testpert_update_testplan - Edit focus-area levels and the feature tree
• bugasura_testpert_get_features - List the live feature/sub-feature tree
• bugasura_testpert_add_feature - Add a feature or sub-feature
• bugasura_testpert_delete_feature - Delete a feature or sub-feature
• bugasura_testpert_enrich_requirements - Run the requirements-enrichment phase explicitly (optional — generate_coverage runs it automatically)
• bugasura_testpert_generate_coverage - Move the sprint to test coverage (runs enrichment first if needed)
• bugasura_testpert_get_coverage - Fetch the coverage mind map
• bugasura_testpert_generate_testcases - Generate test cases (polls to completion; re-callable)
• bugasura_testpert_regenerate_testcases - Regenerate/retry one sub-feature's test cases after TEST_CASES (needs the user's answers to the 3-section context modal; max 5 attempts per sub-feature)

Skip-enrich flow — use existing project requirements instead of documents

• bugasura_testpert_link_requirements - Link existing project requirements to the sprint as its source
• bugasura_testpert_start_from_requirements - Build the test plan directly from the sprint's linked requirements

Low-level status driver (advanced)

• bugasura_testpert_advance - Set a specific status and/or poll until a target status — use this when you need direct control over the pipeline

Flow overview:

Normal:  create → upload_kb → generate_sprint_context → [get_kb_validation → resolve_kb_validation]*         → get_sprint_context → confirm_sprint_context → answer_context_questions         → (missing reqs) → (risks) → get_testplan → enrich → generate_coverage → generate_testcases
         * only if generate_sprint_context lands on SPRINT_CONTEXT_USER_VALIDATION instead of SPRINT_CONTEXT
Skip:    create (skip_enrich=true) → link_requirements → start_from_requirements         → get_testplan → generate_coverage → generate_testcases

Notes:

• The project must have TestPert enabled (is_testpert_enabled). Use bugasura_create_sprint for standard sprints.
• Polling tools (generate_sprint_context, resolve_kb_validation, confirm_sprint_context, start_from_requirements, enrich_requirements, generate_coverage, generate_testcases) are time-bounded per call and re-callable — if the AI phase is still running, call the same tool again to keep checking.
• generate_coverage drives both the enrichment and test-plan phases itself (RISKS_IN_REQUIREMENTS → ENRICH_REQUIREMENTS → TEST_PLANING → TEST_COVERAGE), one phase per call — enrich_requirements is only needed if you want that phase visible as its own step.
• A team-admin API key is required for status transitions and test-plan updates.