# biaws-mcp

Source: https://glimind.com/server/npm%2Fbiaws-mcp
Registry id: `npm/biaws-mcp`
Status: unknown

## Install

```json
{
  "mcpServers": {
    "biaws-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "biaws-mcp"
      ]
    }
  }
}
```

Claude Code:

```sh
claude mcp add biaws-mcp -- npx -y biaws-mcp
```

## Tools (61)

- `applications_monitoring_health_get`: Get consolidated health of an application.
- `attachments_delete`: Permanently delete attachment record and its.
- `attachments_download`: Return name, MIME type, size, and full content.
- `attachments_update_tags`: Replace classification tags of the file.
- `attachments_upload`: Upload up to ten files provided in.
- `audit_events_list`: Query recent events of an entity.
- `demands_add_note`: Add a note to an improvement.
- `demands_add_task_note`: Add an execution note to a task.
- `demands_create`: Create an improvement with registration data, specification.
- `demands_create_task`: Include a task.
- `demands_deadlines`: Consolidate deadlines and status per improvement.
- `demands_delete_note`: Permanently delete a note from the improvement.
- `demands_delete_task`: Delete a task.
- `demands_delete_task_note`: Delete an execution note.
- `demands_get`: Get a structured improvement.
- `demands_implementation_context`: Extract specification and task context for dev agents.
- `demands_journey_calendar`: Consolidate planned and executed journeys per month.
- `demands_list`: List a page of improvements; page defaults to 1.
- `demands_list_tasks`: List tasks with optional status filter.
- `demands_update`: Update code, title, description, status, deadlines, estimate.
- `demands_update_checklist`: Replace all checklist items including.
- `demands_update_description`: Update the brief description of the improvement.
- `demands_update_journeys`: Replace monthly journey planning.
- `demands_update_note`: Update note content and optionally date.
- `demands_update_specification`: Replace all specification sections.
- `demands_update_task`: Update code, title, status, dates, situation, description, specification.
- `demands_update_task_note`: Update an execution note.
- `demands_update_task_status`: Change only the status of a task.
- `document_types_list`: Query official contract of each type including.
- `documents_add_observation`: Add an immutable observation.
- `documents_create`: Create rules, decisions, guidelines, features, references.
- `documents_update`: Update content, context, and metadata preserving.
- `issues_add_comment`: Add a Markdown comment to an issue.
- `issues_aggregate`: Return a specific aggregation.
- `issues_analyze_eml_file`: Analyze an EML file without persisting.
- `issues_by_taxonomy`: Search issues by subject/taxonomy including all.
- `issues_classify`: Write classification/KB into issues.classification.
- `issues_create`: Create a manual issue with origin mcp; applicationId required.
- `issues_create_taxonomy_item`: Add a taxonomy item at root or under another.
- `issues_delete_comment`: Permanently delete a comment.
- `issues_get`: Get an issue with comments and attachment metadata.
- `issues_get_classification_catalog`: Get taxonomic tree and valid tag groups.
- `issues_import_eml`: Analyze or import a Base64 EML; dryRun defaults true.
- `issues_import_eml_file`: Validate SHA-256 and analyze/import file from path.
- `issues_search`: Search issues with main filters.
- `issues_suggest_taxonomy`: Legacy lexical search; main flow uses agent analysis.
- `issues_summary`: Return aggregates by day, week, month, year, type, status, taxonomy.
- `issues_update`: Update title, text, type, status, application, components.
- `issues_update_comment`: Update comment content and optionally date.
- `issues_update_state`: Change status and/or type of an issue.
- `issues_update_taxonomy_item`: Change name or scope by applications.
- `knowledge_context_load`: Load active rules and accepted decisions for context.
- `monitoring_templates_archive`: Archive an unused version per policy.
- `monitoring_templates_preview`: Test a definition with a JSON sample without persisting.
- `monitoring_templates_validate`: Evaluate a sample against a persisted version.
- `resource_collections_create`: Create a collection at root or under another collection.
- `resource_collections_delete`: Delete only an empty collection.
- `resource_collections_update`: Rename or reparent a collection.
- `runtime_monitoring_signals_list`: List passive/external signals per runtime.
- `secrets_list`: List metadata with filters by application, environment, state.
- `secrets_register`: Register a secret need with identification.

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.