DEPRECATED
Legacy registry entry for Tencent Lexiang enterprise knowledge—only relevant if you are migrating off this deprecated remote URL to the current publisher package.
Overview
Lexiang (ajaxhe) MCP is a deprecated MCP server for the Build phase that previously connected agents to Tencent Lexiang enterprise knowledge via streamable-http remotes.
What is this MCP server?
- Registry title explicitly marks DEPRECATED—migrate to io.github.tencent-lexiang/lexiang-mcp-server
- Remote streamable-http template: https://mcp.lexiang-app.com/ajaxhe-deprecated?company_from={company_code}
- Company code obtained from https://lexiangla.com/mcp after enterprise login
- Canonical codebase lives at github.com/tencent-lexiang/lexiang-mcp-server (v1.0.2 metadata)
- Tencent Lexiang product site: https://lexiang.tencent.com
- Registry version metadata: 1.0.2
- Remote type: streamable-http with company_code variable
- Publisher directive: use io.github.tencent-lexiang/lexiang-mcp-server instead
Community signal: 1 GitHub stars.
What problem does it solve?
Old MCP configs still point at a deprecated Lexiang publisher slug, which breaks or confuses agent access to company knowledge bases.
Who is it for?
Teams auditing legacy MCP manifests that reference ajaxhe/lexiang-mcp-server and need the exact replacement mapping.
Skip if: Any new project—install io.github.tencent-lexiang/lexiang-mcp-server instead; also not for builders outside Tencent Lexiang enterprises.
What do I get? / Deliverables
You identify the replacement io.github.tencent-lexiang/lexiang-mcp-server entry and update remotes with a valid company_code from Lexiang’s MCP portal.
- Clear migration path to the supported Lexiang MCP registry package
- Updated remote URL and company_code variables in agent MCP config
- Agent access to enterprise Lexiang spaces when using the replacement server
Recommended MCP Servers
Journey fit
Enterprise wiki and team knowledge integrations sit on Build / integrations when agents read or write org documentation alongside product work. Integrations subphase covers third-party knowledge bases; Lexiang connects agent sessions to company spaces and MCP remotes.
How it compares
Deprecated remote alias for the same Lexiang integration family—use the current Tencent-lexiang registry server, not this slug.
Common Questions / FAQ
Who is this Lexiang MCP entry for?
Admins and builders maintaining older MCP configs that still reference the ajaxhe registry name, not greenfield installs.
When should I use io.github.ajaxhe/lexiang-mcp-server?
You should not use it for new work; switch to io.github.tencent-lexiang/lexiang-mcp-server whenever you add or refresh Lexiang MCP access.
How do I add Lexiang to my agent correctly?
Register the io.github.tencent-lexiang/lexiang-mcp-server MCP server, set streamable-http to Lexiang’s current remote pattern, and pass company_code from https://lexiangla.com/mcp after login.