How bariskisir/izmirdammcp works
IzmirDamMcp exposes one MCP tool for retrieving Izmir dam status. A client sends a request through the HTTP app, FastMCP dispatches it to the tool, and the tool defaults the date to the current Istanbul date, fetches and caches IZSU data when needed, optionally filters by dam name, and returns the result. The README documents this capability; the graph follows the sampled server and HTTP-app wiring, while deployment details and unsampled behavior are omitted.
Main entry points: server.py Status tool · index.py HTTP app
Components 9
MCP entry
- HTTP app
api/index.py - FastMCP runtime
api/server.py
Status retrieval
- Status tool
api/server.py - Date default
api/server.py - Name filter
api/server.py - Turkish lowercase
api/server.py
Data sources
- Date cache
api/server.py - IZSU API
Other components
- MCP client
Connections 9
- MCP client → HTTP app: sends request
- HTTP app → FastMCP runtime: serves app
- FastMCP runtime → Status tool: dispatches tool
- Status tool → Date default: defaults date
- Status tool → Date cache: reads or writes
- Status tool → IZSU API: fetches data
- Status tool → Name filter: filters results
- Name filter → Turkish lowercase: normalizes names
- Status tool → FastMCP runtime: returns result