Cursor and Windsurf MCP Setup

Use this page when an editor agent should maintain code or documentation with live TextMine API context, or operate TextMine through hosted MCP tools.

Which endpoint to use

Use https://mcp.textmine.com/mcp for public TextMine MCP setup. Use environment-specific MCP hosts only for private preview, staging validation, or dedicated deployments when TextMine explicitly issues that host.

Cursor

Add a project or global MCP configuration using the remote server URLs:

{
  "mcpServers": {
    "textmine-docs": {
      "url": "https://developers.textmine.com/mcp"
    },
    "textmine": {
      "url": "https://mcp.textmine.com/mcp",
      "headers": {
        "Authorization": "Bearer $TEXTMINE_API_KEY"
      }
    }
  }
}

Store TEXTMINE_API_KEY in the editor or shell secret mechanism rather than committing it. If your editor cannot set Authorization, set X-TextMine-Api-Key with the same tm_... key instead.

Windsurf

Use Windsurf's MCP server configuration UI or config file with the same selected endpoint and bearer token. If Windsurf stores secrets separately, put only the server URL in JSON and keep the bearer token in the secret field.

{
  "name": "textmine",
  "serverUrl": "https://mcp.textmine.com/mcp",
  "headers": {
    "Authorization": "Bearer $TEXTMINE_API_KEY"
  }
}

For documentation discovery, add a second server named textmine-docs with server URL https://developers.textmine.com/mcp.

API keys

Existing customers can create or request keys through their organization access flow. 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.

First prompt to try

Use TextMine docs to read the For Agents page, then inspect the Public API V3 operations needed to upload a file into Vault and poll processing status. Do not call write operations yet.

Safety notes

• Use discovery calls before mutations.
• Ask before destructive changes, workflow activation, publication, scheduled work, provider disconnects, or API-key creation.
• Keep tm_... keys out of repo files, prompts, screenshots, and shared docs.