Codex MCP Setup

Use this setup when Codex should discover TextMine docs and API schemas through ReadMe MCP, or call the hosted TextMine MCP product tools with a TextMine API key.

Which endpoint to use

Use the environment-specific TextMine MCP host for dedicated deployments. The public multitenant host is https://app.textmine.com.

Prerequisites

• A TextMine API key for the user, integration, or third-party agent service account.
• Codex with remote HTTP MCP support.

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 tm_... service-account key for the trusted runtime to store.

Recommended setup

Store the API key in an environment variable:

export TEXTMINE_API_KEY="tm_your_api_key"

Add the ReadMe MCP server for docs and generated API-reference tools:

codex mcp add textmine-docs \
  --url https://developers.textmine.com/mcp \
  --bearer-token-env-var TEXTMINE_API_KEY

Add the hosted TextMine MCP server when Codex should use product tools directly:

codex mcp add textmine \
  --url https://app.textmine.com/mcp \
  --bearer-token-env-var TEXTMINE_API_KEY

Check the servers are configured:

codex mcp list

First prompt to try

Use TextMine docs to read the For Agents page, list the relevant Public API V3 operation IDs, then explain the safe sequence for importing a Google Drive file into Vault.

Operating guidance

Codex should use listVaults and other discovery calls before mutations, and should ask before destructive changes, new workflows, scheduled agents, provider disconnects, or credential creation.

Keep tm_... keys in environment variables or secure credential storage. Do not paste real keys into prompts, repo files, task transcripts, or shared docs.