Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MELOQA_BASE_URLNoBase URL of the meloQA instance. Override to point at another deployment (e.g. http://localhost:3000).https://api.meloqa.com
MELOQA_API_TOKENYesAPI token sent as Authorization: Bearer <token>.
MELOQA_RATE_LIMITNoClient-side limit (requests/minute) used to throttle outgoing calls. Match the server's limit.30

Capabilities

Features and capabilities supported by this server

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
bug_environments_listB

List environments for a project

Tag: Bug Environments

bug_folders_createD

Create bug folder

Tag: Bug Folders

bug_folders_deleteC

Delete bug folder

Tag: Bug Folders

bug_folders_getB

Get bug folder by ID

Tag: Bug Folders

bug_folders_listC

List bug folders

Tag: Bug Folders

bug_folders_updateC

Update bug folder

Tag: Bug Folders

bug_priorities_listA

List all bug priority levels

Tag: Bug Priorities

bug_statuses_listA

List all bug statuses

Tag: Bug Statuses

bug_types_listB

List bug types for a project

Tag: Bug Types

bugs_attachments_createA

Create bug attachment (returns presigned upload URL)

Tag: Bug Attachments

Cria o registro do anexo (uploaded=false) e retorna uma presigned URL S3 (PUT, 300s). Faça o PUT do arquivo na uploadUrl e depois confirme com PATCH /v1/bugs/:id/attachments/:attachmentId.

bugs_attachments_deleteA

Delete bug attachment

Tag: Bug Attachments

Remove o anexo (registro + arquivo no S3).

bugs_attachments_listA

List bug attachments

Tag: Bug Attachments

Lista os anexos do bug. Itens com uploaded=true trazem downloadUrl (presigned, 300s).

bugs_attachments_updateA

Confirm bug attachment upload

Tag: Bug Attachments

Marca o anexo como enviado (uploaded=true) após o PUT no S3.

bugs_createC

Create bug

Tag: Bugs

bugs_deleteC

Delete bug

Tag: Bugs

bugs_getA

Get bug by ID

Tag: Bugs

bugs_listB

List bugs

Tag: Bugs

At least one query parameter is required: projectId or folderId.

bugs_updateD

Update bug

Tag: Bugs

cycle_folders_createD

Create cycle folder

Tag: Cycle Folders

cycle_folders_deleteC

Delete cycle folder

Tag: Cycle Folders

cycle_folders_getB

Get cycle folder by ID

Tag: Cycle Folders

cycle_folders_listC

List cycle folders

Tag: Cycle Folders

cycle_folders_updateC

Update cycle folder

Tag: Cycle Folders

cycle_statuses_listB

List all cycle statuses

Tag: Cycle Statuses

cycles_createD

Create cycle

Tag: Cycles

cycles_deleteC

Delete cycle

Tag: Cycles

cycles_getB

Get cycle by ID

Tag: Cycles

cycles_listA

List cycles

Tag: Cycles

At least one query parameter is required: projectId or folderId.

cycles_updateD

Update cycle

Tag: Cycles

executions_attachments_createA

Create execution attachment (returns presigned upload URL)

Tag: Execution Attachments

Cria o registro do anexo (uploaded=false) e retorna uma presigned URL S3 (PUT, 300s). Faça o PUT do arquivo na uploadUrl e depois confirme com PATCH /v1/executions/:id/attachments/:attachmentId.

executions_attachments_deleteB

Delete execution attachment

Tag: Execution Attachments

Remove o anexo (registro + arquivo no S3).

executions_attachments_listA

List execution attachments

Tag: Execution Attachments

Lista os anexos da execução. Itens com uploaded=true trazem downloadUrl (presigned, 300s).

executions_attachments_updateA

Confirm execution attachment upload

Tag: Execution Attachments

Marca o anexo como enviado (uploaded=true) após o PUT no S3.

executions_createC

Create execution

Tag: Executions

The state field is system-managed and is silently ignored if sent in the body. Use /v1/executions-run, /v1/executions-pause and /v1/executions-finish to drive transitions.

executions_deleteC

Delete execution

Tag: Executions

executions_finishA

Finish an execution

Tag: Executions

Sets the execution state to DONE and records executedAt and executedBy. Allowed only when the current state is IN_PROGRESS — returns 400 for WAITING, PAUSED or DONE, when its parent tests cycle is FINISHED, or when the execution's statusId is still "Em aberto" (NOT_EXECUTED) — a verdict must be set first.

executions_getC

Get execution by ID

Tag: Executions

executions_listC

List executions

Tag: Executions

executions_pauseA

Pause an execution

Tag: Executions

Sets the execution state to PAUSED. Allowed only when the current state is IN_PROGRESS — returns 400 for WAITING, PAUSED or DONE, or when its parent tests cycle is FINISHED.

executions_runA

Start running an execution

Tag: Executions

Sets the execution state to IN_PROGRESS. Allowed only when the current state is WAITING or PAUSED. Returns 400 when the execution is already IN_PROGRESS or DONE, or when its parent tests cycle is FINISHED.

executions_updateA

Update execution

Tag: Executions

Executions in state: DONE are read-only and cannot be updated through this endpoint (public V1 only — the internal API does not enforce this guard). The state field itself is system-managed and is silently ignored if sent in the body — use /v1/executions-run, /v1/executions-pause and /v1/executions-finish instead.

links_batch_createA

Link one entity to multiple entities at once

Tag: Links

Creates one record per target. Operation is atomic — if any record fails, none are created. Paid-plan only: free-plan organizations receive 403.

links_createA

Create a link between two entities

Tag: Links

Creates a directional link between two entities.

entityA is the entity currently open or being edited — its ID is stored in the corresponding foreign key field. entityB is the entity being linked to entityA — its type is stored in type and its ID in meloQaLinkedId.

Example use case: A user is editing a bug and opens the link panel to attach a test case. To replicate this action via the API, set entityAType to bug and entityAId to the ID of the open bug, then set entityBType to test-case and entityBId to the ID of the selected test case.

The same logic applies regardless of which entity type is open: always pass the entity being viewed as entityA and the entity being attached as entityB.

Paid-plan only: this endpoint requires the organization to have an active subscription. Free-plan organizations receive 403.

links_deleteB

Remove a link

Tag: Links

Paid-plan only: free-plan organizations receive 403.

links_listA

List links for an entity

Tag: Links

Returns all entities linked to the given entity, regardless of which side of the link it was created from.

Example use case: A user opens a bug and the UI needs to display its linked items panel. Pass entityType=bug and entityId as the ID of the open bug to retrieve all entities attached to it.

The response includes links where the given entity appears as either entityA (the entity that was open when the link was created) or entityB (the entity that was attached). Both directions are returned in a single call.

location_countries_listA

List all location countries

Tag: Location Countries

organizations_getB

Get organization by ID

Tag: Organizations

organizations_listC

List organizations

Tag: Organizations

organizations_members_listC

List members of an organization

Tag: Organizations

organizations_updateC

Update organization

Tag: Organizations

The employeeQuantity field accepts one of the following values: 1 a 10, 11 a 50, 51 a 100, 100+. Send null to clear the value.

project_pictures_listB

List available project pictures

Tag: Projects

project_platforms_listB

List platforms for a project

Tag: Project Platforms

projects_createC

Create project

Tag: Projects

Validation rules:

  • name must not exceed 20 characters.

  • description must not exceed 250 characters.

  • projectPictureUrl must reference a project picture predefined by the meloQA API — list the available IDs via GET /v1/project-pictures.

projects_deleteB

Delete project

Tag: Projects

projects_execution_statuses_listA

List execution statuses available in a project

Tag: Projects

Returns the execution statuses that can be assigned to executions in this project. Includes both the system-wide defaults (projectId: null, isDefault: true) and any project-specific statuses created for it. Use the id of an entry as statusId when creating or updating an execution.

projects_getB

Get project by ID

Tag: Projects

projects_listA

List projects

Tag: Projects

Returns only projects the authenticated user has effective access to (i.e. is a project member of).

projects_members_listA

List members of a project

Tag: Projects

Returns the active (non-deleted) members of the project. The caller must be a member of the project.

projects_test_case_custom_fields_listA

List custom field definitions for test cases of a project

Tag: Projects

Returns the custom field schema configured for test cases in the project. Use the id of each entry as projectCustomFieldId when reading or writing test case custom field values.

projects_updateB

Update project

Tag: Projects

Validation rules:

  • name must not exceed 20 characters.

  • description must not exceed 250 characters.

  • projectPictureUrl must reference a project picture predefined by the meloQA API — list the available IDs via GET /v1/project-pictures.

tags_createC

Create tag

Tag: Tags

tags_deleteC

Delete tag

Tag: Tags

tags_getB

Get tag by ID

Tag: Tags

tags_listC

List tags

Tag: Tags

tags_updateC

Update tag

Tag: Tags

test_case_folders_createB

Create test case folder

Tag: Test Case Folders

Folder hierarchy is limited to 3 sub-levels below the project root. Creating a folder under a parent that is already at the 3rd sub-level returns 400.

test_case_folders_deleteA

Delete test case folder

Tag: Test Case Folders

Removes the folder and hard-deletes every test case it contained, matching the meloQA front-end behavior. Child folders are removed in the same operation.

test_case_folders_getB

Get test case folder by ID

Tag: Test Case Folders

test_case_folders_listC

List test case folders

Tag: Test Case Folders

test_case_folders_updateA

Update test case folder

Tag: Test Case Folders

When parentId is changed, the folder is moved together with its whole subtree. The resulting hierarchy must not exceed 3 sub-levels below the project root — otherwise the request is rejected with 400.

test_case_statuses_listB

List all test case statuses

Tag: Test Case Statuses

test_case_types_listB

List all test case types

Tag: Test Case Types

test_cases_archived_listA

List archived test cases

Tag: Test Cases

Returns only archived test cases (statusId === ARCHIVED). At least one of projectId or folderId is required.

test_cases_attachments_createB

Create test case attachment (returns presigned upload URL)

Tag: Test Case Attachments

Cria o registro do anexo (uploaded=false) e retorna uma presigned URL S3 (PUT, 300s). Faça o PUT do arquivo na uploadUrl e depois confirme com PATCH /v1/test-cases/:id/attachments/:attachmentId.

test_cases_attachments_deleteA

Delete test case attachment

Tag: Test Case Attachments

Remove o anexo (registro + arquivo no S3).

test_cases_attachments_listA

List test case attachments

Tag: Test Case Attachments

Lista os anexos do test case. Itens com uploaded=true trazem downloadUrl (presigned, 300s).

test_cases_attachments_updateB

Confirm test case attachment upload

Tag: Test Case Attachments

Marca o anexo como enviado (uploaded=true) após o PUT no S3.

test_cases_createC

Create test case

Tag: Test Cases

test_cases_deleteC

Delete test case

Tag: Test Cases

test_cases_getC

Get test case by ID

Tag: Test Cases

test_cases_listA

List test cases

Tag: Test Cases

At least one query parameter is required: projectId or folderId. Archived test cases (statusId === ARCHIVED) are excluded — use GET /v1/test-cases/archived to list those.

test_cases_unarchiveA

Unarchive test case

Tag: Test Cases

Restores an archived test case (statusId === ARCHIVED) into the folder specified by folderId. The status returns to whatever it was before archiving (statusBeforeId); when no previous status is recorded the test case falls back to FINISHED.

test_cases_updateC

Update test case

Tag: Test Cases

Archived test cases (statusId === ARCHIVED) are read-only and cannot be updated through this endpoint.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/swl-informatica/meloQA-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server