docbot-mcp 1.0.3 → 1.0.4

package/.github/instructions/chat.instructions.md

@@ -1,45 +1,45 @@
----
-name: chat-instructions
-description: Chatbot response rules and guidelines
----
-
-# Chat Instructions
-
-These instructions govern how chatbots respond to user prompts. Chatbots and large-language models must strictly adhere to these rules at all times.
-
-**Rule 1: Always limit responses to a maximum of 30 words**
-
-**Rule 2: Chat in a conversational manner**
-
-A conversational manner means:
-
-- Use natural language that mimics human conversation
-- Write direct and concise statements or questions
-- Exchange back-and-forth dialogue addressing one idea or topic at a time
-- Avoid providing multiple suggestions, explanations, or solutions in a single response
-- When the user writes a declarative prompt:
-  - Do NOT immediately provide answers, suggestions or explanations
-  - Respond with a simple acknowledgement
-  - Ask a question to clarify intent--a declarative prompt may be a prelude to an imperative or interrogative prompt
-
-**Rule 3: Tutoring the User**
-
-When the user asks how to complete a complex procedure such as coding and developing a user-interface, adhere to the following rules:
-
-- **Do not immediately provide a full solution:**\
-Begin by framing the problem to help the user reason about the solution themselves.
-
-- **Surface initial thought starters:**\
-Share guiding principles or foundational concepts relevant to the task (e.g., componentization, data flow, layout hierarchy, state boundaries).
-
-- **Ask probing, clarifying questions:**\
-Use questions to uncover intent, constraints, and assumptions. The goal is to lead the user's thinking, not to guess on their behalf.
-
-- **Facilitate decomposition:**\
-Use chain-of-thought (CoT) reasoning to break down complex procedures into smaller, manageable steps and present each step sequentially. (e.g., pages → sections → components → behaviors).
-
-- **Use conversational scaffolding:**\
-Phrase guidance in a way that nudges the user toward the correct approach without asserting the solution. Avoid prescriptive language unless explicitly prompted.
-
-- **Casually confirm understanding:**\
+---
+name: chat-instructions
+description: Chatbot response rules and guidelines
+---
+
+# Chat Instructions
+
+These instructions govern how chatbots respond to user prompts. Chatbots and large-language models must strictly adhere to these rules at all times.
+
+**Rule 1: Always limit responses to a maximum of 30 words**
+
+**Rule 2: Chat in a conversational manner**
+
+A conversational manner means:
+
+- Use natural language that mimics human conversation
+- Write direct and concise statements or questions
+- Exchange back-and-forth dialogue addressing one idea or topic at a time
+- Avoid providing multiple suggestions, explanations, or solutions in a single response
+- When the user writes a declarative prompt:
+  - Do NOT immediately provide answers, suggestions or explanations
+  - Respond with a simple acknowledgement
+  - Ask a question to clarify intent--a declarative prompt may be a prelude to an imperative or interrogative prompt
+
+**Rule 3: Tutoring the User**
+
+When the user asks how to complete a complex procedure such as coding and developing a user-interface, adhere to the following rules:
+
+- **Do not immediately provide a full solution:**\
+Begin by framing the problem to help the user reason about the solution themselves.
+
+- **Surface initial thought starters:**\
+Share guiding principles or foundational concepts relevant to the task (e.g., componentization, data flow, layout hierarchy, state boundaries).
+
+- **Ask probing, clarifying questions:**\
+Use questions to uncover intent, constraints, and assumptions. The goal is to lead the user's thinking, not to guess on their behalf.
+
+- **Facilitate decomposition:**\
+Use chain-of-thought (CoT) reasoning to break down complex procedures into smaller, manageable steps and present each step sequentially. (e.g., pages → sections → components → behaviors).
+
+- **Use conversational scaffolding:**\
+Phrase guidance in a way that nudges the user toward the correct approach without asserting the solution. Avoid prescriptive language unless explicitly prompted.
+
+- **Casually confirm understanding:**\
 Periodically check the user's comprehension with a short quiz e.g. "Does this distinction make sense?" or "Can you explain why we'd lift this state?".

package/.github/instructions/version-control.instructions.md

@@ -1,97 +1,97 @@
-# Version Control Instructions
-
-Git is the version-control system used for this project.
-
-Follow the rules below when a user prompts you to complete a task related to version control.
-
-## Copilot Capabilities
-
-You are allowed to carry out ONLY the following two actions:
-
-1. Examine the git working directory to determine whether the modified files belong in the same commit.
-2. Write a commit message for staged files adhering to the guidelines in "Writing Commit Messages" below.
-
-### Allowed Commands
-
-Copilot may always run the following commands without asking for permission:
-
-- **git status --short**\
-List files that are in the working directory as well as files that are staged for commit.
-
-- **git diff --name-only**\
-List files in the working diretory that have unstaged changes.
-
-- **git diff --staged --name-only**\
-List files that are staged for commit.
-
-### Prohibited Commands
-
-Copilot is NEVER allowed to modify the index nor run the following commands regardless of user permission:
-
-- **git add [file]**\
-NEVER stage a file for commit.
-
-- **git commit -m "[message]"**\
-NEVER create a commit.
-
-- **git restore [file]**\
-NEVER discard changes in the working directory.
-
-- **git reset [file]**\
-NEVER unstage a file.
-
-- **git push**\
-NEVER push commits to a remote repository.
-
-- **git pull**\
-NEVER pull changes from a remote repository.
-
-
-- Always examine the diffs of staged files to get context for commit messages
-  - List staged files by executing `git diff --cached --name-only`
-  - View file diffs, run `git diff --cached`
-- If there are no staged files:
-  - Do not write a commit message
-  - Inform the user, "There are not staged files"
-
-## Writing Commit Messages
-
-Commit messages must follow the [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) structure including:
-
-1. Use the imperative mood -- the message should complete the sentence: "If applied, this commit will __"
-2. Insert a blank line between the subject and the body
-3. Limit the subject to a maximum of 50 characters
-4. Wrap the body lines at approximately 72 characters
-5. Use Conventional Commit prefixes (e.g., `feat:`, `fix:`, `docs:`, `refactor`, `revert`)
-
-Carry out the following steps when prompted to write a commit message:
-
-1. Check for staged files: run `git diff --staged --name-only`
-2. If there are no staged files:
-   - Do not write a commit message
-   - Inform the user, "There are not staged files"
-
-If there are staged files:
-
-1. Run `git diff --staged` to examine the diffs and get context for commit messages
-2. Based on the file diffs, infer the message's structural elements including:
-   - Prefix
-   - Optional scope
-   - Body
-   - Footer
-3. Output the commit message inside the chat panel for the user to preview prior to commit
-
-### Example Message Structure
-
-```
-feat(auth): add OAuth2 provider for Google logins
-
-Implement the Google-specific strategy within the passport middleware.
-This allows users to authenticate using their corporate accounts.
-
-Fixes: #102
-```
-
-## References
-
-[Git documentation](https://git-scm.com/docs "Official Git docs")
+# Version Control Instructions
+
+Git is the version-control system used for this project.
+
+Follow the rules below when a user prompts you to complete a task related to version control.
+
+## Copilot Capabilities
+
+You are allowed to carry out ONLY the following two actions:
+
+1. Examine the git working directory to determine whether the modified files belong in the same commit.
+2. Write a commit message for staged files adhering to the guidelines in "Writing Commit Messages" below.
+
+### Allowed Commands
+
+Copilot may always run the following commands without asking for permission:
+
+- **git status --short**\
+List files that are in the working directory as well as files that are staged for commit.
+
+- **git diff --name-only**\
+List files in the working diretory that have unstaged changes.
+
+- **git diff --staged --name-only**\
+List files that are staged for commit.
+
+### Prohibited Commands
+
+Copilot is NEVER allowed to modify the index nor run the following commands regardless of user permission:
+
+- **git add [file]**\
+NEVER stage a file for commit.
+
+- **git commit -m "[message]"**\
+NEVER create a commit.
+
+- **git restore [file]**\
+NEVER discard changes in the working directory.
+
+- **git reset [file]**\
+NEVER unstage a file.
+
+- **git push**\
+NEVER push commits to a remote repository.
+
+- **git pull**\
+NEVER pull changes from a remote repository.
+
+
+- Always examine the diffs of staged files to get context for commit messages
+  - List staged files by executing `git diff --cached --name-only`
+  - View file diffs, run `git diff --cached`
+- If there are no staged files:
+  - Do not write a commit message
+  - Inform the user, "There are not staged files"
+
+## Writing Commit Messages
+
+Commit messages must follow the [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) structure including:
+
+1. Use the imperative mood -- the message should complete the sentence: "If applied, this commit will __"
+2. Insert a blank line between the subject and the body
+3. Limit the subject to a maximum of 50 characters
+4. Wrap the body lines at approximately 72 characters
+5. Use Conventional Commit prefixes (e.g., `feat:`, `fix:`, `docs:`, `refactor`, `revert`)
+
+Carry out the following steps when prompted to write a commit message:
+
+1. Check for staged files: run `git diff --staged --name-only`
+2. If there are no staged files:
+   - Do not write a commit message
+   - Inform the user, "There are not staged files"
+
+If there are staged files:
+
+1. Run `git diff --staged` to examine the diffs and get context for commit messages
+2. Based on the file diffs, infer the message's structural elements including:
+   - Prefix
+   - Optional scope
+   - Body
+   - Footer
+3. Output the commit message inside the chat panel for the user to preview prior to commit
+
+### Example Message Structure
+
+```
+feat(auth): add OAuth2 provider for Google logins
+
+Implement the Google-specific strategy within the passport middleware.
+This allows users to authenticate using their corporate accounts.
+
+Fixes: #102
+```
+
+## References
+
+[Git documentation](https://git-scm.com/docs "Official Git docs")

package/CHANGELOG.md

@@ -2,6 +2,14 @@
 
 All notable changes to this project will be documented in this file.
 
+## [1.0.4] - 2026-03-15
+### Changed
+- Move sample data into `data/` subfolder for better organization
+- Remove exposed App Runner URL from server settings
+- Update `.gitignore` with MCP registry ignore rules
+- Add `sample_data.csv` fixture under `data/`
+- Add script to sync version between package files
+
 ## [1.0.3] - 2026-03-14
 ### Changed
 - Update HTTP MCP endpoint from `/mcp` to `/docbot-mcp` for all incoming requests

package/data/sample-data.csv

@@ -0,0 +1,26 @@
+ticker,shares,price,gain-loss,sector,market-cap,volume
+AAPL,219,422.4,+9.93%,Technology,2353B,40302865
+MSFT,409,90.41,+1.82%,Energy,769B,20254714
+GOOGL,72,77.64,-0.99%,Consumer Staples,1991B,36897201
+AMZN,328,167.85,-8.21%,Consumer Staples,1531B,8895044
+TSLA,349,103.06,+1.42%,Financials,2498B,36219457
+BRK-B,160,512.64,-1.85%,Technology,2111B,14232770
+UNH,477,235.41,-8.35%,Technology,352B,12674771
+JNJ,313,284.86,+1.27%,Energy,1405B,17165971
+XOM,482,339.26,+10.15%,Energy,52B,10598777
+JPM,19,568.33,+11.13%,Healthcare,2046B,29312899
+META,100,324.34,+13.14%,Technology,631B,22888266
+V,94,589.52,+8.33%,Consumer Discretionary,1643B,28852195
+PG,268,105.61,+3.67%,Financials,1909B,44038561
+MA,79,182.44,-9.38%,Financials,173B,37474546
+HD,175,71.8,+3.33%,Financials,2863B,7625833
+CVX,32,266.04,-1.28%,Consumer Discretionary,1531B,28573010
+ABBV,417,146.22,-6.24%,Energy,2672B,32220110
+LLY,314,113.88,-10.53%,Financials,2143B,1232034
+PEP,35,137.1,+6.95%,Energy,2720B,30765339
+KO,128,558.33,+12.15%,Consumer Staples,1788B,37818059
+BAC,412,277.88,+1.46%,Financials,2908B,12488920
+PFE,338,508.69,+1.46%,Consumer Staples,554B,44892846
+COST,70,422.18,-5.12%,Energy,779B,4379465
+TMO,74,264.56,-14.95%,Financials,579B,19665238
+AVGO,230,293.56,+6.99%,Financials,1575B,20542990

package/index.js

@@ -13,7 +13,7 @@ app.use(express.json());
 function createServer() {
   const server = new McpServer({
     name: 'docbot-mcp',
-    version: '1.0.2'
+    version: '1.0.4'
   });
 
   server.registerTool(

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "docbot-mcp",
-  "version": "1.0.3",
+  "version": "1.0.4",
   "mcpName": "io.github.rflukerii-dev/docbot-mcp",
   "description": "Bidirectional CSV <> JSON <> Markdown transformer",
   "main": "index.js",
@@ -8,8 +8,9 @@
     "docbot-mcp": "./index.js"
   },
   "scripts": {
+    "start": "node index.js",
     "test": "echo \"Error: no test specified\" && exit 1",
-    "start": "node index.js"
+    "version": "node scripts/sync-version.js"
   },
   "author": "",
   "license": "MIT",

package/scripts/sync-version.js

@@ -0,0 +1,32 @@
+/**
+ * scripts/sync-version.js
+ * 
+ * Called by npm's "version" lifecycle hook.
+ * Reads the bumped version from package.json and patches
+ * server.json and index.js to match, then stages both files.
+ */
+
+import { readFileSync, writeFileSync } from 'fs';
+import { execSync } from 'child_process';
+
+const pkg = JSON.parse(readFileSync('package.json', 'utf8'));
+const version = pkg.version;
+
+// Patch server.json
+const serverJson = JSON.parse(readFileSync('server.json', 'utf8'));
+serverJson.version = version;
+serverJson.packages[0].version = version;
+writeFileSync('server.json', JSON.stringify(serverJson, null, 2) + '\n');
+
+// Patch index.js
+let indexJs = readFileSync('index.js', 'utf8');
+indexJs = indexJs.replace(
+  /version:\s*['"][^'"]+['"]/,
+  `version: '${version}'`
+);
+writeFileSync('index.js', indexJs);
+
+// Stage patched files so they ride the version commit
+execSync('git add server.json index.js');
+
+console.log(`Synced version ${version} to server.json and index.js`);

package/server.json

@@ -6,20 +6,15 @@
     "url": "https://github.com/rflukerii-dev/docbot-mcp",
     "source": "github"
   },
-  "version": "1.0.3",
+  "version": "1.0.4",
   "packages": [
     {
       "registryType": "npm",
       "identifier": "docbot-mcp",
-      "version": "1.0.3",
+      "version": "1.0.4",
       "transport": {
         "type": "streamable-http"
       }
     }
-  ],
-  "remotes": {
-    "streamable-http": {
-      "url": "https://spdeyfjpfv.us-east-1.awsapprunner.com/docbot-mcp"
-    }
-  }
-}
+  ]
+}

package/server.remote.json

@@ -0,0 +1,25 @@
+{
+  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
+  "name": "io.github.rflukerii-dev/docbot-mcp",
+  "description": "Bidirectional CSV <> JSON <> Markdown transformer",
+  "repository": {
+    "url": "https://github.com/rflukerii-dev/docbot-mcp",
+    "source": "github"
+  },
+  "version": "1.0.3",
+  "packages": [
+    {
+      "registryType": "npm",
+      "identifier": "docbot-mcp",
+      "version": "1.0.3",
+      "transport": {
+        "type": "streamable-http"
+      }
+    }
+  ],
+  "remotes": {
+    "streamable-http": {
+      "url": "https://spdeyfjpfv.us-east-1.awsapprunner.com/docbot-mcp"
+    }
+  }
+}

package/sample_data.csv

@@ -1,21 +0,0 @@
-ID,First Name,Last Name,Email,Department,Job Title,Salary,Hire Date,Manager,Status
-1,John,Smith,john.smith@company.com,Engineering,Senior Developer,125000,2019-03-15,Alice Johnson,Active
-2,Sarah,Johnson,sarah.johnson@company.com,Marketing,Marketing Manager,95000,2020-06-20,Bob Wilson,Active
-3,Michael,Davis,michael.davis@company.com,Sales,Sales Executive,105000,2018-11-10,Carol White,Active
-4,Emily,Brown,emily.brown@company.com,HR,HR Specialist,72000,2021-01-25,David Green,Active
-5,David,Wilson,david.wilson@company.com,Engineering,Junior Developer,65000,2022-08-05,Alice Johnson,Active
-6,Jessica,Martinez,jessica.martinez@company.com,Finance,Finance Analyst,78000,2020-02-14,Edward Black,Active
-7,Robert,Anderson,robert.anderson@company.com,Operations,Operations Manager,98000,2019-09-30,Frank Gray,Active
-8,Lisa,Taylor,lisa.taylor@company.com,Marketing,Content Creator,68000,2021-04-12,Bob Wilson,Active
-9,James,Thomas,james.thomas@company.com,Sales,Sales Representative,72000,2021-11-08,Carol White,Active
-10,Patricia,Jackson,patricia.jackson@company.com,Engineering,DevOps Engineer,115000,2020-05-18,Alice Johnson,Active
-11,Christopher,White,christopher.white@company.com,Finance,Senior Accountant,92000,2019-07-22,Edward Black,Active
-12,Nancy,Harris,nancy.harris@company.com,HR,Recruiter,71000,2021-09-15,David Green,Active
-13,Daniel,Martin,daniel.martin@company.com,Operations,Logistics Coordinator,61000,2022-03-28,Frank Gray,Active
-14,Karen,Thompson,karen.thompson@company.com,Marketing,Social Media Manager,65000,2022-01-10,Bob Wilson,Active
-15,Paul,Garcia,paul.garcia@company.com,Sales,Account Executive,88000,2020-10-05,Carol White,Active
-16,Betty,Lee,betty.lee@company.com,Engineering,QA Engineer,82000,2021-06-14,Alice Johnson,Active
-17,Mark,Perez,mark.perez@company.com,Finance,Budget Analyst,75000,2021-12-06,Edward Black,Active
-18,Susan,Edwards,susan.edwards@company.com,HR,Training Manager,84000,2020-08-17,David Green,Active
-19,Donald,Collins,donald.collins@company.com,Operations,Supply Chain Manager,101000,2019-04-09,Frank Gray,Active
-20,Margaret,Stewart,margaret.stewart@company.com,Sales,Regional Manager,110000,2018-02-19,Carol White,Active