Context7
Up-to-date docs for AI agents
作者による説明(英語の原文)
Connect AI assistants to openLCA. 35 tools for database search, model building, and LCIA.
この3つを1つのスコアにまとめることはしません。意見、測定、人気はそれぞれ別のものだからです。
このサーバーのやさしい解説はまだ書いていません。以下はレジストリから読み取った事実です。
使っているAIアプリを選んで、設定をコピーしてください。
必要なもの
どのアプリを使っていますか?
上でアプリを選んでください。選んだアプリを覚えておくので、次からはボタンに「…にインストール」と表示されます。
Claude Desktop → Settings → Developer → Edit Config を開き、claude_desktop_config.json にこれを貼り付けます
{
"mcpServers": {
"b280-olca": {
"command": "uvx",
"args": [
"b280-olca-mcp"
]
}
}
}ターミナルでこれを実行します
claude mcp add b280-olca -- uvx b280-olca-mcpプロジェクトの .cursor/mcp.json、または ~/.cursor/mcp.json に貼り付けます
{
"mcpServers": {
"b280-olca": {
"command": "uvx",
"args": [
"b280-olca-mcp"
]
}
}
}ブラウザがアプリを開いてよいか確認し、そのあとアプリが設定を表示して確認を求めます。キーの値は空欄のままなので、自分で入力してください。
プロジェクトの .vscode/mcp.json に貼り付けます
{
"servers": {
"b280-olca": {
"type": "stdio",
"command": "uvx",
"args": [
"b280-olca-mcp"
]
}
}
}ブラウザがアプリを開いてよいか確認し、そのあとアプリが設定を表示して確認を求めます。キーの値は空欄のままなので、自分で入力してください。
これはパソコンで動くサーバーですが、ChatGPTがつなげるのはインターネット上のサーバーだけです。ほかのアプリを選んでください。
選んだアプリは、この端末のCookieに保存されます。アカウントは不要です。
この設定は、作者のレジストリ登録情報から作成しています。READMEと違う場合は、READMEに従ってください。
パソコンで動くサーバーです。インストールすると、ツール一覧がAIアプリに表示されます。
誰でも見られる情報をチェックしており、コードは読んでいません。当てはまらない項目は数に入れていません。 · 2026年11月7日にチェック
レジストリ名は、リポジトリを所有するGitHubアカウント Below280 で確認済みです
このリポジトリはまだGitHubから読み取っていません
このリポジトリはまだGitHubから読み取っていません
これはパソコンで動くため、インターネット上のエンドポイントはありません
パソコンで動き、代わりにローカルの設定を使います
パソコンで動くサーバーです。ツール一覧を読み取れるのは、インターネット上のエンドポイントがある場合だけです
レジストリでこのカテゴリにある有効なすべてのサーバーと比較しています。スターは、公開者がリポジトリの所有者である場合だけ数えます。
当てはまる基本チェック1項目のうち1項目に合格しました。コードは読んでいません。キーやトークンを追加する前に、サーバーがどんなアクセスを求めているかを確認し、必要な権限だけを持つキーを使ってください。
レジストリには必須のキーは載っていません。ただし、最初に使うときにサインインを求めるサーバーもあります。
あなたのパソコンで動きます。必要なときにAIアプリが起動し、データは作者のサーバーを通りません(サーバー自体がオンラインサービスを呼び出す場合を除きます)。
GitHubリポジトリの最終更新は–、最新バージョン(1.16.0)がレジストリに届いたのは41 日前です。
Claude Desktop、Claude Code、Cursor、VS CodeなどのMCP対応アプリで使えます。パソコンにPython (uv)も必要です。
同じカテゴリには:Context7, Codebase Memory, Exa
同じカテゴリで、ほかの作者が作ったサーバー。スターの多い順。
カードの見方:★ GitHubスターi3つの柱:レビュー · チェック · 利用状況i更新=最新バージョンをレジストリに公開した日i
Up-to-date docs for AI agents
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Connect AI agents to Exa for web search, content fetching, and multi-step research.
作者のリポジトリから書かれたとおりにコピーしたものです。PopNx MCPは内容を確認・推奨していません。HTML、画像、スクリプトは取り除いています。リンクはこのサイトの外へ移動します。
An MCP (Model Context Protocol) server that connects AI assistants to a running openLCA instance. Developed and tested with Claude Desktop; compatible with any MCP client that supports stdio transport. Built by Below280, the UK partner for openLCA.
The server exposes 35 tools covering the full LCA workflow: exploring databases, building and editing models, running calculations (scenarios, sensitivity, Monte Carlo, contribution analysis), auditing and validating models, and extracting data quality assessments. All calculation patterns are tested against production ecoinvent databases.
The server works with both ecoinvent-family databases (ecoinvent, EN15804GD, HiQLCD, BAFU) and FLCAC-family databases (LCA Commons, US LCI, USEEIO). It asks which family you are using, or auto-detects from the flow property names.
Available on PyPI and the MCP Registry.
pip install b280-olca-mcp
This installs the server and its dependencies (mcp, olca-ipc) in one step. The server runs from anywhere with python -m b280_olca_mcp.
Clone the repository for the latest code, the React dashboard, or if you want to modify the server:
git clone https://github.com/Below280/B280-olca-MCP.git
cd B280-olca-MCP pip install -r requirements.txt
The server entry point is b280_olca_mcp/server.py.
Someone using this MCP can say things like:
The AI assistant handles the conversation, builds the tool calls, and presents results visually with charts, tables, and exportable data.
The server uses stdio transport. Any MCP client that can spawn a local Python process will work.
In Claude Desktop, go to Settings > Developer > Edit Config. Add an openLCA entry to the mcpServers section.
If you installed via PyPI:
{
"mcpServers": { "openLCA": { "command": "python", "args": ["-m", "b280_olca_mcp"], "env": { "OLCA_PORT": "8080" } } } }
If you cloned from GitHub:
{
"mcpServers": { "openLCA": { "command": "python", "args": ["C:/path/to/B280-olca-MCP/b280_olca_mcp/server.py"], "env": { "OLCA_PORT": "8080" } } } }
On Windows, if Claude Desktop cannot find Python, use the full path to your Python executable.
Restart Claude Desktop after saving.
Go to Settings > Tools & MCP > Add MCP Server. Choose stdio transport, set the command to python and the argument to -m b280_olca_mcp (PyPI) or the path to b280_olca_mcp/server.py (GitHub clone). Cursor picks up config changes without restarting.
Add the server to .vscode/mcp.json in your workspace or user settings:
{
"servers": { "openLCA": { "type": "stdio", "command": "python", "args": ["-m", "b280_olca_mcp"], "env": { "OLCA_PORT": "8080" } } } }
Note: VS Code uses servers as the root key, not mcpServers. If using GitHub Copilot, switch Copilot Chat to Agent mode.
ChatGPT cannot directly launch a local stdio server. OpenAI provides the Secure MCP Tunnel, which bridges ChatGPT to a local MCP server without exposing anything publicly. The architecture is:
ChatGPT → Secure MCP Tunnel → B280 MCP (stdio) → openLCA IPC localhost:8080
The tunnel launches the B280 server (python -m b280_olca_mcp) on your machine. No changes to the B280 server are needed; it remains stdio throughout. No additional search or fetch tools are required for ChatGPT custom MCP servers.
B280's existing tool annotations (read-only, destructive, idempotent) are used by ChatGPT when deciding whether to auto-approve or prompt for confirmation.
For the full setup guide, including installation, configuration, troubleshooting and security considerations, see [docs/chatgpt.md](docs/chatgpt.md).
ChatGPT support is currently experimental. A remote Streamable HTTP transport option may be added in future for users who prefer not to run the local tunnel.
Any client that spawns a local Python process over stdin/stdout should work. With PyPI: python -m b280_olca_mcp. With GitHub clone: python path/to/b280_olca_mcp/server.py.
Beta software. This server is under active development. Test it on a copy of your database before connecting a production database. Report issues on GitHub or at mcp-feedback@below280.com.
After creating or modifying anything, press the Refresh button in openLCA's toolbar to see changes in the GUI.
The MCP server runs locally and communicates with openLCA on localhost. The AI client (Claude Desktop or equivalent) sends tool results to its provider's servers for processing. This means process names, exchange data, parameter values, and impact results from your database will be in the conversation.
Do not connect a confidential client database through a personal or free-tier AI account. Use a business or enterprise account with appropriate data retention controls, and check your provider's data processing terms before connecting any database containing sensitive information.
| Tool | Purpose |
|---|---|
database_info | Counts of systems, processes, flows, methods, parameters. Auto-detects database family |
set_database_family | Set ecoinvent or FLCAC naming conventions |
list_systems | List/search product systems |
list_methods | List/search impact assessment methods |
search_processes | Find processes by name, location, or category |
search_flows | Find flows by name and/or category folder |
process_details | Full process info: exchanges, parameters, providers |
system_parameters | List parameters for a product system |
global_parameters | Look up database-level parameters |
find_unit | Look up units and their flow properties |
chemical_synonyms | PubChem synonym search to find database matches |
| Tool | Purpose |
|---|---|
create_global_parameter | Create or update a database-level parameter, as a value or a formula |
create_flow | Create product, waste, or elementary flows |
edit_flow | Add or update flow properties, or change the reference property |
create_bridge | Create a bridge flow + process in one call |
create_process | Build a process with exchanges, parameters, and providers |
edit_process | Edit an existing process: add/update/remove exchanges and parameters |
create_system | Create a product system from a process |
delete_entity | Delete a process, flow, or product system (requires user confirmation; refuses to delete a flow that is still in use) |
| Tool | Purpose |
|---|---|
extract_model | Pull everything from a model folder for inspection |
audit_model | Structural checks: missing qrefs, zero amounts, unit mismatches |
validate_system | Mirrors openLCA's Validate button: linking, parameters, test calculation |
get_system_links | Show which providers are linked for each exchange |
data_quality | Extract pedigree matrices and uncertainty from a process |
find_flow_usage | Find the processes and impact categories that use a flow |
| Tool | Purpose |
|---|---|
calculate | Baseline impact assessment |
contribution_analysis | Process-level contribution breakdown per impact category |
upstream_tree | Multi-level contribution tree for one category, with pedigree scores on every branch |
monte_carlo | Uncertainty simulation with statistics |
inventory_flows | Raw elementary flow results (LCI level) |
scenarios | Scenario calculations from conversational parameter values |
scenarios_csv | Scenario calculations from a CSV file |
sensitivity | Parameter sensitivity analysis |
sensitivity_csv | Sensitivity analysis from a CSV file |
| Tool | Purpose |
|---|---|
help | Show capabilities grouped by workflow, with optional topic filter |
Every tool carries MCP tool annotations (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) so clients can decide whether to auto-approve or prompt for confirmation. Explore and Calculate tools are read-only. Build tools signal that they modify the database. delete_entity is marked destructive. CSV tools are marked as writing files to disk. chemical_synonyms is marked as reaching an external service (PubChem).
The server exposes four MCP resources that AI clients can read on demand:
| Resource | URI | Purpose |
|---|---|---|
| Database info | lca://database/info | Live database overview |
| Assistant instructions | lca://knowledge/instructions | Operational rules, workflows, and conventions |
| IPC protocol reference | lca://knowledge/ipc-protocol | Complete JSON-RPC spec for all 60 IPC methods |
| openLCA resources | lca://knowledge/openlca-resources | Links to databases, docs, forums, and training |
The IPC protocol reference enables AI clients to help users connect to openLCA from any programming language by generating client code from the protocol specification.
The server includes a guided workflow for building EN15804 EPD models from LCI data. The AI maps LCI items to lifecycle modules (A1-D), creates the folder structure, bridge processes, module processes, and product systems. Ask 'build an EPD from this LCI' to start.
For repeated analyses, the server recommends standalone Python scripts that run without AI tokens. After a scenario or sensitivity calculation, it offers to generate the CSV file needed to run the equivalent script from the openLCA-IPC-tools-python repository.
| Repository | Description |
|---|---|
| openLCA-IPC-tools-python | Standalone Python scripts for scenarios, sensitivity, parameters, prospective LCA |
| openLCA-IPC-tools-r | R client for openLCA IPC (first R package for openLCA) |
| openLCA-IPC-tools-fortran | Fortran IPC client and batch calculator |
Built by Below280 Limited, a UK LCA, EPD and CBAM consultancy and official UK partner for openLCA. The calculation patterns in this server are derived from production scripts used in EPD and LCA consulting work, tested against ecoinvent 3.10/3.11/3.12, EN15804GD, and US Federal LCA Commons (FLCAC) databases.
For issues: GitHub Issues or mcp-feedback@below280.com
冒頭だけを表示しています。続きはリポジトリで読めます