Available Tekst MCP Tools

This article lists the tools available through the Tekst MCP server. Your AI assistant uses these tools to retrieve and analyze data from your Tekst workspace.

Users

• List Users - Lists all members of the workspace, including their email addresses and roles. Returns summary fields only. Supports pagination.

AI models

• List Models - Lists all AI models in your workspace (classification and extraction), including their names and statuses. Returns summary fields only - use Get Model for full information. Supports pagination.

• Get Model - Returns detailed information about a specific AI model. For classification models, the response includes the model's labels (tags). For extraction models, it includes the model's entities. The modelKind field indicates which type was returned.

Integrations

• List Integrations - Lists all active data source integrations (such as Zendesk, Salesforce, Gmail, and others), including their names and types. Returns summary fields only - use Get Integration for full information. Supports pagination.

• Get Integration - Returns configuration and sync status for a specific integration.

Process mining

• List Processes - Lists all active process mining processes (discovered workflows such as ticket handling or order fulfillment), including their names, draft status, linked integrations, and throughput time target. Supports pagination.

• Get Process Activities - Lists all activities (steps) discovered in a specific process. Activities can be classification-based (extracted from message content) or system-based (such as tag added or thread closed). Returns each activity's name, type, visibility status, occurrence count, and an optional description. Also indicates whether each activity was manually added - only manually added activities can be removed. Supports pagination.

• Get Process Graph - Returns details for a specific process, including name, draft status, connected integrations, number of discovered variants, and throughput time target. Use Get Process Graph Paths to retrieve the actual variant paths with per-edge metrics.

• Get Process Graph Paths - Returns individual paths (variants) through a process. Each path includes the sequence of activities, case frequency, and throughput time statistics per edge. Supports filtering by time range and integration, and sorting by case frequency, throughput time, or path length. Returns a link to view the variant in the Tekst UI when available.

• Get Process Totals - Returns aggregate KPIs across all processes, including total case frequency, average throughput time, and the number of paths meeting the throughput time target. Supports time-range filtering.

Analytics

• Describe Analytics Tables - Returns the schema (column names, ClickHouse types, and descriptions) for all available analytics tables. Tables must always be prefixed with analytics. in queries (for example, analytics.mcp_threads). Always call this before running a query to confirm which columns and types exist. When aggregating data, always include a filter on thread_time, message_created_at, or day to limit the time range and avoid slow or timed-out queries.

• Query Analytics - Executes a read-only SQL query against the ClickHouse analytics database. Tables must be prefixed with analytics. (for example, analytics.mcp_threads). Always include a filter on thread_time, message_created_at, or day when aggregating data - queries without a time filter may be slow or time out. Column metadata (types, constraints, and guardrails) is only available from Describe Analytics Tables - sampling rows does not expose this information. Use this to answer custom questions about your ticket data, message volumes, and automation performance.

• Sample Analytics Table - Returns a sample of rows from one of the core analytics tables (mcp_threads, mcp_messages, or mcp_automation_block_runs) so you can inspect the data before writing a query. Sampling rows does not replace calling Describe Analytics Tables - always describe the schema before running a query.

Automations

• List Automations - Lists all automation flows in your workspace, including their names and running status. Returns summary fields only - use Get Automation for full information. Supports pagination.

• Get Automation - Returns full details for a specific automation flow, including its blocks (steps), creator, connected integrations, and aggregate success/failure stats over a recent time window.

• Get Automation Monitor - Returns the execution history for a specific automation flow. Each entry represents a thread run with its status and block results. Supports filtering by block and status, with pagination.

• Get Automation Run - Returns detailed information about a single automation run, including individual block results, the integration, and the thread involved. Use Get Automation Monitor first to find run IDs.

• List Available Block Types - Lists all block types that can be used when building an automation flow. Use minimal detail for a quick overview (type, name, description, and branching shape) or full detail to also include configuration schemas. You can also filter to specific block types.

• List Available Actions - Lists actions available for an automation flow or a specific integration, including any custom actions. Provide flow_id to list all actions for an existing automation (preferred), or integration_id to browse actions before creating one. Also supports filtering by search query. Use Get Action Schema to retrieve the full parameter details for any listed action.

• Get Action Schema - Returns the parameter schema for a specific integration action or custom action, including what inputs are required, what values are valid, and what outputs the action produces. For integration actions, provide action_id along with flow_id or integration_id. For custom actions, provide app_id instead.

• Get Condition Schema - Returns the condition group schema, valid variables, and operators for building condition blocks in an automation flow. Includes guidance on choosing AND vs. OR logic for condition groups.