ChatGPT and OpenAI MCP Setup

Use this page when a ChatGPT workspace, OpenAI API agent, or custom connector should discover and use TextMine.

Which endpoint to use

Use the environment-specific TextMine MCP host for dedicated deployments.

ChatGPT connector setup

If your ChatGPT workspace supports custom MCP connectors, configure the relevant remote MCP endpoint:

Server URL: https://developers.textmine.com/mcp
Authorization: Bearer tm_your_api_key

Use https://app.textmine.com/mcp instead when the connector should call hosted TextMine product tools directly. Use a caller-owned TextMine API key for authenticated execution. If the connector UI does not support bearer headers, use the connector for documentation discovery only until a first-party OAuth flow is available, or use a gateway approved by your organisation.

If an autonomous third-party agent does not yet have a key, use Agent self-service signup. Signup is REST-first and returns an encrypted service-account key for the trusted runtime to store.

OpenAI Responses API pattern

For agents built on the OpenAI Responses API, treat TextMine as an external tool source:

1. Store the TextMine API key outside the model context.
2. Configure the selected MCP endpoint in the agent runtime.
3. Start by reading For Agents and the relevant API Reference pages.
4. Call discovery/list operations before write operations.
5. Return TextMine resource IDs in the final answer for auditability.

Example runtime metadata:

mcp:
  textmine_docs:
    server_url: "https://developers.textmine.com/mcp"
    authorization: "Bearer $TEXTMINE_API_KEY"
  textmine:
    server_url: "https://app.textmine.com/mcp"
    authorization: "Bearer $TEXTMINE_API_KEY"

Keep tm_... keys in a secret store. Do not place raw keys in prompts, system messages, task transcripts, screenshots, or shared docs.