Get a list of available workflow templates/pipelines that can be started. Returns: List of pipeline templates with their required header schemas. Note: Always use the 'id' field (and not the legacy 'pipeline_id' field) to start a process or archive a pipeline.

Start a new workflow process under a template. template_id: UUID of the workflow template (MUST use the 'id' field from list_pipelines, NOT 'pipeline_id'). payload: Input data matching the template's header_schema. Returns: The started process ID and initial status.

List all processes visible to the member (filtered by backend per role). status: Filter by status: 'active', 'completed', 'rejected', 'failed'. pipeline_id: Filter by pipeline template UUID (use the 'id' field from list_pipelines). limit: Max results to return (default: 50, max: 200). offset: Pagination offset (default: 0). NOTE: Pagination is server-side; the list may be incomplete if total > limit.

List pending approval requests waiting for this member's decision. Includes the available_actions list for each request so you know valid statuses. limit: Max results to return (default: 50, max: 200). offset: Pagination offset (default: 0). NOTE: Pagination is server-side; the list may be incomplete if total > limit.

Fetch detailed status, current node states, and context variables of a specific process. process_id: UUID of the process. verbose: If True, returns full process structure including pipeline_config and display_all_data. If False (default), returns a compact representation with context variables but config omitted.

Fetch detailed request information, including audit history, context payload, and available_actions. Always call this before submit_decision to know which action values are valid for this request. request_id: UUID of the pending approval request.

Submit a decision on a pending approval request. request_id: UUID of the pending approval request. status: MUST be one of the values from available_actions returned by get_request_details. Always call get_request_details first to obtain valid action IDs. comment: Optional explanation for the decision (recommended for audit trail).

Sync members of the organization. data: List of members mapping to the onboarding structure.

Create a new workgroup (DEPARTMENT, LOCATION, etc.) in the organization. name: Name of the workgroup. type: 'DEPARTMENT', 'LOCATION', or 'SQUAD'. parent_id: Optional parent workgroup UUID. key: Optional unique workgroup key.

Delete a workgroup from the organization structure. workgroup_id: UUID of the workgroup to delete.

List all registered global custom fields in the organization. Returns: A list of custom fields with their ID, name, label, type, validation, and options.

Create a custom metadata field for workflows. name: Identifier name (alphanumeric/snake_case). label: Human readable display label. type: Field type (e.g. 'text', 'number', 'select', 'date'). description: Optional details. validation: Optional regex/constraint config dictionary. options: Optional choice list for select fields. is_active: True if field is enabled.

Delete a custom field from the system. field_id: UUID of the custom field to delete.

Create a new supplier/vendor profile. name: Name of the vendor. email: Primary email. account_number: Bank account number. bank_country_code: country code. financial_details: List of financial settings/details for invoicing.

Delete a vendor from accounting records. vendor_id: UUID of the vendor.

Deactivate/archive a workflow pipeline template. template_id: UUID of the template (MUST use the 'id' field from list_pipelines, NOT 'pipeline_id').

Resolve (approve or reject) a pending MCP human-in-the-loop (HITL) transaction. action: MUST be 'approve' or 'reject'. approval_id: UUID of the pending approval (optional, exactly one of approval_id or token is required). token: Raw token string from the pending approval response (optional). session_key: Operator's active session key. If not provided, defaults to COLBA_TOKEN.

Get the official specification, validation rules, node type hierarchies, and schema guidelines for generating new Colba workflow pipeline JSON configurations. Returns: Complete Markdown specification text to guide pipeline JSON creation.

Create a new workflow pipeline template in Colba. name: Human readable template name (e.g. 'Vendor Invoice Approval'). pipeline_config: Complete JSON workflow configuration complying strictly with docs://skills/workflow_json_creation specification. Must contain start_node_id and valid nodes list. Call get_pipeline_generation_rules tool first to inspect the required format. description: Optional human-readable description. Returns: Created pipeline template details including template_id.

List all active members (users/employees) in the organization. query: Optional search string to filter members by full name. Returns: A list of members with their IDs, names, emails, roles, and status.

List the organizational workgroups hierarchy (departments and locations). Returns: A tree structure of workgroups with their member details and counts.

List all registered vendors/counterparties in the organization. Returns: A list of vendors with their IDs, names, and profiles.

Update an existing workflow pipeline template. template_id: UUID of the template to update. pipeline_config: Optional updated JSON workflow configuration. name: Optional updated name. description: Optional updated description.

Update an existing custom field / global field registration. field_id: UUID of the custom field to update. name: Optional system name. label: Optional display label. type: Optional field type. description: Optional description. validation: Optional validation schema. options: Optional dropdown options or dynamic source settings. is_active: Optional active status.

Retrieve the Colba MCP Server Update Log and Changelog. Contains lists of new tools, changes, and alerts about required client restarts.

List all available workflow pipeline blueprints that can be instantiated. category: Optional category filter (e.g. 'finance', 'hr', 'it'). query: Optional search query. Returns: A list of blueprints with their details and base configurations.

Retrieve the full configuration of a specific pipeline blueprint. blueprint_id: UUID of the blueprint. Returns: Complete blueprint details including its pipeline_config baseline.

Create a new pipeline template in the current organization based on a blueprint. blueprint_id: UUID of the blueprint to instantiate. Returns: Status of the instantiation and the created template_id (requires approval).