Bugasura MCP Server

Bugasura MCP Server

Connect AI assistants directly to your test management workspace.

Bugasura MCP Server enables AI tools like Claude, VS Code Copilot, and Cursor to interact with your Bugasura projects—manage test cases, track issues, plan sprints, and more—all through natural language.

---

⚠️ Breaking changes in 3.5

⚠️ Breaking changes in 3.3

⚠️ Breaking changes in 3.0

Authentication moved to OAuth 2.0 sign-in. If you're upgrading from 2.x:

⚠️ Breaking changes in 2.0

If you're upgrading from 1.x, update your client configuration:

1.x clients pointed at /sse must migrate to /mcp — SSE has been removed.

---

Features

• 📋 Test Case Management - Create, update, delete, and search test cases
• 💬 Test Case Comments - Add, update, delete, and list comments on test cases with pagination and filtering
• 🐛 Issue Tracking - Report, manage, and delete bugs with rich context
• 💬 Issue Comments - Add, update, delete, and list comments on issues with pagination and filtering
• 📝 Requirements Management - Create, organize, and manage product requirements with folder structure
• 📚 Knowledge Base - Upload, list, star, and delete documents in a project's knowledge base, with folders created on demand; import from a website, Coda, Jira, Confluence or Figma
• 🏃 Sprint Planning - Create, update, delete, and manage agile sprints
• 🏁 Test Runs - Create one-time or scheduled (recurring) runs, edit/rerun/delete them, pick environments and app builds, and add test cases — all by name or ID
• 🧪 Test Data - Manage a project's test data environments (create, rename, duplicate, delete), their variables and the Globals scope, plus test data files (upload, read, download, delete), app builds and file categories — all by name or ID
• 🤖 Testpert Sprints - Full AI-driven test enrichment flow: upload specs, answer requirement questions, edit the test plan, and generate test cases automatically
• 👥 Team Collaboration - Assign work using names or emails (auto-resolves to user IDs)
• 👤 Team Member Management - Add, update roles, and remove team members using team names or IDs
• 🔍 Smart Discovery - Find projects and teams without memorizing IDs
• 🤖 Interactive Workflows - Guided context selection for all operations

---

Quick Start

1. Have a Bugasura account

That's all the hosted server needs. On first use your AI tool opens the Bugasura sign-in page in your browser; approve once and you're connected. Tokens refresh automatically for 30 days.

An API key is only needed for the local STDIO setup described under Local Development.

2. Install the MCP Server

Add the server URL to your AI tool. No headers, no keys: the client discovers the OAuth sign-in from the server and walks you through it.

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.

codex mcp add bugasura --url https://mcp.bugasura.io/mcp
codex mcp login bugasura

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

3. Start Using It

Once installed, just talk naturally to your AI assistant:

"List all my Bugasura teams and projects"

"Create a test case for login functionality with high severity"

"Create a requirement for user authentication feature"

"Show me all critical bugs in sprint 5"

---

How It Works

No IDs Required

Bugasura MCP features interactive context selection. You don't need to know team IDs, project IDs, or user IDs—just describe what you want in natural language.

Example: Creating an issue without knowing any IDs:

You: "Create a bug for the login button not working"

AI: [Calls MCP server]
    "Which team should I use?
     1. Acme Corp (Admin)
     2. Client Project (Member)"

You: "Acme Corp"

AI: "Which project?
     1. Mobile App
     2. Web App"

You: "Mobile App"

AI: "Which sprint?
     1. Sprint 5 (IN PROGRESS)
     2. Sprint 6 (SCHEDULED)"

You: "Sprint 5"

AI: ✓ "Created issue #ISSUE-123 in Sprint 5"

The system guides you through team → project → sprint selection automatically.

Smart Assignee Resolution

Assign work using names, emails, or user IDs—the system automatically converts them:

"Assign issue 123 to John Doe"

"Add jane@example.com and user 789 to issue 456"

"Remove Sarah from issue 321"

Works for both issues and test cases.

Discovery Tools

Find resources without memorizing IDs:

"Find my mobile app project"
→ Searches across ALL teams automatically

"Show me all projects I have access to"
→ Returns complete context in one call

---

What You Can Do

📋 Test Cases

Create an API test case for user authentication with priority P1

List all test cases for the mobile app project

Update test case 123 to mark it as PASS

Assign test case 456 to john@example.com

Delete test case 789

Delete test case with key "TES5"

Delete test case named "Verify login with valid credentials"

💬 Test Case Comments

List all comments on test case 123

List comments on test case "Verify login with valid credentials"

List only user comments on test case 456 (exclude system comments)

Get details of comment 789

Add a comment "Test passed on Chrome and Firefox" to test case 123

Add a private comment to test case 456

Update comment 789 with new text

Delete comment 456

📝 Requirements

Create a requirement titled "User Authentication" with details and priority P1

List all requirements for the mobile app project

Get requirement details for requirement ID 2036

Update requirement 2036 to change severity to HIGH

Assign requirement 456 to john@example.com

Create a folder named "Sprint 1 Features" for organizing requirements

List all requirement folders in a project

Delete requirement 789

Link test cases to requirement 2036

🐛 Issues & Bugs

Create a critical bug for login page crash in sprint 5

Show me all open issues assigned to me

Update issue 789 to change status to "Fixed"

Add John and Jane as assignees to issue 123

Delete issue 456

Delete issue with key "ISS09"

Delete issue with summary "Login button not working"

💬 Issue Comments

List all comments on issue 123

List comments with pagination (start at 10, show 20 results)

List only user comments, exclude system comments

Get details of comment 456

Add a comment "Fixed in latest build" to issue 789

Add a private comment to issue 123

Update comment 456 with new text

Delete comment 789

🏃 Sprints

Create a new sprint called "Sprint 15" for the mobile app

List all sprints for project 456

Update sprint 789 to mark it as COMPLETED

Show sprint details including issue statistics

Delete sprint 321

Delete sprint named "Sprint 15"

🏁 Test Runs

List the test runs for the "Login Sprint"

Show me the environments and app builds for this project

Create a test run called "Smoke run" for the "Login Sprint" using the "Staging" environment

Schedule a daily run "Nightly" for the "Login Sprint" at 09:00, ending after 10 runs

Schedule a run every 2 weeks on Monday and Friday at 09:00

Add test cases 12, 15, 18 to the "Smoke run" run

Rename the "Smoke run" run and mark it COMPLETED

Pause the "Nightly" scheduler

Rerun the "Nightly" scheduler

Delete the "Smoke run" run

Note: Reports/suites, environments, app builds, runs, and schedulers can all be referenced by name or numeric ID — names are resolved automatically (with a helpful prompt if a name is ambiguous).

🧪 Test Data

List the test data environments for this project

Create a "Staging" environment and set its baseUrl to https://staging.example.com

Add a variable loginEmail = qa@example.com to the Staging environment

Show me everything in the Staging environment

Duplicate Staging as "UAT"

Deactivate the legacyToken variable in Globals

List the App Build files in Production

Upload /home/me/users.csv to the Staging environment as Sample Data Files

Show me what's in users.csv in Staging

Download app-release.apk from Production to /home/me/builds/

Which app builds does this project have?

Add a custom file category "Payment Fixtures"

Delete the "Old QA" environment

Note: Environments, variables and files can be referenced by name or numeric ID; use "Globals" for the project-wide global scope. Writes and deletes need the scope named explicitly and match names exactly; only the read tools accept part of a name. Deleting an environment that still holds custom variables or files asks for confirmation first (delete_contents=true). The default baseUrl / apiBaseUrl variables can have their value changed but cannot be renamed or deleted.

🤖 Testpert Sprints

TestPert is a paid, project-level feature that uses AI to generate a full test plan and test cases from your requirement documents.

Normal flow (with document upload):

Create a TestPert sprint called "Login Feature Sprint"

Upload /path/to/login-spec.pdf to the knowledge base

Start the analysis and answer the requirement questions

Review the test plan focus areas and feature tree

Generate test cases for the sprint

Skip-enrich flow (driven from existing requirements):

Create a TestPert sprint with skip_enrich_requirements=true

Link requirement IDs 101 and 102 to the sprint

Build the test plan from those requirements

📋 Projects

List all projects in team 123

Find project by name "Mobile App"

Get detailed information for project 456

Create a new project "E-commerce Web App" in team 123

Update project 789 name to "Mobile Application"

Update project "Mobile App" to change issue prefix to "MOB"

Delete project 321

Delete project "Old Test Project"

👥 Team Management

List all my teams

Find team by name "Acme"

Get detailed information for team 123

Get detailed information for team "Engineering"

Create a new team called "Mobile App Team"

Update team 456 name to "Web Development Team"

Rename team "Mobile Team" to "Mobile App Development"

List all members in team "Acme Corp"

Add john@example.com and jane@example.com to team "Engineering"

Invite user@example.com to team 123

Promote user 456 to admin in team "Marketing"

Demote user to regular member in team "Sales"

Remove john@example.com from team "Sales"

Remove user by name "John Doe" from team 123

Show all projects in team 456

---

Available Tools

• 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., "john@example.com")
• 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

Documentation truncated — see the full README on GitHub.