mcp-grocy 2.2.0 → 2.6.0

package/CHANGELOG.md

@@ -0,0 +1,45 @@
+# [2.6.0](https://github.com/miguelangel-nubla/mcp-grocy/compare/v2.5.0...v2.6.0) (2026-07-06)
+
+### Bug Fixes
+
+- reap idle streamable HTTP sessions to prevent McpServer leak ([c55b2c4](https://github.com/miguelangel-nubla/mcp-grocy/commit/c55b2c4808dac4ac5f0c55a45936c8f995d5efc3))
+
+### Features
+
+- add shopping_list_update_item tool to allow modifying list items ([dcbc974](https://github.com/miguelangel-nubla/mcp-grocy/commit/dcbc9746630667bbe89330bab7f7e9f84a3f060f))
+- add shopping*lists*\* configurations to example yaml ([204f03d](https://github.com/miguelangel-nubla/mcp-grocy/commit/204f03dca8c9ca17f3cfc476274f0a5b844912c7))
+- configure husky git hooks ([c8ac158](https://github.com/miguelangel-nubla/mcp-grocy/commit/c8ac1582f477c6dc074166b5a9753a06608c8007))
+- enhance shopping list tools with manual item support and enriched metadata resolution ([a1a8ce3](https://github.com/miguelangel-nubla/mcp-grocy/commit/a1a8ce341b61e5b24a366ae74a95a2c92e93e07c))
+- enrich shopping list tool responses with product and quantity unit details ([56bd553](https://github.com/miguelangel-nubla/mcp-grocy/commit/56bd553e17d913db1f2c61fc963a900f6477f45f))
+- expand shopping module with get, update, and filtered list capabilities ([d7e0e5d](https://github.com/miguelangel-nubla/mcp-grocy/commit/d7e0e5d94962c1b4daf0835a91fc275c25188673))
+- make productId optional in shopping list add tool ([a427e18](https://github.com/miguelangel-nubla/mcp-grocy/commit/a427e1832a9b70e579dae062c7665ec472656359))
+
+# [2.5.0](https://github.com/miguelangel-nubla/mcp-grocy/compare/v2.4.4...v2.5.0) (2026-03-30)
+
+### Bug Fixes
+
+- add read permissions for contents in release workflow to support nested publish-docker job ([5a055a6](https://github.com/miguelangel-nubla/mcp-grocy/commit/5a055a62cf07fa3f0f03d4319e485350c111804a))
+- improve test build isolation and commit-specific tagging ([b1875cc](https://github.com/miguelangel-nubla/mcp-grocy/commit/b1875ccc080111c6d56700aab9c493e418d155be))
+
+### Features
+
+- improve tool call error handling, and implement multi-server shutdown management ([4d19cfb](https://github.com/miguelangel-nubla/mcp-grocy/commit/4d19cfb35dc238a41a92d2fba505998b6a59e1ae))
+
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+Release notes are appended automatically by [semantic-release](https://semantic-release.gitbook.io/) using `@semantic-release/changelog`.
+
+## [Unreleased]
+
+### ⚠️ Breaking Changes
+
+- **MCP resource URIs** use the **`mcp-grocy://`** scheme (from `package.json` `name`, generated into `SERVER_NAME` at build time). Bundled docs: `mcp-grocy://examples`, `mcp-grocy://response-format`, `mcp-grocy://config`. Clients, prompts, or bookmarks that used **`grocy-api://…`** must be updated.
+
+### Added
+
+- **MCP tool `annotations.readOnlyHint: true`** on read-only tools (inventory/recipes/shopping/household/system getters and lookups only—no `*_print_*`, dev tools, or mutating calls). Optional hint for clients; not a security boundary.

package/README.md

@@ -8,20 +8,22 @@
 [![MCP Compatible](https://img.shields.io/badge/MCP-Compatible-blue)](https://modelcontextprotocol.io)
 
 > **🍴 Opinionated Fork Notice**
-> 
+>
 > This is a heavily opinionated fork of [saya6k/mcp-grocy-api](https://github.com/saya6k/mcp-grocy-api) that has diverged significantly to warrant a separate identity. This MCP prioritizes **usability over features**.
 >
 > **Why This Fork Exists:**
+>
 > - The original wrapper exposes the entire Grocy API unprocessed, leading to context overload and LLM confusion
 > - Grocy's API design choices and limitations cause error-prone interactions
 > - Generic API exposure increases hallucination and near-miss results
-> 
+>
 > **This Fork's Philosophy:**
+>
 > - **Filters and augments data** with relevant context for better LLM comprehension
 > - **Reduces API calls** by combining common operations to minimize error chains
 > - **Optimizes for reliability and repeatability** over feature completeness
 > - **Opinionated workflows** that may not match everyone's preferences
-> 
+>
 > If you need complete API access, use the [original fork](https://github.com/saya6k/mcp-grocy-api). This version trades flexibility for focused, dependable grocery management workflows.
 
 ## 🎯 What This MCP Does
@@ -29,24 +31,28 @@
 Transform your LLM into an intelligent household management assistant with focused tools for:
 
 ### 📦 **Stock Management**
+
 - Track inventory across multiple locations with precision
 - Record purchases and consumption with automatic stock updates
 - Monitor expiry dates and get volatile stock alerts
 - Transfer products between storage locations
 
 ### 🛒 **Smart Shopping & Planning**
+
 - Maintain shopping lists with intelligent quantity management
 - Plan meals with recipe scheduling and fulfillment checking
 - Automatically add missing ingredients to shopping lists
 - Track shopping locations and optimize store visits
 
-### 🍽️ **Recipe & Meal Workflows** 
+### 🍽️ **Recipe & Meal Workflows**
+
 - Find recipes with fuzzy search capabilities
 - Check if recipes can be made with current stock
 - Complete cooking workflows with portion control
 - Integrate meal planning with inventory consumption
 
 ### 🏠 **Household Management**
+
 - Manage chores, tasks, and battery tracking
 - Get product price history for budgeting
 - Organize products by groups and categories
@@ -56,21 +62,24 @@ Transform your LLM into an intelligent household management assistant with focus
 
 1. **Get your Grocy API key** from your Grocy instance (User Settings → API Keys)
 2. **Set up with Docker Compose:**
+
    ```bash
    # Get the project
    git clone https://github.com/miguelangel-nubla/mcp-grocy.git
    cd mcp-grocy
-   
+
    # Configure
    cp .env.example .env
    # Edit .env with your GROCY_BASE_URL and GROCY_API_KEY
-   
+
    # Run
    docker compose up -d
    ```
 
 ### Try Without Grocy
+
 Test with mock data (no real Grocy instance needed):
+
 ```bash
 # In .env file, any values work for mock mode
 GROCY_BASE_URL=http://mock
@@ -79,6 +88,14 @@ GROCY_API_KEY=mock
 npm install && npm run dev
 ```
 
+## Requirements (Node.js & tooling)
+
+- **Node.js:** **22 or newer** as declared in `package.json` `engines`. **GitHub Actions** and **`.nvmrc`** use **Node 22** for CI and local alignment.
+- **Docker:** the default image is **`node:22-alpine`** so the container matches that major version (Home Assistant addon builds still override the base image).
+- **TypeScript:** **5.9** in this repo; **TypeScript 6** is waiting on **`typescript-eslint`** to declare compatible peer support.
+- **`npm audit`:** any remaining findings are often inside **nested tooling** (e.g. bundled `npm`), not application dependencies. Use `npm audit` / `npm audit fix` on a branch when refreshing the lockfile.
+- **Quality checks:** `npm run lint` (ESLint), `npm run format:check` (Prettier), `npm test` (Vitest).
+
 ## Installation
 
 ### NPM
@@ -99,6 +116,7 @@ docker run -e GROCY_API_KEY=your_api_key -e GROCY_BASE_URL=http://your-grocy-ins
 ### Docker Compose (Recommended)
 
 Create a `docker-compose.yml`:
+
 ```yaml
 services:
   mcp-grocy:
@@ -109,6 +127,7 @@ services:
 ```
 
 Then:
+
 ```bash
 cp .env.example .env
 # Edit .env with your configuration
@@ -124,6 +143,7 @@ docker compose up -d
    - Create a new API key and copy it
 
 2. **Configure the server:**
+
    ```bash
    cp .env.example .env
    # Edit .env with your GROCY_BASE_URL and GROCY_API_KEY
@@ -135,71 +155,96 @@ docker compose up -d
 
 ### Configuration Options
 
-| Method | Use Case | Command |
-|--------|----------|---------|
-| **`.env` file** | Recommended for most users | `cp .env.example .env` |
-| **Environment variables** | CI/CD, containers | `GROCY_BASE_URL=... GROCY_API_KEY=... mcp-grocy` |
-| **Tool configuration** | Customize functionality | Edit `tools` section in `mcp-grocy.yaml` |
+| Method                    | Use Case                   | Command                                          |
+| ------------------------- | -------------------------- | ------------------------------------------------ |
+| **`.env` file**           | Recommended for most users | `cp .env.example .env`                           |
+| **Environment variables** | CI/CD, containers          | `GROCY_BASE_URL=... GROCY_API_KEY=... mcp-grocy` |
+| **Tool configuration**    | Customize functionality    | Edit `tools` section in `mcp-grocy.yaml`         |
 
 📖 **For complete configuration reference:** See [Configuration Guide](src/resources/config.md)
 
 ## 🚀 Usage Modes
 
 ### Production Mode
+
 Start with your real Grocy instance:
+
 ```bash
 npm start
 ```
 
 ### Development/Testing Mode
+
 Use mock data (no Grocy instance required):
+
 ```bash
 npm run dev
 ```
 
-### HTTP Server Mode  
+### HTTP Server Mode
+
 Enable web-based access via HTTP/SSE:
+
 ```bash
 # In .env: ENABLE_HTTP_SERVER=true
 npm start
 # Access via http://localhost:8080/mcp
 ```
 
-
 ## 📚 Documentation & Resources
 
-| Resource | Purpose | When to Use |
-|----------|---------|-------------|
-| [📖 API Reference](src/resources/api-reference.md) | Complete tool documentation | Tool usage and examples |
-| [⚙️ Configuration Guide](src/resources/config.md) | Advanced configuration reference | Detailed setup, presets, troubleshooting |
-| [📋 .env.example](.env.example) | Environment configuration template | Copy and customize for your setup |
-| [🧪 MCP Inspector](https://github.com/modelcontextprotocol/inspector) | Protocol debugging | Debug MCP interactions |
+| Resource                                                              | Purpose                            | When to Use                              |
+| --------------------------------------------------------------------- | ---------------------------------- | ---------------------------------------- |
+| [📖 API Reference](src/resources/api-reference.md)                    | Complete tool documentation        | Tool usage and examples                  |
+| [⚙️ Configuration Guide](src/resources/config.md)                     | Advanced configuration reference   | Detailed setup, presets, troubleshooting |
+| [📋 .env.example](.env.example)                                       | Environment configuration template | Copy and customize for your setup        |
+| [🧪 MCP Inspector](https://github.com/modelcontextprotocol/inspector) | Protocol debugging                 | Debug MCP interactions                   |
+
+**Bundled MCP resources** (from `resources/list`): `mcp-grocy://examples`, `mcp-grocy://response-format`, `mcp-grocy://config` — markdown docs shipped with the server. The URI scheme matches **`package.json` `name`** (previously some builds used `grocy-api://…`; update pinned URIs in clients or prompts if you relied on that).
 
 ### 🆘 Troubleshooting
 
 #### Common Issues
 
 **"Connection refused" or "Cannot connect to Grocy"**
+
 - Verify `GROCY_BASE_URL` is correct and accessible
 - Check that your Grocy instance is running
 - For HTTPS URLs, ensure SSL certificate is valid or disable verification with `GROCY_ENABLE_SSL_VERIFY=false`
 
 **"Invalid API key" or "Authentication failed"**
+
 - Verify your `GROCY_API_KEY` is correct
 - Check that the API key exists in your Grocy instance (User Settings → API Keys)
 - Ensure the API key has proper permissions
 
 **"Tool not found" errors**
+
 - Check if the tool is enabled in your `mcp-grocy.yaml` file
 - Verify you're using the correct tool names from the API reference
 
 **Large response errors**
+
 - Increase `REST_RESPONSE_SIZE_LIMIT` if you have many products/stock entries
 - Consider disabling unused tools in `mcp-grocy.yaml`
 
+**High memory usage / RAM grows over time (HTTP mode)**
+
+- In HTTP mode the server automatically reaps idle MCP sessions (by default, after
+  5 minutes with no requests), so clients that disconnect without `DELETE /mcp` —
+  or that repeatedly reconnect with a new session — no longer leak per-session
+  server instances. No action is required.
+- Tune via `MCP_SESSION_IDLE_TIMEOUT_MS` / `MCP_SESSION_SWEEP_INTERVAL_MS` (or the
+  `server.session_idle_timeout_ms` / `server.session_sweep_interval_ms` YAML keys):
+  lower the timeout on memory-constrained hosts, raise it if a client legitimately
+  idles for long periods between calls.
+- For the lowest overhead, prefer an MCP client that reuses its `Mcp-Session-Id`
+  across requests and sends `DELETE /mcp` when it disconnects.
+
 #### Debug Mode
 
 Enable detailed logging and use the MCP inspector:
+
 ```bash
 # Launch MCP inspector for protocol debugging
 npm run inspector
@@ -212,8 +257,8 @@ npm run dev
 
 ### Prerequisites
 
-- Node.js 18 or higher
-- Grocy instance (optional with mock mode)
+- Node.js 22 or newer (see **Requirements** above)
+- Grocy instance (optional: use placeholder URLs/keys in `.env` for local runs)
 
 ### Development Setup
 
@@ -234,18 +279,63 @@ npm start
 
 ### Development Commands
 
-| Command | Description |
-|---------|-------------|
-| `npm run build` | Build TypeScript to JavaScript |
-| `npm run watch` | Watch mode for development |
-| `npm run dev` | Start with mock data (no Grocy needed) |
-| `npm test` | Run test suite |
-| `npm run test:watch` | Run tests in watch mode |
-| `npm run inspector` | Launch MCP protocol inspector |
+| Command                  | Description                                                                                                                         |
+| ------------------------ | ----------------------------------------------------------------------------------------------------------------------------------- |
+| `npm run build`          | Build TypeScript to JavaScript                                                                                                      |
+| `npm start`              | Run the built server (`build/main.js`)                                                                                              |
+| `npm run dev`            | Build, then run (use mock `.env` for local testing)                                                                                 |
+| `npm run watch`          | Watch mode for development                                                                                                          |
+| `npm test`               | Run test suite                                                                                                                      |
+| `npm run test:watch`     | Run tests in watch mode                                                                                                             |
+| `npm run inspector`      | Launch MCP protocol inspector                                                                                                       |
+| `npm run dev:mcp-tef`    | Run [mcp-tef](https://github.com/StacklokLabs/mcp-tef) locally (needs **uv** + **Ollama**) for tool-description / similarity checks |
+| `npm run report:mcp-tef` | One command: build, temporary mcp-grocy HTTP + mcp-tef, write `reports/mcp-tef/<timestamp>/` (similarity JSON + `SUMMARY.md`)       |
+
+### Optional: mcp-tef (local tool evaluation)
+
+When you change tool descriptions or add tools, you can run [StacklokLabs/mcp-tef](https://github.com/StacklokLabs/mcp-tef) against **Ollama** (no cloud API key required):
+
+1. Install [uv](https://docs.astral.sh/uv/) and start Ollama; pull a small model, e.g. `ollama pull llama3.2:3b`.
+2. Build and start **mcp-grocy over HTTP** in another terminal (SSE endpoint for mcp-tef):
+
+   ```bash
+   npm run build
+   MCP_HTTP_TRANSPORT_ONLY=true ENABLE_HTTP_SERVER=true HTTP_SERVER_PORT=8790 npm start
+   ```
+
+3. Start mcp-tef:
+
+   ```bash
+   npm run dev:mcp-tef
+   ```
+
+4. Open `http://127.0.0.1:8000/docs` and point workflows at **`http://127.0.0.1:8790/mcp/sse`** (or your port).
+
+The first run clones mcp-tef into `.cache/mcp-tef` (ignored by git). Override the Ollama model with `MCP_TEF_OLLAMA_MODEL`, the listen port with `MCP_TEF_PORT`, or the clone ref with `MCP_TEF_REF`.
+
+**One-shot report (no manual API calls):**
+
+```bash
+npm run report:mcp-tef
+```
+
+Writes under `reports/mcp-tef/<timestamp>/`:
+
+- **`REPORT.md`** — human-readable: tools by domain, flagged pairs as a **markdown table** (short tool names, similarity %).
+- **`REPORT.html`** — same pairs in a simple table; open in a browser if you prefer.
+- **`SUMMARY.md`** — one-screen pointer + counts.
+- **`similarity.json`** — full API response (matrix, composite ids).
+
+Uses ephemeral ports **8792** (mcp-grocy) and **8020** (mcp-tef) by default (`MCP_GROCY_HTTP_PORT`, `MCP_TEF_REPORT_PORT` to override). If you do not set `MCP_GROCY_YAML`, the script drops a temporary `mcp-grocy.yaml` next to the report by copying `mcp-grocy.yaml.example` with every `enabled: false` flipped to `true`, so `tools/list` is complete for analysis.
+
+Add `--with-recommendations` for LLM suggestions on flagged pairs, or `--quality` for per-tool quality scoring (slow; both need Ollama). The report calls mcp-tef’s similarity API with **`transport: sse`** against `/mcp/sse` (current [mcp-tef](https://github.com/StacklokLabs/mcp-tef) request shape). Default similarity threshold is **0.9** (set `SIMILARITY_THRESHOLD=0.85` for the previous, noisier report).
+
+Optional per-tool **`title`** and **`meta`** (→ MCP `_meta`) can be set in definitions when they add real signal; otherwise clients use **`name`** only.
 
 ### Debugging
 
 Use the MCP inspector to debug protocol interactions:
+
 ```bash
 npm run inspector
 ```
@@ -257,22 +347,25 @@ This launches a web interface for testing MCP tools and viewing protocol message
 This is an **opinionated fork** focused on LLM usability and workflow reliability. Contributions are welcome but must align with the core philosophy:
 
 ### ✅ Welcome Contributions
+
 - Bug fixes and reliability improvements
-- Better error handling and validation  
+- Better error handling and validation
 - Documentation improvements
 - Test coverage enhancements
 - Performance optimizations
 
 ### ❌ Contributions Requiring Discussion
+
 - New tool additions (must demonstrate clear LLM workflow benefits)
 - API design changes that increase complexity
 - Features that expose raw Grocy API behavior
 
 ### Development Workflow
+
 1. Fork the repository
 2. Create a feature branch
 3. Make your changes with tests
-4. Run `npm test` and ensure all tests pass  
+4. Run `npm test` and ensure all tests pass
 5. Submit a pull request with clear description
 
 ## 📄 License
@@ -282,4 +375,4 @@ This project is licensed under the [MIT License](LICENSE).
 ---
 
 **🏠 Made for reliable household management with LLMs**  
-*Prioritizing workflow efficiency over feature completeness*
+_Prioritizing workflow efficiency over feature completeness_

package/build/resources/CHANGELOG.md

@@ -0,0 +1,47 @@
+# [2.6.0](https://github.com/miguelangel-nubla/mcp-grocy/compare/v2.5.0...v2.6.0) (2026-07-06)
+
+
+### Bug Fixes
+
+* reap idle streamable HTTP sessions to prevent McpServer leak ([c55b2c4](https://github.com/miguelangel-nubla/mcp-grocy/commit/c55b2c4808dac4ac5f0c55a45936c8f995d5efc3))
+
+
+### Features
+
+* add shopping_list_update_item tool to allow modifying list items ([dcbc974](https://github.com/miguelangel-nubla/mcp-grocy/commit/dcbc9746630667bbe89330bab7f7e9f84a3f060f))
+* add shopping_lists_* configurations to example yaml ([204f03d](https://github.com/miguelangel-nubla/mcp-grocy/commit/204f03dca8c9ca17f3cfc476274f0a5b844912c7))
+* configure husky git hooks ([c8ac158](https://github.com/miguelangel-nubla/mcp-grocy/commit/c8ac1582f477c6dc074166b5a9753a06608c8007))
+* enhance shopping list tools with manual item support and enriched metadata resolution ([a1a8ce3](https://github.com/miguelangel-nubla/mcp-grocy/commit/a1a8ce341b61e5b24a366ae74a95a2c92e93e07c))
+* enrich shopping list tool responses with product and quantity unit details ([56bd553](https://github.com/miguelangel-nubla/mcp-grocy/commit/56bd553e17d913db1f2c61fc963a900f6477f45f))
+* expand shopping module with get, update, and filtered list capabilities ([d7e0e5d](https://github.com/miguelangel-nubla/mcp-grocy/commit/d7e0e5d94962c1b4daf0835a91fc275c25188673))
+* make productId optional in shopping list add tool ([a427e18](https://github.com/miguelangel-nubla/mcp-grocy/commit/a427e1832a9b70e579dae062c7665ec472656359))
+
+# [2.5.0](https://github.com/miguelangel-nubla/mcp-grocy/compare/v2.4.4...v2.5.0) (2026-03-30)
+
+### Bug Fixes
+
+- add read permissions for contents in release workflow to support nested publish-docker job ([5a055a6](https://github.com/miguelangel-nubla/mcp-grocy/commit/5a055a62cf07fa3f0f03d4319e485350c111804a))
+- improve test build isolation and commit-specific tagging ([b1875cc](https://github.com/miguelangel-nubla/mcp-grocy/commit/b1875ccc080111c6d56700aab9c493e418d155be))
+
+### Features
+
+- improve tool call error handling, and implement multi-server shutdown management ([4d19cfb](https://github.com/miguelangel-nubla/mcp-grocy/commit/4d19cfb35dc238a41a92d2fba505998b6a59e1ae))
+
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+Release notes are appended automatically by [semantic-release](https://semantic-release.gitbook.io/) using `@semantic-release/changelog`.
+
+## [Unreleased]
+
+### ⚠️ Breaking Changes
+
+- **MCP resource URIs** use the **`mcp-grocy://`** scheme (from `package.json` `name`, generated into `SERVER_NAME` at build time). Bundled docs: `mcp-grocy://examples`, `mcp-grocy://response-format`, `mcp-grocy://config`. Clients, prompts, or bookmarks that used **`grocy-api://…`** must be updated.
+
+### Added
+
+- **MCP tool `annotations.readOnlyHint: true`** on read-only tools (inventory/recipes/shopping/household/system getters and lookups only—no `*_print_*`, dev tools, or mutating calls). Optional hint for clients; not a security boundary.

package/build/resources/DOCS.md

@@ -4,12 +4,11 @@ This addon allows you to run MCP server that communicates with Grocy API in your
 
 ## Installation
 
-1. Add this repository to your Home Assistant addon store: 
+1. Add this repository to your Home Assistant addon store:
    [![Open your Home Assistant instance and show the add add-on repository dialog with a specific repository URL pre-filled.](https://my.home-assistant.io/badges/supervisor_add_addon_repository.svg)](https://my.home-assistant.io/redirect/supervisor_add_addon_repository/?repository_url=https://github.com/miguelangel-nubla/hassio-addons)
 
 2. Find the "MCP Grocy API" addon and click Install.
 
-
 ## How-to-use
 
 You cannot use this with [Model Context Protocol](https://www.home-assistant.io/integrations/mcp) alone.
@@ -30,26 +29,32 @@ http_server_port: 8080
 ```
 
 ### Option: `grocy_base_url` (required)
+
 - The URL to your Grocy instance.
 - Example: `https://grocy.example.com`
 
 ### Option: `grocy_api_key` (required)
+
 - Your Grocy API key.
 - You can find this in your Grocy settings.
 
 ### Option: `enable_ssl_verify` (optional)
+
 - Set to `false` to disable SSL verification (useful for self-signed certificates).
 - Default: `true`
 
 ### Option: `response_size_limit` (optional)
+
 - Maximum size of API responses.
 - Default: `10000`
 
 ### Option: `enable_http_server` (optional)
+
 - Set to `false` to disable streamable http and sse protocol server.
 - Default: `true`
 
 ### Option: `http_server_port` (optional)
+
 - Set to port you want to use in streamable http and sse protocol server.
 - Default: `8080`
 
@@ -59,4 +64,4 @@ This addon communicates with Home Assistant via standard input/output (stdio) or
 
 ## Support
 
-If you have any issues or questions, please file an issue on the GitHub repository.
+If you have any issues or questions, please file an issue on the GitHub repository.