Skip to main content
Use this guide when a Microsoft Copilot Studio agent should search TextMine Vaults, ask questions over documents, inspect business records, or create and follow task-agent work. TextMine is exposed to Copilot Studio through the hosted TextMine MCP server. The MCP server is backed by Public API V3, so the agent acts with the same TextMine permissions as the API key used for the connection. Microsoft supports two setup paths for existing MCP servers in Copilot Studio:
  • Recommended: add the TextMine MCP server with Copilot Studio’s MCP onboarding wizard.
  • Fallback: create a Power Platform custom connector in Power Apps and import an OpenAPI 2.0 wrapper for the TextMine MCP endpoint.

​
Which setup path should I use?

SituationUse this path
The agent’s Tools page shows New tool > Model Context ProtocolUse the MCP onboarding wizard in Copilot Studio.
A TextMine MCP connector already exists in the same Power Platform environmentAdd the existing Model Context Protocol connector to the agent.
Model Context Protocol is not available under New toolCreate the custom connector in Power Apps, then add it to the agent from Copilot Studio.
You need to connect a non-UK TextMine environmentUse the same path, but replace the host with the environment-specific TextMine MCP host.
Think of Copilot Studio as the place where the agent gets TextMine as a tool. Use Power Apps only when you need to create the fallback custom connector that Copilot Studio will later consume. For general Microsoft setup details, see Microsoft’s guides for connecting an existing MCP server to a Copilot Studio agent, adding MCP tools to an agent, using custom connectors in Copilot Studio agents, and creating a custom connector from an OpenAPI definition.

​
Before you start

You need:
  • Access to Microsoft Copilot Studio and the Power Platform environment where the agent lives.
  • Permission to create or use custom connectors in that environment if you need the fallback path.
  • A TextMine API key for the TextMine organization the agent should use. TextMine API keys use the tm_... format.
  • The TextMine MCP endpoint for the target environment.
  • Confirmation that any required TextMine features, Vaults, integrations, and task-agent email routes have been activated for that organization.
For public UK production, use: 
https://public-api.textmine.com/mcp
Some direct MCP clients may use the hosted app URL: 
https://app.textmine.com/mcp
For Copilot Studio and Power Platform custom connectors, use the environment’s public API host shape, such as https://public-api.textmine.com/mcp for UK production. For staging, US, BDO, or dedicated deployments, use the environment-specific MCP endpoint provided by TextMine. Store the TextMine API key only in the Copilot Studio or Power Platform connection. Do not paste it into agent instructions, prompts, chat transcripts, screenshots, or documentation. Use Copilot Studio’s MCP onboarding wizard when the Model Context Protocol option is available in your tenant.

​
Open the wizard

  1. Go to Copilot Studio.
  2. Select the same Power Platform environment that should contain the TextMine connection.
  3. Open the agent that should use TextMine.
  4. In the agent, open Tools.
  5. Select Add a tool.
  6. Select New tool.
  7. Select Model Context Protocol.
If Model Context Protocol appears, the MCP onboarding wizard opens. If it is not available, use the custom connector fallback.

​
Configure TextMine

In the MCP onboarding wizard, enter:
FieldValue
Server nameTextMine
Server descriptionSearch TextMine Vaults, ask document questions, inspect records, and create task-agent work.
Server URLhttps://public-api.textmine.com/mcp for UK production, or the TextMine endpoint for your environment
Authentication typeAPI key
API key typeHeader
Header nameX-TextMine-Api-Key
Then:
  1. Select Create.
  2. In the Add tool dialog, create a new connection or choose an existing TextMine connection.
  3. When prompted for the API key, enter the raw TextMine key value, for example tm_....
  4. Select Add to agent.
  5. Open the TextMine tool settings and review the tools discovered from the MCP server.

​
Add an existing TextMine MCP connector to an agent

If someone has already created the MCP connector in the same Power Platform environment:
  1. Open the agent in Copilot Studio.
  2. Go to Tools.
  3. Select Add a tool.
  4. Select Model Context Protocol.
  5. Choose the TextMine MCP connector from the list.
  6. Authorize or create the connection with the tm_... TextMine API key.
  7. Select Add and configure.
  8. Open the TextMine tool settings and confirm the available tools and resources.

​
Choose the tools to allow

Keep the first version of the agent focused. Start with read and task-management tools, then enable broader actions once the team has tested the agent’s behaviour. Useful starting tools include:
  • list_vaults
  • search_documents
  • fetch_document
  • get_document_text
  • get_document_metadata
  • ask_vault
  • list_record_schemas
  • get_schema_records
  • get_record
  • createTask
  • listTasks
  • getTask
  • addTaskMessage
In Copilot Studio, open the TextMine tool settings. If Allow all is on, Copilot Studio can use all tools exposed by the MCP server. To restrict the agent, turn Allow all off and enable only the individual tools you want the agent to use. For tools that create tasks, approve work, send messages, upload files, import provider files, or change TextMine data, add clear agent instructions requiring confirmation before the agent acts.

​
Test the connection

In the Copilot Studio test pane, start with low-risk prompts: 
List the TextMine Vaults I can access.

Search TextMine for supplier agreements mentioning renewal.

Ask the Commercial Contracts Vault what the termination notice period is in the latest Acme agreement. Include source documents.

Create a TextMine task to review the latest ServiceNow contract intake documents and summarize the missing fields.
The results should only include Vaults, documents, records, and tasks that the connected TextMine API key can access.

​
Custom connector fallback

If the MCP onboarding wizard is not available, create a Power Platform custom connector that wraps the TextMine MCP endpoint. Microsoft’s custom connector import flow expects an OpenAPI 2.0 file. The wrapper describes the MCP endpoint for Power Platform; it is not the full TextMine Public API specification. Use the TextMine developer hub for the full REST API reference. For UK production, use this shape: 
swagger: "2.0"
info:
  title: TextMine MCP UK
  description: OpenAPI 2.0 custom connector wrapper for the TextMine UK production Streamable MCP endpoint. Configure API key authentication in Power Platform with header name X-TextMine-Api-Key, then create connections with the value tm_<key>.
  version: 1.0.0
host: public-api.textmine.com
basePath: /
schemes:
  - https
securityDefinitions:
  api_key:
    type: apiKey
    name: X-TextMine-Api-Key
    in: header
    description: TextMine API key value: tm_<key>. The MCP server normalizes this to Authorization: Bearer tm_<key> for Public API.
security:
  - api_key: []
paths:
  /mcp:
    post:
      summary: Invoke TextMine MCP
      description: Streamable MCP entrypoint for TextMine. Copilot Studio discovers TextMine vault, integration, business record, and task-agent tools from this endpoint.
      x-ms-agentic-protocol: mcp-streamable-1.0
      operationId: InvokeTextMineMcp
      consumes:
        - application/json
      produces:
        - application/json
        - text/event-stream
      parameters:
        - name: Accept
          in: header
          description: Required by Streamable MCP so the transport can return JSON or server-sent event messages.
          required: true
          type: string
          default: application/json,text/event-stream
          x-ms-visibility: internal
      responses:
        "200":
          description: Success

​
Import the wrapper in Power Apps

  1. Copy the YAML above into a file named textmine-mcp-uk.openapi.yaml.
  2. Go to Power Apps.
  3. Select the same Power Platform environment as the Copilot Studio agent.
  4. In the left navigation, select More if needed, then select Discover all.
  5. Under Data, select Custom connectors.
  6. Select New custom connector.
  7. Select Import an OpenAPI file.
  8. Enter a connector name such as TextMine MCP UK.
  9. Upload textmine-mcp-uk.openapi.yaml.
  10. Select Continue.

​
Review the connector settings

In the custom connector wizard:
  1. On General, confirm:
    • Host: public-api.textmine.com
    • Base URL: /
    • Scheme: HTTPS
  2. On Security, confirm:
    • Authentication type: API Key
    • Parameter label: api_key or TextMine API key
    • Parameter name: X-TextMine-Api-Key
    • Parameter location: Header
  3. On Definition, confirm the action is InvokeTextMineMcp and that the /mcp POST operation includes x-ms-agentic-protocol: mcp-streamable-1.0.
  4. Confirm the Accept header parameter is internal and defaults to application/json,text/event-stream.
  5. Select Create connector or Update connector.
Do not add an Authorization header parameter to the Power Platform connector. Power Platform owns authorization handling for connector calls. TextMine expects the connector connection to send the TextMine key through X-TextMine-Api-Key.

​
Create the connection

  1. In the connector, open Test.
  2. Select New connection.
  3. Paste the TextMine API key value, for example tm_....
  4. Create the connection.
  5. If the connection does not appear immediately on the Test tab, wait a few minutes and refresh the connection list.
The API key must come from the same TextMine environment as the connector host. A UK production key should be used with public-api.textmine.com, not a staging, US, BDO, or dedicated host.

​
Add the custom connector to Copilot Studio

After the connector exists in Power Apps:
  1. Return to Copilot Studio.
  2. Open the agent.
  3. Go to Tools.
  4. Select Add a tool.
  5. Select Model Context Protocol.
  6. Select the TextMine custom connector.
  7. Authorize the connection if prompted.
  8. Select Add and configure.
  9. Open the tool settings and review the discovered TextMine MCP tools.
If the connector does not appear, confirm that the connector and agent are in the same Power Platform environment and that the OpenAPI operation includes x-ms-agentic-protocol: mcp-streamable-1.0.

​
Environment hosts

Use the host that matches the TextMine API key and deployment:
EnvironmentConnector hostMCP path
UK productionpublic-api.textmine.com/mcp
Stagingpublic-staging.textmine.com/mcp
US productionpublic-mufg.api.textmine.com/mcp
BDO productionpublic-bdo.api.textmine.com/mcp
Dedicated deploymentProvided by TextMine/mcp
For a non-UK environment, keep the same OpenAPI wrapper shape and replace the info.title, info.description, and host values with the target environment details.

​
Agent instructions

Add instructions that keep the Copilot Studio agent predictable: 
Use TextMine when the user asks about TextMine Vault documents, contract data, business records, or TextMine task-agent work.

Before creating tasks, approving work, sending emails, uploading files, importing provider files, changing records, or triggering workflows, explain the planned action and ask for confirmation.

When answering from TextMine documents, include the document names and source references returned by TextMine.

If TextMine says a Vault, integration, or task-agent email route is not available, tell the user it needs to be activated by their TextMine administrator.

​
Troubleshooting

SymptomCheck
Model Context Protocol is not available under New toolThe MCP onboarding wizard may not be enabled for the tenant or environment. Use the custom connector fallback.
The TextMine connector does not appear in Copilot StudioConfirm the connector and agent are in the same Power Platform environment and the OpenAPI operation includes x-ms-agentic-protocol: mcp-streamable-1.0.
The agent cannot connect to TextMineConfirm the MCP endpoint host matches the TextMine environment for the API key.
Authentication failsConfirm the connection sends X-TextMine-Api-Key with the raw tm_... key value.
No tools appearConfirm the tenant allows MCP/custom connector tools and that the connector was added as a Model Context Protocol tool.
Streamable MCP errors mention AcceptConfirm the custom connector includes the internal Accept header with application/json,text/event-stream.
A Vault or document is missingConfirm the connected TextMine API key has access to that Vault or document.
ServiceNow or another provider is unavailableConfirm the integration is activated and connected in TextMine before asking the agent to use it.
Task-agent email does not create workConfirm task-agent email has been activated for the organization.
For exact Public API operations, schemas, and REST setup, use the developer hub. For product capability context, see TextMine MCP server, Integration catalog, and Workflows.