Tencent Internal Service MCP Setup

Problem to solve

When an agent needs to read iWiki pages, query TAPD requirements, or manage Gongfeng repositories and MRs, it must also handle internal authentication, MCP endpoint discovery, and service boundaries. This guide breaks the setup into concrete steps: obtain a Taihu PAT, then register the services as MCP endpoints.

How the skill works

The workflow centers on Taihu token and MCP configuration:

• Create a personal token at https://tai.it.woa.com/user/pat; the token looks like tai_pat_xxxxx and is shown only once.
• Prefer official remote MCP: add the service URL and Bearer Token to ~/.workbuddy/mcp.json, so agents can call the services without local dependencies.
• If the remote endpoint is unavailable, use local MCP Server as a fallback for debugging or connectivity issues.

The covered services include iWiki for reading, searching, and creating docs; Gongfeng for repository, MR, Issue, and KM search; and TAPD for requirements, tasks, and defects.

Boundaries and caveats

• It assumes the agent already has access to the relevant Tencent internal services; an expired token will produce 401 and must be refreshed.
• The local path depends on internal npm sources and the local runtime; a missing uvx binary requires installing uv, but remote MCP avoids that dependency.
• Keep the PAT out of public repos and logs, and verify the MCP URL and Bearer header before calling tools.