@testomatio/mcp 1.0.14 → 2.0.0-beta.9

package/README.md

@@ -1,449 +1,193 @@
 # Testomat.io MCP Server
 
-A Model Context Protocol (MCP) server for Testomat.io API integration with AI assistants like Cursor.
+Model Context Protocol (MCP) server that enables AI assistants (Claude, Cursor, OpenCode, etc.) to interact with Testomat.io Public API v2.
 
-<img width="1920" height="1085" alt="image" src="https://github.com/user-attachments/assets/cf823e8b-1305-4ed2-a7c5-712efec12ceb" />
-
-## Installation
+## Features
 
-### Prerequisites
+- **Full CRUD** for core entities:
+  - Tests, Suites, Plans, Runs, TestRuns, RunGroups, Steps, Snippets, Labels
+  - Tags (read-only access)
+  - Issues (global + scoped helpers for tests/suites/runs/testruns/plans)
+- **Smart Search** - delegates to list endpoints with query/filter forwarding
+- **Issue Linking** - link/unlink issues to any resource
+- **API Compatibility** - automatic handling of payload format differences (flat vs wrapped)
+- **Run Management** - status transitions via `status_event` parameter
 
-- Node.js 18 or higher (with built-in fetch support)
-- npm or yarn package manager
-- Testomat.io account with API access
+## Quick Start
 
-### Run directly with npx
+### Installation
 
 ```bash
-npx @testomatio/mcp@latest --token <your-token> --project <project-id>
+npm install -g @testomatio/mcp
 ```
 
-## Usage
-
-### Command Line Options
-
-The MCP server can be started using command line arguments or environment variables:
+### Configuration
 
-#### Using Command Line Arguments
+**Required credentials:**
+- `TESTOMATIO_PROJECT_TOKEN` - Your project API token
+- `TESTOMATIO_PROJECT_ID` - Your project ID
 
+**Run server:**
 ```bash
-# Using short flags
-npx @testomatio/mcp@latest -t testomat_YOUR_TOKEN_HERE -p your-project-id
-
-# Using long flags
-npx @testomatio/mcp@latest --token testomat_YOUR_TOKEN_HERE --project your-project-id
-
-# With custom base URL
-npx @testomatio/mcp@latest --token testomat_YOUR_TOKEN_HERE --project your-project-id --base-url https://your-instance.testomat.io
+testomatio-mcp --token <PROJECT_TOKEN> --project <PROJECT_ID>
 ```
 
-#### Using Environment Variables
-
+**Or with environment variables:**
 ```bash
-# Set environment variables
-export TESTOMATIO_API_TOKEN=testomat_YOUR_TOKEN_HERE
-export TESTOMATIO_BASE_URL=https://app.testomat.io  # Optional, defaults to https://app.testomat.io
-
-# Run with project ID
-npx @testomatio/mcp@latest --project your-project-id
-
-# Or run directly with environment variables
-TESTOMATIO_API_TOKEN=testomat_YOUR_TOKEN_HERE npx @testomatio/mcp@latest --project your-project-id
+export TESTOMATIO_PROJECT_TOKEN=<PROJECT_TOKEN>
+export TESTOMATIO_PROJECT_ID=<PROJECT_ID>
+testomatio-mcp
 ```
 
-### Getting Your API Token
-
-1. Go to [Testomat.io](https://app.testomat.io)
-2. Navigate to user tokens https://app.testomat.io/account/access_tokens
-3. Create and copy **General API token** (starts with `testomat_`)
-
-### Getting Your Project ID
-
-Your project ID can be found in the URL when you're viewing your project:
-```
-https://app.testomat.io/projects/YOUR_PROJECT_ID
+**Optional: custom base URL**
+```bash
+export TESTOMATIO_BASE_URL=https://beta.testomat.io
 ```
 
-### ID Formats
-
-Testomatio uses specific ID formats for different resources:
-
-- **Test IDs**: Start with `T` prefix followed by 7 alphanumeric characters (e.g., `Ta1b2c3d4`)
-- **Suite IDs**: Start with `S` prefix followed by 7 alphanumeric characters (e.g., `Sx9y8z7w6`)
-- **Total length**: 8 characters including the prefix
-- **Format**: `[Prefix][7 alphanumeric characters]`
+## Usage with AI Assistants
 
-When working with tools that require specific IDs, ensure you use the correct format with the appropriate prefix.
+### Cursor IDE
 
-## Integration with Cursor
-
-To use this MCP server with Cursor, add the following configuration to your Cursor settings:
-
-### Option 1: Using npx (Recommended)
-
-Add this to your Cursor MCP settings (`cursor-settings.json` or through the Cursor settings UI):
+Add to `.cursorrules` or settings.json:
 
 ```json
 {
   "mcpServers": {
     "testomatio": {
-      "command": "npx",
-      "args": ["-y", "@testomatio/mcp@latest", "--token", "testomat_YOUR_TOKEN_HERE", "--project", "YOUR_PROJECT_ID"]
+      "command": "testomatio-mcp",
+      "args": ["--token", "<TOKEN>", "--project", "<PROJECT_ID>"],
+      "env": {
+        "TESTOMATIO_PROJECT_TOKEN": "<TOKEN>",
+        "TESTOMATIO_PROJECT_ID": "<PROJECT_ID>"
+      }
     }
   }
 }
 ```
 
-### Option 2: Using Environment Variables
-
-First, set your environment variables in your shell profile (`.bashrc`, `.zshrc`, etc.):
-
-```bash
-export TESTOMATIO_API_TOKEN=testomat_YOUR_TOKEN_HERE
-```
-
-Then add this to your Cursor MCP settings:
+### Claude Desktop
 
 ```json
 {
   "mcpServers": {
     "testomatio": {
-      "command": "npx",
-      "args": ["-y", "@testomatio/mcp@latest", "--project", "YOUR_PROJECT_ID"],
-      "env": {
-        "TESTOMATIO_API_TOKEN": "testomat_YOUR_TOKEN_HERE"
-      }
+      "command": "node",
+      "args": ["/path/to/mcp/index.js", "--token", "<TOKEN>", "--project", "<PROJECT_ID>"]
     }
   }
 }
 ```
 
-## Features
-
-### Tools
-
-#### Tests
-* `get_tests` – Get all tests (params: `plan`, `query`, `state`, `suite_id`, `tag`, `labels`) — api: GET `/tests`
-* `get_test` – Get a specific test by ID with all information including labels, tags, and metadata (params: `test_id`) — api: GET `/tests/{test_id}`
-* `search_tests` – Search tests (params: `query`, `tql`, `labels`, `state`, `priority`, `filter`, `page`) — api: GET `/tests`
-* `create_test` – Create a new test (params: `suite_id`, `title`, `description`, `code`, `file`, `state`, `tags`, `jira_issues`, `assigned_to`, `labels_ids`, `fields`) — api: POST `/tests`
-* `update_test` – Update an existing test (params: `test_id`, `suite_id`, `title`, `description`, `code`, `file`, `state`, `tags`, `jira_issues`, `assigned_to`, `labels_ids`, `fields`) — api: PUT `/tests/{test_id}`
+### OpenCode
 
-#### Test Suites
-* `search_suites` – Search suites (params: `query`, `labels`, `state`, `priority`, `page`) — api: GET `/suites`
-* `get_root_suites` – List root-level suites (no params) — api: GET `/suites`
-* `get_suite` – Get one suite (params: `suite_id`) — api: GET `/suites/{suite_id}`
-* `create_suite` – Create a new suite (params: `title`, `description`, `parent_id`, `fields`) — api: POST `/suites`
-* `create_folder` – Create a new folder (params: `title`, `description`, `parent_id`, `fields`) — api: POST `/suites`
+Create `.opencode/opencode.json`:
 
-#### Labels
-* `get_labels` – Get all available labels with their IDs and configurations
-* `create_label` – Create a new label with optional custom field
-* `unlink_label` – Remove a label from a test or suite
-
-### Custom Fields and Labels
-
-The MCP server provides two distinct ways to assign values to tests, suites, and folders:
-
-#### 1. Using `labels_ids` with label:value syntax
-```javascript
+```json
 {
-  "labels_ids": ["priority:high", "severity:critical", "type:regression"]
+  "$schema": "https://opencode.ai/config.json",
+  "mcp": {
+    "testomat": {
+      "type": "local",
+      "command": [
+        "node",
+        "node_modules/@testomatio/mcp/index.js",
+        "--token",
+        "<TOKEN>",
+        "--project",
+        "<PROJECT_ID>"
+      ],
+      "enabled": true,
+      "environment": {
+        "TESTOMATIO_BASE_URL": "https://app.testomat.io"
+      }
+    }
+  }
 }
 ```
-- Direct label assignment with values using `label:value` format
-- Good for simple label assignments
-- Works with existing Testomatio labels
 
-#### 2. Using `fields` parameter (structured custom fields)
-```javascript
+## Quick Examples
+
+**List tests:**
+```json
 {
-  "fields": {
-    "priority": "high",
-    "severity": "critical",
-    "risk_score": "8.5",
-    "team": "backend"
-  }
+  "name": "tests_list",
+  "arguments": { "page": 1, "per_page": 50 }
 }
 ```
-- Structured way to set custom fields
-- Cleaner syntax for AI assistants
-- Supports any custom field defined in your Testomatio project
-- Maps to Testomatio's custom-fields API
-
-**Available for:**
-- `create_test` and `update_test` - Test custom fields
-- `create_suite` - Suite custom fields
-- `create_folder` - Folder custom fields
-
-#### Example Usage
-```javascript
-// Create a test with custom fields
+
+**Create test:**
+```json
 {
-  "tool": "create_test",
+  "name": "tests_create",
   "arguments": {
+    "title": "User login test",
     "suite_id": "123",
-    "title": "Login Test",
-    "fields": {
-      "priority": "high",
-      "severity": "critical",
-      "team": "backend"
-    }
+    "priority": "high"
   }
 }
+```
 
-// Update a test with label:value syntax
+**Create run:**
+```json
 {
-  "tool": "update_test",
+  "name": "runs_create",
   "arguments": {
-    "test_id": "456",
-    "labels_ids": ["priority:high", "severity:critical"]
+    "title": "Smoke tests",
+    "kind": "automated",
+    "env": "production"
   }
 }
 ```
 
-#### Test Runs
-* `get_runs` – List all runs (no params) — api: GET `/runs`
-* `get_run` – Get one run (params: `run_id`, `tree`) — api: GET `/runs/{run_id}`
-* `get_testruns` – Runs for a test (params: `test_id`, `finished_at_date_range`) — api: GET `/testruns`
-
-#### Test Plans
-* `get_plans` – List all plans (params: `detail`, `labels`, `page`) — api: GET `/plans`
-* `get_plan` – Get one plan (params: `plan_id`) — api: GET `/plans/{plan_id}`
-
-## Example Usage in Cursor
-
-Once configured, you can ask your AI assistant questions like:
-
-- "Show me all the tests in the project"
-- "Get details for test ID Ta1b2c3d4"
-- "Get the test runs for test ID Ta1b2c3d4"
-- "What are the root suites in this project?"
-- "Show me details for test run xyz789"
-- "List all automated tests with the @smoke tag"
-- "Get all test plans for this project"
-- "Create a new test called 'Login validation' in suite Sx9y8z7w6"
-- "Update test Ta1b2c3d4 to change its description and add @regression tag"
-- "Create a test with custom fields: priority='high', severity='critical', team='backend'"
-- "Update test Tb2c3d4e5 to set custom fields for risk score and assigned team"
-- "Create a new suite called 'Authentication Tests' with description 'All login and signup related tests'"
-- "Create a suite with custom fields for team ownership and priority level"
-- "Create a folder called 'API Tests' to organize API-related test suites with custom fields"
-- "Create a label called 'Severity' with color '#ffe9ad' and predefined values like 'Blocker', 'Critical', 'Major', 'Minor', 'Normal', 'Trivial'"
-
-## Query Patterns
-
-### Basic Information Queries
-
-These queries retrieve general information without specific filtering:
-
-- **"Show me all the tests in the project"** → `get_tests` tool
-- **"What are the root suites in this project?"** → `get_root_suites` tool  
-- **"Get all test runs"** → `get_runs` tool
-- **"Get all test plans for this project"** → `get_plans` tool
-
-### Test Management Queries
-
-These queries allow creating and updating tests:
-
-- **"Create a new test called 'Login validation' in suite Sx9y8z7w6"** → `create_test` tool with `title: "Login validation"`, `suite_id: "Sx9y8z7w6"`
-- **"Update test Ta1b2c3d4 to change its description"** → `update_test` tool with `test_id: "Ta1b2c3d4"`, `description: "new description"`
-- **"Create an automated test with @smoke tag"** → `create_test` tool with `state: "automated"`, `tags: ["smoke"]`
-- **"Create a test with custom fields: priority='high', severity='critical'"** → `create_test` tool with `title: "Test Title"`, `suite_id: "Sx9y8z7w6"`, `fields: { "priority": "high", "severity": "critical" }`
-- **"Update test Tb2c3d4e5 to set custom fields for risk score and team"** → `update_test` tool with `test_id: "Tb2c3d4e5"`, `fields: { "risk_score": "8.5", "team": "backend" }`
-
-### Suite and Folder Management Queries
-
-These queries help organize your test structure:
-
-- **"Create a new suite called 'Authentication Tests'"** → `create_suite` tool with `title: "Authentication Tests"`
-- **"Create a suite for login tests with description"** → `create_suite` tool with `title: "Login Tests"`, `description: "All login related test cases"`
-- **"Create a suite with custom fields for team ownership and priority level"** → `create_suite` tool with `title: "Backend Tests"`, `fields: { "team": "backend", "priority": "high" }`
-- **"Create a folder called 'API Tests' under parent suite Sx9y8z7w6"** → `create_folder` tool with `title: "API Tests"`, `parent_id: "Sx9y8z7w6"`
-- **"Create a folder with custom fields for team and project"** → `create_folder` tool with `title: "Integration Tests"`, `fields: { "team": "qa", "project": "mobile-app" }`
-- **"Create a test suite for payment features"** → `create_suite` tool with `title: "Payment Features", description: "Tests covering payment processing"`
-- **"Create a folder to organize integration tests"** → `create_folder` tool with `title: "Integration Tests"`
-
-**Note**: Suites can only contain other suites, while folders can contain both suites and folders (but no tests).
-
-### Label Creation Queries
-
-These queries help create custom labels for better test categorization:
-
-- **"Create a label called 'Severity' with red color"** → `create_label` tool with `title: "Severity"`, `color: "#ff6b6b"`
-- **"Create a severity label with predefined values"** → `create_label` tool with `title: "Severity"`, `color: "#ffe9ad"`, `field: { "type": "list", "short": true, "value": "Blocker\nCritical\nMajor\nNormal\nMinor\nTrivial" }`
-- **"Create a simple label for test types"** → `create_label` tool with `title: "Test Type"`, `scope: ["tests", "suites"]`
-- **"Create a label visible in test lists"** → `create_label` tool with `title: "Category"`, `visibility: ["list"]`
-
-### Specific Item Queries
-
-These queries target specific entities by ID:
-
-- **"Get details for test ID Ta1b2c3d4"** → `get_test` tool with `test_id: "Ta1b2c3d4"`
-- **"Get test runs for test ID Ta1b2c3d4"** → `get_testruns` tool with `test_id: "Ta1b2c3d4"`
-- **"Show me details for test run xyz789"** → `get_run` tool with `run_id: "xyz789"`
-- **"Get suite details for suite Sx9y8z7w6"** → `get_suite` tool with `suite_id: "Sx9y8z7w6"`
-
-### Search and Filter Queries
-
-These queries use advanced filtering capabilities:
-
-- **"List all automated tests with the @smoke tag"** → `search_tests` tool with `query: "@smoke"`, `state: "automated"`
-- **"Search for tests containing 'login'"** → `search_tests` tool with `query: "login"`
-- **"List tests tagged @critical or labelled 'ux' with critical severity"** → `search_tests` tool with `tql: "tag == 'critical' or label == 'ux' and severity == 'critical'"`
-- **"Find tests linked to JIRA-123"** → `search_tests` tool with `tql: jira == 'BDCP-2'`
-
-### Advanced Query Syntax
-
-#### Test Query Language (TQL)
-
-The `search_tests` tool supports TQL for complex filtering:
-
-```
-"tag == 'smoke' and state == 'manual'"
-"severity == 'critical' or label == 'ux'"
+**Finish run:**
+```json
+{
+  "name": "runs_update",
+  "arguments": {
+    "run_id": "456",
+    "status_event": "finish"
+  }
+}
 ```
 
-#### Tag-Based Searches
-
-Tags can be searched using the `@` prefix:
-
-```
-@smoke        # Tests tagged with 'smoke'
-@regression   # Tests tagged with 'regression'
-@critical     # Tests tagged with 'critical'
-```
+## Documentation
 
-#### Jira Integration
+Complete tool reference: [docs/tools.md](./docs/tools.md)
 
-Tests linked to Jira issues can be found using issue keys:
+## Project Structure
 
 ```
-JIRA-123      # Tests linked to JIRA-123
-PROJ-456      # Tests linked to PROJ-456
+src/
+├── config/          # Config loading, defaults
+├── core/            # Errors, logger
+├── api/             # HTTP client, Testomat.io API client
+├── mcp/             # MCP server, tools, registry
+│   ├── definitions/ # Tool definitions by entity
+│   ├── configs/     # Registry generation configs
+│   └── registry/    # Tool handlers
+└── cli/             # CLI bootstrap
 ```
 
-## Troubleshooting
-
-### Common Issues
-
-1. **"API token is required" error**
-   - Make sure your token starts with `testomat_`
-   - Verify the token is correct in your Testomat.io project settings
-
-2. **"Project ID is required" error**
-   - Check that you're passing the correct project ID
-   - Verify the project ID exists and you have access to it
-
-3. **Connection errors**
-   - Ensure you have internet connectivity
-   - Check if your firewall allows connections to `app.testomat.io`
-   - Verify your API token has the necessary permissions
-
-4. **MCP server not starting in Cursor**
-   - Check Cursor's MCP logs for error messages
-   - Ensure Node.js 18+ is installed and accessible
-   - Try running the command manually first to test
-
-### Debug Mode
-
-To see detailed logs when running the server:
-
-```bash
-DEBUG=* npx @testomatio/mcp --token <token> --project <project-id>
-```
+## Environment Variables
 
-## API Reference
+| Variable | Required | Default | Description |
+|----------|----------|---------|-------------|
+| `TESTOMATIO_PROJECT_TOKEN` | Yes* | - | Project token (preferred) |
+| `TESTOMATIO_API_TOKEN` | Yes* | - | Alternative token |
+| `TESTOMATIO_PROJECT_ID` | Yes | - | Project ID |
+| `TESTOMATIO_BASE_URL` | No | `https://app.testomat.io` | API base URL |
 
-For detailed information about the underlying Testomat.io API, refer to the [Testomat.io API Documentation](https://app.testomat.io/docs/api/).
+*Either `TESTOMATIO_PROJECT_TOKEN` or `TESTOMATIO_API_TOKEN`
 
-## Contributing
+## Important Notes
 
-Contributions are welcome! Please feel free to submit a Pull Request.
+- **Run Status** - Use `runs_update` with `status_event` for transitions (finish, launch, rerun, etc.)
+- **Search** - No dedicated `/search` endpoints; search uses list with filters
+- **Issue Linking** - Scoped helpers available: `{entity}_issues_link/unlink`
 
-### Development Setup
+## Development
 
 ```bash
-# Clone the repository
-git clone https://github.com/testomatio/mcp.git
-cd mcp
-
-# Install dependencies
 npm install
-
-# Run unit tests
-npm test
-
-# Run integration tests (requires environment variables)
-npm run test:integration
-
-# Run all tests
-npm run test:all
-```
-
-### Testing
-
-The project includes comprehensive test coverage:
-
-- **Unit Tests**: Fast tests with mocked dependencies
-- **Integration Tests**: Real API tests against Testomat.io
-
-#### Running Tests Locally
-
-```bash
-# Unit tests only
-npm run test:unit
-
-# Integration tests (requires .env file)
-npm run test:integration
-
-# With coverage
-npm run test:coverage
-npm run test:coverage:integration
+npm run start -- --token <TOKEN> --project <PROJECT_ID>
 ```
-
-#### Environment Setup for Integration Tests
-
-Create a `.env` file:
-
-```bash
-TESTOMATIO_API_TOKEN=testomat_your_token_here
-TESTOMATIO_PROJECT_ID=your_project_id
-TESTOMATIO_BASE_URL=https://app.testomat.io  # optional
-```
-
-### CI/CD
-
-This project uses GitHub Actions for continuous integration:
-
-- ✅ **Unit Tests**: Run on every push/PR across Node.js 18, 20, 22
-- ✅ **Integration Tests**: Run daily and on main branch merges
-- ✅ **Coverage Reports**: Automatic upload to Codecov
-- ✅ **Security**: Secrets management for API credentials
-
-
-### Code Quality
-
-- Follow existing code style patterns
-- Add tests for new functionality
-- Update documentation when needed
-- Ensure all tests pass before submitting PRs
-
-## License
-
-This project is licensed under the MIT License - see the LICENSE file for details.
-
-## Support
-
-For support, please:
-1. Check the [Testomat.io Documentation](https://docs.testomat.io)
-2. Open an issue on GitHub
-3. Contact Testomat.io support
-
-## Changelog
-
-### v1.0.0
-- Initial release
-- Support for all major Testomat.io API endpoints
-- MCP-compatible tool interface
-- Semantic XML formatting for LLM processing