mcpField
G
Gie Storage

Gie Storage

Remote
pipeworx.ioBusiness & Marketing0Updated 3d ago

About Gie Storage

Gie Storage is an MCP server for European gas-storage and LNG-terminal transparency data from Gas Infrastructure Europe. It provides facility directories and outage reports without a key, while live inventory and level queries require a GIE API key.

Key features

  1. 01Query daily gas-storage levels
  2. 02Retrieve LNG inventory and send-out data
  3. 03Browse storage and LNG facility directories
  4. 04View planned and unplanned outages

Use cases

  1. 01Check gas-storage levels by country or facility
  2. 02Review LNG terminal inventories and send-out
  3. 03Find facilities and inspect outage reports

MCP support

Exposes GIE storage, LNG, facility-directory, and outage tools to MCP clients. Level queries require a GIE API key; directory and outage tools are keyless. It can run through Pipeworx or as a local stdio MCP server.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://gateway.pipeworx.io/gie-storage/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

45
ParameterTypeRequiredDescription
qstringNoAlias for question.
askstringNoAlias for question.
textstringNoAlias for question.
inputstringNoAlias for question.
packsarrayNoOPTIONAL. Restrict routing to these pack slugs (e.g. ["sec-form-d","sec-13f"]) — the router then picks only from tools in those packs. Omit for the default full-catalog routing. Slugs come from list_packs / search_packs / https://pipeworx.io/directory; unlisted or unknown slugs are ignored and named in _meta.pack_scope.ignored, and if none of them resolves the question is routed across the whole catalog with _meta.pack_scope.full_catalog:true (never an empty answer).
querystringNoAlias for question.
promptstringNoAlias for question.
messagestringNoAlias for question.
questionstringYesYour question or request in natural language. Accepts query, q, prompt, text, input, ask, message as aliases.

Details

From the project README

@pipeworx/gie-storage

European natural gas storage and LNG terminal data from Gas Infrastructure Europe (GIE): how full EU gas storage is, by country, operator or site; LNG terminal inventory and send-out; the facility directory; and planned and unplanned outage reports.

Part of Pipeworx — an MCP gateway connecting AI agents to 1800+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.

Tools

  • gie_gas_storage(country?, company?, facility?, date?, from?, to?, days?, _apiKey): daily gas storage level for the EU, one country, one operator or one facility. Covers fill % of working gas volume, gas in storage (TWh), injection and withdrawal (GWh/d), trend and the gas day. With no dates you get the latest gas day. Requires a GIE key.
  • gie_lng_terminals(country?, company?, facility?, date?, from?, to?, days?, _apiKey): daily LNG terminal inventory (1000 m³ LNG and GWh), send-out, and declared maximum inventory and send-out. Requires a GIE key.
  • gie_storage_facilities(dataset?, country?, query?, include_closed?): lists every storage system operator (or LNG operator) by country, with each facility's name, type, EIC code and operational dates. Use the EIC codes as company / facility in the other tools. Keyless.
  • gie_storage_outages(dataset?, country?, company?, facility?, type?, from?, to?, limit?, page?): planned and unplanned unavailability reports, newest first. Each report gives the facility, start and end, whether the end is confirmed or estimated, the capacity taken offline and the operator's reason. from/to filter on the publication date. Keyless.

Auth

The two directory and outage tools are keyless. The two level tools are BYO only: GIE refuses storage and LNG level calls without a personal API key. Registration is free at https://agsi.gie.eu/account, and the same key works on both AGSI+ and ALSI+. Pass it as _apiKey. Without a key, the tool refuses with "requires an API key" and points to the keyless tools.

Data sources

  • Gas Infrastructure Europe (GIE), AGSI+ Aggregated Gas Storage Inventory: daily underground gas storage levels and storage unavailability reports.
  • Gas Infrastructure Europe (GIE), ALSI+ Aggregated LNG Storage Inventory: daily LNG terminal levels and terminal unavailability reports.

Reuse terms: GIE publishes this as public transparency-platform data, and the platform states no reuse licence (checked 2026-10-14). This pack fetches it live for each request and stores no copy, so attribute it to GIE AGSI+ / ALSI+. Every call goes live to GIE, and every response carries source, licence and data_as_of. For the level tools, data_as_of is the gas day GIE reports.

Notes for the next person:

  • An outage filter on a facility is silently ignored by GIE unless the country and operator are also sent. gie_storage_outages resolves both from the directory when only facility is given.
  • In the outage feed, total is the row count on the current page. last_page is the real page count.
  • GIE returns an auth error as HTTP 200 with {"error":"access denied","message":"Invalid or missing API key"}. The pack reads the body and raises the error rather than returning an empty list.

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "gie-storage": {
      "url": "https://gateway.pipeworx.io/gie-storage/mcp"
    }
  }
}
What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/gie-storage/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — ask_pipeworx, discover_tools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via ask_pipeworx, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.

Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://gateway.pipeworx.io/mcp"
    }
  }
}

Both URLs reach the same gateway and the same 1800+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.

No MCP client? Call it over HTTP

This pack takes your own API key (_apiKey) — we don't front one for it, so there's no curl here that would run without it. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/gie_gas_storage. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.

Standalone (no gateway account)

This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:

{
  "mcpServers": {
    "gie-storage": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-gie-storage"]
    }
  }
}

Or run it directly to confirm it starts:

npx -y @pipeworx/mcp-gie-storage

It speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call for only this pack's tools — none of the shared meta-tools the gateway connection above adds. Same source, same tools, no ask_pipeworx routing.

Using with ask_pipeworx

Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:

ask_pipeworx({ question: "your question about Gie Storage data" })

The gateway picks the right tool and fills the arguments automatically.

More

License

MIT

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.