@transcend-io/mcp-server-discovery

Beta — this package is under active development. APIs may change without notice.

Transcend MCP Server for data discovery. Provides tools for scanning, classifying, and extracting entities from data.

Requires Node.js ≥ 22.12 (see engines in package.json).

For local runs from this repository, copy secret.env.example to secret.env at the repo root (gitignored) and set the OAuth environment variables (see Run from the monorepo).

Install

Install the CLI globally:

npm install -g @transcend-io/mcp-server-discovery

Or run from a checkout of this repository (see Run from the monorepo below).

Usage

# With OAuth env vars in the environment; from the monorepo use secret.env (see Run from the monorepo)
TRANSCEND_OAUTH_CLIENT_ID=your-client-id \
TRANSCEND_OAUTH_CLIENT_SECRET=your-client-secret \
TRANSCEND_OAUTH_REDIRECT_PORT=your-client-redirect-port \
transcend-mcp-discovery

The process speaks MCP over stdio and is meant to be launched by an MCP client (for example Cursor or Claude Desktop), not used as an interactive shell.

OAuth client setup

OAuth stdio is the recommended path for MCP clients (Cursor, Claude Desktop). Requires org admin access to create OAuth clients.

1. Navigate to app.transcend.io/admin/oauth-clients and create an OAuth client.
2. Copy the client ID and client secret.
3. Choose an available localhost port number, then register http://127.0.0.1:{port}/callback on the OAuth client ({port} is the number you chose). Use 127.0.0.1, not localhost, and ensure the path is /callback. Set TRANSCEND_OAUTH_REDIRECT_PORT to the same port number.

At startup the server verifies client ID, secret, and redirect URI. On first tool call it opens a browser for login. Tokens are session-only (in-memory).

OAuth scopes: ViewDataMap, ViewAssignedIntegrations, ViewCodeScanning, ManageCodeScanning, ViewPrompts, ViewPromptRuns, ExecutePrompt. The signed-in user must hold these permissions. See src/scopes.ts.

Full setup, troubleshooting, and multi-server guidance: MCP root README.

API key alternative: set TRANSCEND_API_KEY instead of OAuth vars for stdio (OAuth is disabled when both are set).

MCP client configuration

npx runs the package’s transcend-mcp-discovery binary (see bin in package.json).

{
  "mcpServers": {
    "transcend-discovery": {
      "command": "npx",
      "args": ["-y", "@transcend-io/mcp-server-discovery"],
      "env": {
        "TRANSCEND_OAUTH_CLIENT_ID": "your-client-id",
        "TRANSCEND_OAUTH_CLIENT_SECRET": "your-client-secret",
        "TRANSCEND_OAUTH_REDIRECT_PORT": "your-client-redirect-port"
      }
    }
  }
}

When developing in this repository, reuse the same variable names from root secret.env in the env block, or use your client’s env-file support if it has one.

Run from the monorepo

1. Credentials — From the repository root, copy secret.env.example to secret.env and set TRANSCEND_OAUTH_CLIENT_ID, TRANSCEND_OAUTH_CLIENT_SECRET, and TRANSCEND_OAUTH_REDIRECT_PORT (and optional URL overrides).

2. Build and run — node ./dist/cli.mjs matches the transcend-mcp-discovery bin (use node because pnpm exec transcend-mcp-discovery may not resolve this package’s own binary in a pnpm workspace):

# from the repository root
pnpm exec turbo run build --filter="@transcend-io/mcp-server-discovery..."
set -a && source ./secret.env && set +a
pnpm -F @transcend-io/mcp-server-discovery exec node ./dist/cli.mjs

Alternative: ./scripts/mcp-run.sh ./packages/mcp/mcp-server-discovery/dist/cli.mjs (sources secret.env when present; run after build).

See [CONTRIBUTING.md](../../../CONTRIBUTING.md#mcp-server