– – . . . 标题:TianGong LCA MCP README EN docType: 向导 范围: repo 状态: 活动 权威:虚假 拥有者: mcp 语言: en 使用时 :

• 当您需要英语用户界面的 MCP 软件包设置、 Docker 使用、本地启动或检查员实例时 当更新时 :
• 当英语启动命令、 Docker 使用、 软件包引用或用户化的 MCP 实例发生变化时 检查路径 :
• 读取。
• 读取ME CN.md
• 包裹,杰森
• 多克档案
• Mcp config.json (英语).
• src/index.ts
• src/index server.ts (中文(简体) ).
• src/index server local.ts 互联网档案馆的存檔,存档日期2013-12-02.
• sc/http app.ts
• src/http app local.ts (英语). 上次审查日期:2026-10-25 最后审查的承诺:3ddf1367e7d48fc12cf43e953ef539070c7671fd last Reviewed Note:'MCP #97:已审查过明确的后端卫和下线/STDIO回归,外加被限制的Zod/body-parser/Vite/Undici安全修复. HTTP OAuth, 公共计划, SDK, Express, 源包版本, Docker pin和出版边界被保留." 有关:
• 科学家们,md
• .docpact/ config.yaml (英语).
• DEV EN. md (英语).
• 读取ME CN.md – – . . .

天相乐团

联合国

TianGong LCA模式上下文协议(MCP)服务器支持STIO和可流 Http协议.

□ 环境

复制 '.env. 存档副本.

---

title: TianGong LCA MCP README EN docType: guide scope: repo status: active authoritative: false owner: mcp language: en whenToUse:

• when you need English user-facing MCP package setup, Docker usage, local startup, or inspector examples whenToUpdate:
• when English startup commands, Docker usage, package invocation, or user-facing MCP examples change checkPaths:
• README.md
• README_CN.md
• package.json
• Dockerfile
• mcp_config.json
• src/index.ts
• src/index_server.ts
• src/index_server_local.ts
• src/http_app.ts
• src/http_app_local.ts lastReviewedAt: 2026-11-04 lastReviewedCommit: e141b4108eb864e99e185c81f6fb32b1278ba1c8 lastReviewedNote: ‘MCP #104: reviewed explicit actor-authenticated V2-V5 Study consumer, exact Edge artifacts, bounded downloads, source refusal and sticky same-key mutation recovery. Canonical source/packed/clean gates, independent review and installed runtime qualification are recorded separately; no publication or P5 enablement.’ related:
• AGENTS.md
• .docpact/config.yaml
• DEV_EN.md
• README_CN.md

---

TianGong-LCA-MCP

中文 | English

TianGong LCA Model Context Protocol (MCP) Server supports STDIO and Streamable Http protocols.

Environment

Copy .env.example and populate its Supabase issuer, publishable key, exact admitted public OAuth client IDs, and allowed browser origins. OAuth authentication requires no Redis, confidential client secret, or server-side session encryption key.

GLAD dataset search tools additionally require a GLAD API key:

GLAD_API_KEY=your-glad-api-key
GLAD_API_BASE_URL=https://www.globallcadataaccess.org/api/v1

Remote OAuth

Remote Streamable HTTP is an OAuth 2.1 protected resource. A compatible MCP host discovers /.well-known/oauth-protected-resource/mcp, follows its Supabase Auth authorization server, opens the user’s browser, and completes Authorization Code with S256 PKCE. The user signs in and consents in Next; usernames and passwords are never entered into the AI or MCP host.

Supabase issues the access and rotating refresh tokens directly to the public MCP client. The client stores its refresh token locally and sends the short-lived Supabase ES256 access JWT on every MCP request. The server verifies signature, issuer, audience, expiry, role/session, and exact client_id; Edge/PostgREST then re-verify the same user/client context and enforce RLS capabilities.

Dynamic Client Registration remains disabled. Operators register exact public clients and loopback callbacks in Supabase, then list those UUID client IDs in MCP_OAUTH_ALLOWED_CLIENT_IDS_JSON. Unknown, malformed, expired, Cognito, and password/API-key bearers fail the canonical OAuth challenge without fallback I/O.