Tekst MCP Troubleshooting

This article covers common issues you may encounter when using the Tekst MCP integration, and how to resolve them.

Authentication issues

"Unable to connect" or login page does not appear

• Make sure you are using an MCP-compatible AI client (such as Claude or Microsoft Copilot Studio).
• Check that your browser allows pop-ups, as the authentication flow opens a login page in your browser.
• Try disconnecting and reconnecting the integration from your AI client's settings.

Session expired

Your Tekst MCP session expires after 30 minutes of inactivity. If your AI assistant reports that it cannot access your Tekst data, start a new conversation or reconnect the integration. Your client will prompt you to re-authenticate if needed.

Wrong workspace

The MCP session is locked to the workspace you authenticated with. If you need to access a different workspace, disconnect the integration and reconnect using credentials for the desired workspace.

Data access issues

"Tool not found" or missing tools

If your AI assistant reports that certain Tekst tools are unavailable, verify that:

• The Tekst integration is still connected in your client's settings.
• Your session has not expired (see above).
• You have the necessary permissions in your Tekst workspace to access the requested data.

Empty results

If your assistant returns empty results when querying your data:

• Confirm that the data exists in your Tekst workspace by checking the Tekst platform directly.
• For analytics queries, make sure you are asking about a time range that contains data.
• For process mining tools, verify that the process is not in draft status if you expect it to have data.

Permission errors

The tools available to you depend on your role in the Tekst workspace. If you receive a permission error, check with your workspace administrator to confirm your access level.

Analytics query issues

Query errors

When your AI assistant runs analytics queries on your behalf, errors can occur if:

• The query references a column or table that does not exist. Ask your assistant to call the describe tables tool first to check the schema.
• The query is missing a time filter. Analytics queries require filtering on a date or timestamp column.

Unexpected query results

If query results seem incorrect:

• Ask your assistant to show you the SQL query it used so you can verify the logic.
• Ask your assistant to sample the table first to understand the data format before running complex queries.

Connection issues in Claude Code

Command not recognized

Make sure you have the latest version of Claude Code installed. Update by running:

npm install -g @anthropic-ai/claude-code@latest

Authentication fails in terminal

If the browser-based authentication does not complete successfully:

• Make sure your default browser is set correctly.
• Try running the command again - the authentication flow will restart.
• Check that no firewall or proxy is blocking the connection to mcp.tekst.com.

Connection issues in Microsoft Copilot Studio

Tools are not appearing

Make sure Generative Orchestration is enabled on your agent. MCP tools require this setting to be active in Copilot Studio.

Dynamic discovery fails

If the dynamic discovery OAuth option does not work, try the Dynamic or Manual OAuth configuration instead. See the Copilot Studio connection guide for detailed steps.

Getting help

If you continue to experience issues with the Tekst MCP integration:

• Contact Tekst support at support@tekst.com
• Include details about the AI client you are using, the error message you received, and the steps you took before the error occurred.