Taixin Semiconductor

MCP

Taixin Documentation MCP Server

Connect AI coding tools to search public Taixin product, solution, download, and technical documentation sources. OAuth sign-in is required to protect account access.

Server URL
https://taixin-semi.com/api/mcp
Same-origin compatibility URL
https://taixin-semi.com/api/mcp

Cursor

{
  "mcpServers": {
    "taixin-documentation": {
      "url": "https://taixin-semi.com/api/mcp"
    }
  }
}

VS Code

{
  "servers": {
    "taixin-documentation": {
      "type": "http",
      "url": "https://taixin-semi.com/api/mcp"
    }
  }
}

Claude Code

claude mcp add --transport http --scope user taixin-documentation "https://taixin-semi.com/api/mcp"

ChatGPT (Codex)

codex mcp add taixin-documentation --url "https://taixin-semi.com/api/mcp"
codex mcp login taixin-documentation

VS Code installation status

If MCP: List Servers already contains taixin-documentation but the details page still shows Install, this is a UI state issue in some VS Code versions. Do not keep selecting Install. Confirm that the server starts by viewing its output or opening the tool picker.

Reliable CLI alternative (PowerShell or macOS/Linux shell)
code --add-mcp '{"name":"taixin-documentation","type":"http","url":"https://taixin-semi.com/api/mcp"}'

Available Tools

search_taixin_sources

Search public Taixin sources for a concrete product, document, parameter, support, company, or application question.

query, language

get_taixin_product_specs

Return public product-spec sources for a Taixin model such as TXW8301.

model, language

find_taixin_downloads

Find public datasheets, manuals, SDKs, downloads, and technical documents for a Taixin product or topic.

query, language

compare_taixin_products

Search public product and technical sources for two concrete Taixin models to support comparison.

leftModel, rightModel, language

Verify The Connection

  1. Add the server URL in your MCP client.
  2. Complete authorization with any sign-in method currently available on the authorization page: Website Email, GitHub, or WeChat.
  3. Confirm tools/list returns the four Taixin tools below.
  4. Call get_taixin_product_specs with model TXW8301 and check that the result cites Taixin sources.
  5. Ask a generic unrelated question such as why lifetime is limited; the tool should return out_of_scope with no sources.

Structured Output

  • Each tool returns unresolved so clients can distinguish no-result or boundary cases from successful lookups.
  • primary_source points to the best matched public source, while sources contains normalized source cards for IDE display.
  • Each source includes source_url, source_type, title, content, and score. The legacy results array is kept for compatibility.

Scope And Guardrails

  • The server only searches public Taixin website sources: products, solutions, downloads, technical documents, support, and company information.
  • Generic questions without a Taixin product, document, parameter, download, or application context return out_of_scope instead of unrelated sources.
  • Product specification and comparison tools require concrete Taixin model-like inputs such as TXW8301.
  • The MCP server does not expose admin APIs, unpublished files, secrets, prices, stock, delivery promises, or internal engineering conclusions.

Command-Line Smoke Test

The discovery script verifies OAuth metadata and dynamic client registration. The client smoke script verifies the OAuth challenge. The token smoke script can issue a short-lived test token in the target database, call initialize, tools/list, a TXW8301 tool call, and an out_of_scope generic search, then revoke the token.

$env:MCP_TEST_ENDPOINT="https://taixin-semi.com/api/mcp"
node frontend/scripts/mcp-oauth-discovery.test.mjs
node frontend/scripts/mcp-client-smoke.test.mjs

$env:MCP_TEST_BEARER_TOKEN="<access-token>"
node frontend/scripts/mcp-client-smoke.test.mjs

$env:MCP_TEST_ISSUE_TOKEN="1"
$env:MCP_TEST_DATABASE_URL="<database-url>"
node frontend/scripts/mcp-token-tool-call-smoke.test.mjs