连接能力
linancn tiangong lca mcp 为 AI Agent 提供什么
来源目录未提供结构化功能列表，请在使用前阅读源仓库文档。
安全
MCP 收录不等于安全审核
MCP 服务器可能获得模型上下文、凭据、本地文件或调用外部系统的权限。连接 Agent 前，请检查代码、环境变量、网络行为、软件包来源与维护状态。
README
仓库文档
| title | TianGong LCA MCP README EN | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| docType | guide | ||||||||||
| scope | repo | ||||||||||
| status | active | ||||||||||
| authoritative | false | ||||||||||
| owner | mcp | ||||||||||
| language | en | ||||||||||
| whenToUse |
|
||||||||||
| whenToUpdate |
|
||||||||||
| checkPaths |
|
||||||||||
| lastReviewedAt | 2026-09-14 | ||||||||||
| lastReviewedCommit | b7a27cda880e0638589e8264c4cef6bbc22d552d | ||||||||||
| lastReviewedNote | Reviewed for MCP #78 / release 0.2.1: exact helper-confirmed version projection advances 0.2.0 to 0.2.1 across package.json, the Dockerfile global pin, both live consumer/toolchain bindings and the four active Docker run examples, which now describe a local build only because no public Docker Hub prebuilt tag is verified. SDK stays exact 0.2.0; lock bytes, dependencies, Node 24.19.0, pnpm 11.24.0, TypeScript 7.0.2, runtime/auth behavior, workflow logic and every historical release fixture remain unchanged. | ||||||||||
| related |
|
TianGong LCA Model Context Protocol (MCP) Server supports STDIO and Streamable Http protocols.
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/v1Remote 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.
The MCP origin exposes no authorization, token, refresh, revoke, callback, registration, demo, or authorization-code display endpoint. Supabase Auth owns those protocol operations and Next owns /oauth/consent.
corepack install --global pnpm@11.24.0
pnpm add --global @tiangong-lca/mcp-server
pnpm dlx dotenv-cli -e .env -- tiangong-lca-mcp-stdio# Build the MCP server image locally using Dockerfile
docker build -t linancn/tiangong-lca-mcp-server:0.2.1 .
# Start MCP server using Docker
docker run -d \
--name tiangong-lca-mcp-server \
--publish 9278:9278 \
--env-file .env \
linancn/tiangong-lca-mcp-server:0.2.1# Launch the STDIO Server using MCP Inspector
pnpm startpnpm start:serverpnpm start:server-localThe HTTP start commands launch MCP Inspector through a cross-platform Node argv wrapper and inject the development-only Inspector environment without POSIX shell syntax.
社区