了解mcp了解mcp
](https://www.npmjs.com/package/knowing-mcp)

](https://www.npmjs.com/package/knowing-mcp)支持工作空间的MCP(模型上下文协议)服务器 它适用于任何VS Code项目。从工作区的git remote自动检测GitHub存储库,并提供GitHub操作、专家AI协助和架构文档工具。
全局MCP(模型上下文协议)服务器 GitHub运营和人工智能协助。在VS Code中配置一次,在任何存储库的任何工作区中使用。

](https://github.com/Gullers-Grupp/knowing-mcp/actions/workflows/ci.yml)## 🎯 主要特点
工作区感知MCP服务器 适用于任何VS Code项目的GitHub操作和AI协助。自动检测您的存储库,因此您无需再次指定所有者/存储库!- ✅ 工作区感知:从git remote自动检测GitHub仓库
✨ 特性
- ✅ 全球证书:存储GitHub令牌和Azure密钥一次,随处使用
- 🌍 适用于任何VS Code工作区 -配置一次,随处使用
- 🔐 全球证书 -安全存储GitHub令牌和Azure密钥
- ✅ 在任何项目中工作:注册一次,可在所有VS Code工作区中使用
- 🛠️ 11个GitHub工具 -全面的问题和项目管理
- 🤖 2个AI工具 -专家咨询(Azure OpenAI GPT-5)和架构问答 - ✅ 无硬编码:无需为每个操作指定所有者/仓库
- 📚 简单设置 -配置mcp.json并重新加载
- ✅ 全套工具:GitHub问题,项目,问专家,问架构师
🚀 快速开始
1.安装依赖项
🚀 Quick Start
cd ~/Github # or your preferred location
git clone https://github.com/aponomy/knowing-mcp.git
cd knowing-mcp## ✨ Features### 1. Install Dependencies
npm install
2.配置凭据-🎯 自动检测GitHub存储库 从git remote-不再键入owner/repo!\\\`bash
创建 ~/.knowing-mcp.env:- 🌍 适用于任何VS Code工作区 -配置一次,使用everywhere工具/了解mcp
# GitHub Personal Access Token
GH_TOKEN=ghp_your_token_here- 🛠️ **11 GitHub tools** - Full issue and project management```
# Azure OpenAI Configuration (optional)- 🤖 **2 AI tools** - Expert consultation (GPT-5) and architecture Q&A
AZURE_OPENAI_ENDPOINT=https://your-resource.openai.azure.com
AZURE_OPENAI_API_KEY=your_key_here- 📚 **Zero configuration per-project** - Just open and use!### 2. Configure Global Credentials
AZURE_OPENAI_GPT5_DEPLOYMENT=gpt-4o-realtime
获取您的代币:## 🚀 快速开始选项A:VS代码用户设置(推荐)
- GitHub: https://github.com/settings/tokens/new(范围:
repo,project,read:org)
- Azure OpenAI:Azure门户→ 您的OpenAI资源→ 密钥和端点
3.配置VS代码MCP###安装编辑您的VS代码 用户设置 (JSON):
重要:MCP服务器配置在mcp.json,不在settings.json-媒体Cmd+Shift+P→ “首选项:打开用户设置(JSON)”
创建或编辑:\~/库/应用程序支持/代码/用户/mcp.json \\\ bash-添加mcp服务器配置:
{
"servers": {``````json
"knowing-mcp": {
"command": "node",{
"args": ["/Users/YOUR_USERNAME/Github/knowing-mcp/src/server.mjs"],
"env": {### Configure "github.copilot.chat.mcpServers": {
"GH_TOKEN": "${input:gh-token}",
"AZURE_OPENAI_ENDPOINT": "${input:azure-endpoint}", "knowing-mcp": {
"AZURE_OPENAI_API_KEY": "${input:azure-key}",
"AZURE_OPENAI_GPT5_DEPLOYMENT": "${input:azure-deployment}"Add to VS Code **User Settings** (JSON): "command": "node",
}
} "args": ["/Users/YOUR_USERNAME/Github/gullers-platform/tools/knowing-mcp/server.mjs"],
},
"inputs": {```json "env": {
"gh-token": "ghp_your_actual_token",
"azure-endpoint": "https://your-resource.openai.azure.com",{ "WORKSPACE_ROOT": "${workspaceFolder}",
"azure-key": "your_azure_key",
"azure-deployment": "gpt-4o-realtime" "github.copilot.chat.mcpServers": { "GH_TOKEN": "YOUR_GITHUB_TOKEN",
}
} "knowing-mcp": { "AZURE_OPENAI_ENDPOINT": "https://your-resource.openai.azure.com",
"command": "knowing-mcp", "AZURE_OPENAI_API_KEY": "YOUR_AZURE_KEY",替换:
/Users/YOUR_USERNAME/...与您的实际绝对路径server.mjs“env”:{“AZURE_OPENAI_GPT5_DEPLOYMENT”:“gpt-5”
- 所有凭证值与您的实际令牌
"WORKSPACE_ROOT": "${workspaceFolder}", }4.重新加载VS代码
"GH_TOKEN": "ghp_your_github_token" }按 Cmd+Shift+P → “开发人员:重新加载窗口”
} }5.测试它
}}在Copilot聊天中,尝试:
}\\\`
List issues in aponomy/knowing-mcp}
The agent should automatically call the `issue-list` tool with the specified repository.
## 📚 Available Tools
### UseCreate `~/.knowing-mcp.env`:
### GitHub Tools (require owner/repo)
| Tool | Description | Required Parameters |
|------|-------------|---------------------|Open **any** workspace with a GitHub remote, then in Copilot Chat:```bash
| `issue-list` | List issues | `owner`, `repo` |
| `issue-create` | Create an issue | `owner`, `repo`, `title` |# GitHub Personal Access Token
| `issue-get` | Get issue details | `owner`, `repo`, `issue_number` |
| `issue-update` | Update an issue | `owner`, `repo`, `issue_number` |```GH_TOKEN=ghp_your_token_here
| `issue-close` | Close an issue | `owner`, `repo`, `issue_number` |
| `issue-comment` | Comment on issue | `owner`, `repo`, `issue_number`, `body` |List all open issues
### Project ToolsCreate issue titled "Fix header layout"# Azure OpenAI Configuration
| Tool | Description | Required Parameters |Show me issue #42AZURE_OPENAI_ENDPOINT=https://your-resource.openai.azure.com
|------|-------------|---------------------|
| `project-get` | Get project info | `owner`, `number` |```AZURE_OPENAI_API_KEY=your_key_here
| `project-item-add` | Add item to project | `projectId`, `contentId` |
| `project-draft-issue` | Create draft issue | `projectId`, `title` |AZURE_OPENAI_GPT5_DEPLOYMENT=gpt-5
### AI Tools (no repo needed)
| Tool | Description | Required Parameters |
|------|-------------|---------------------|
| `ask-expert` | Ask Azure OpenAI GPT-5 | `question`, `context` |
| `deep-research` | Web research with o3 + Bing | `prompt` |
| `ask-architect` | Query architecture docs | `question` |
### Presentation Tools
| Tool | Description | Required Parameters |
|------|-------------|---------------------|
| `init_presentation` | Create React slide deck workspace | `path` |
| `serve_presentation` | Start dev server for slides | `path` |
| `export_presentation_pdf` | Export slides to PDF | `path` |
See [React Slide Deck documentation](docs/REACT-SLIDE-DECK.md) for details.
## 🎯 Usage Examples
- **[Installation Guide](docs/docs/INSTALL.md)** - Complete installation instructions- **GitHub Token**: https://github.com/settings/tokens/new
### Natural Language Commands
- **[Quick Start](QUICK-START.md)** - Get running in 5 minutes - Scopes needed: `repo`, `project`, `read:org`
The agent intelligently extracts owner/repo from your commands:
- **[VS Code Setup](docs/VSCODE-SETUP.md)** - Detailed configuration- **Azure OpenAI**: From Azure Portal → Your OpenAI resource → Keys and Endpoint
“列出经济学/了解mcp中的问题”- 贡献 -如何做出贡献
“在microsoft/vcode中创建一个名为“Bug修复”的问题”
“在脸书上显示问题#42/反应”###3。更新服务器路径
## 🎯 What Makes It Special?
### Working Across Repositories
In the VS Code User Settings above, replace:
You can work with different repos in the same session:
### Before (traditional MCP):```
“列出aponomy/knowing mcp中的问题”\\/Users/YOUR_USERNAME/Github/gullers platform/tools/knowing mcp/server.mjs
“现在在microsoft/vcode中显示问题”
“在facebook/react中创建一个标题为‘文档更新’的问题”在所有者/仓库中创建标题为“Bug修复”的问题← 每次手动\\\`
使用AI工具
通过实际的绝对路径 server.mjs 在你的机器上。
"Ask expert: Why is my React component re-rendering unnecessarily?"### After (knowing-mcp):
"Ask architect: How should we structure our microservices?"
🔧 Why owner/repo are RequiredCreate issue titled "Bug fix" ← Auto-detects your repo! 🎉```bash
Global MCP servers cannot automatically detect which workspace VS Code is currently using because:```cd tools/knowing-mcp
- ❌ MCP protocol doesn't define "workspace" conceptpwd
- ❌ VS Code doesn't pass workspace context to global servers
- ❌
process.cwd()is the user's home directory, not the workspace### Cross-Workspace:# Copy the output and append "/server.mjs"
- ❌
${workspaceFolder}variables don't work in globalmcp.json
制作 `owner` 和 `repo` **必需的** 确保:
# 工作空间A(Gullers Grupp/平台)
- ✅ 清晰、明确的操作
- ✅ 适用于任何工作区“列出问题”→ 显示来自Gullers Grupp/platform###4的问题。重新加载VS代码
- ✅ 没有无声的失败或令人困惑的错误
- ✅ Agent可以智能地从对话上下文中提取
## 📖 文档#工作区B中(microsoft/vcode)-出版社 `Cmd+Shift+P` (macOS)或 `Ctrl+Shift+P` (Windows/Linux)
- **[部署指南](docs/docs/DEPLOYMENT.md)** -完整的部署说明“列出问题”→ 显示来自microsoft/vcode的问题-运行: **“开发人员:重新加载窗口”**
- **[安装指南](docs/docs/INSTALL.md)** -详细的安装步骤
- **[快速开始](QUICK-START.md)** -5分钟后开始跑步
- **[贡献](CONTRIBUTING.md)** -如何做出贡献
- **[安全](SECURITY.md)** -安全最佳实践相同的命令,不同的仓库。自动! ✨### 5.在任何工作空间进行测试
## 🔧 故障排除\`\`\`
### 服务器未启动打开 **任何** VS Code工作区有一个GitHub远程,然后在Copilot Chat中:
1. 检查 `mcp.json` 语法(必须是有效的JSON)##🛠️ 可用工具
1. 验证服务器路径是否绝对正确
1. 确保已安装Node.js v18+(`node --version`)\`\`\`
1. 检查VS代码开发人员控制台是否有错误
### GitHub Tools(自动检测仓库)@workspace列出所有未解决的问题
### 工具未出现
- Verify server is running (Developer Console: "Connection state: Running")
- Check for "Discovered 11 tools" message| Tool | Description | Required Params |
- Reload window:
Cmd+Shift+P→ "Developer: Reload Window"
- Ensure tools are enabled per-agent/chat session|------|-------------|-----------------|The MCP will automatically detect your repository and list issues!
Authentication Errors| issue-create | Create an issue | title |
- Verify GitHub token scopes:
repo,project,read:org|issue-list| List issues | none |## 📚 Available Tools
- Check credentials in
mcp.jsonare correct
- Test token at https://github.com/settings/tokens|
issue-get| Get issue details |issue_number|
- Verify Azure credentials in Azure Portal
| issue-comment | Add comment | issue_number, body |### GitHub Tools (Auto-detect repo from workspace)
🎓 Configuration Notes
| issue-update | Update issue | issue_number |
Key Differences from Initial Design
| issue-close | Close issue | issue_number |#### issue-create
| Aspect | Initial Design | Actual Implementation |
|--------|---------------|----------------------|| project-get | Get project info | owner, number |Create a GitHub issue. No need to specify owner/repo.
| Config file | settings.json | mcp.json |
| Location | github.copilot.chat.mcpServers | servers in mcp.json || project-item-add | Add to project | projectId, contentId |
| Workspace vars | ${workspaceFolder} supported | Only in workspace configs |
| Repo detection | Automatic from workspace | Explicit owner/repo required || project-draft-issue | Create draft | projectId, title |```typescript
| Credentials | Direct in env | Uses inputs pattern |
{
Where to Configure
AI Tools title: string; // Required
- Global:
~/Library/Application Support/Code/User/mcp.json
- Available in all workspaces body?: string;
- Cannot use ${workspaceFolder} variables
- Must specify owner/repo explicitly| Tool | Description | labels?: string[];
- Workspace:
.vscode/mcp.json(optional)|------|-------------| owner?: string; // Optional: auto-detected
- Workspace-specific configuration
- Can use ${workspaceFolder} variables| ask-expert | Ask Azure OpenAI GPT-5 complex questions | repo?: string; // Optional: auto-detected
- Overrides global config
| ask-architect | Query architecture docs (.vscode/docs/ARCHITECTURE.md) |}
🤝 Contributing
欢迎投稿!请看 [贡献.md](CONTRIBUTING.md) 作为指导方针。
## 💡 示例
## 📝 许可证
**Copilot中的示例:**
MIT许可证-请参阅 [许可证](LICENSE) 了解详情。
### 问题管理\`\`\`
## 🆘 支持
创建一个标题为“修复登录错误”的问题,标签为“错误”
- **问题**: https://github.com/aponomy/knowing-mcp/issues
- **讨论**: https://github.com/aponomy/knowing-mcp/discussions\`\`\`\`\`\`
- **文档**:完整文档 [文档/部署.md](docs/DEPLOYMENT.md)
# 列出问题(自动检测当前仓库)
## 🔄 更新中
“列出所有未决问题”#### `issue-list`
要更新到最新版本:
“显示已关闭的bug”列出当前工作区存储库中的问题。
cd ~/Github/knowing-mcp
git pull origin main
npm install# Create issues```typescript
Reload VS Code: Cmd+Shift+P → "Developer: Reload Window"
## 🌟 Star History state?: "open" | "closed" | "all"; // Default: "open"
If you find this useful, please star the repo! ⭐# Get details limit?: number; // Default: 20
---"Show me issue #42" owner?: string; // Optional: auto-detected
**Built with** [Model Context Protocol](https://modelcontextprotocol.io/) | **Powered by** [Azure OpenAI](https://azure.microsoft.com/en-us/products/ai-services/openai-service)"What's the status of issue #123?" repo?: string; // Optional: auto-detected
}
# Update```
"Add comment to issue #42: 'Working on this'"
"Close issue #42 with comment 'Fixed in PR #43'"**Example:**
显示所有未解决的问题
AI协助\\\`
\\\#### issue-get`
专家咨询(需要Azure OpenAI)获取特定问题的详细信息。
“我需要专家帮助解决这个TypeScript问题。
问:我该如何解决\[问题\]?\\\`打字稿
背景:\[完整细节\]”{
issue_number:编号;//必填
架构问题(需要.vcode/docs/Architecture.md)所有者?:字符串;//可选:自动检测
“我们的断路器策略是什么?”回购?:字符串;//可选:自动检测
“我们该如何处理JOIN中断?”
## 🔧 How It Works**Example:**
- Workspace Detection: Reads
WORKSPACE_ROOTenvironment variableShow me issue #42
- Git Remote Parsing: Runs
git config --get remote.origin.url```
- URL Parsing: Extracts owner and repo from GitHub URL
- Caching: Caches repo info per workspace for performance####
issue-comment
- Tool Execution: Uses detected repo or allows overrideAdd a comment to an issue.
Supports:```typescript
- ✅ HTTPS:
https://github.com/owner/repo.git{
- ✅ SSH:
git@github.com:owner/repo.gitissue_number: number; // Required
body: string; // Required
📦 Installation Methods owner?: string; // Optional: auto-detected
repo?: string; // Optional: auto-detected
1. NPM (Recommended)}
npm install -g knowing-mcp
### 2. From SourceComment on issue #42: "This is fixed in the latest commit"
git clone https://github.com/Gullers-Grupp/knowing-mcp.git
cd knowing-mcp#### issue-update
npm installUpdate an issue's title, body, labels, or state.
npm link
{
### 3. Manual issue_number: number; // Required
git clone https://github.com/Gullers-Grupp/knowing-mcp.git body?: string;
cd knowing-mcp state?: "open" | "closed";
npm install labels?: string[];
Use full path in VS Code settings owner?: string; // Optional: auto-detected
}
See [docs/INSTALL.md](docs/INSTALL.md) for detailed instructions.```
## 🔐 Credentials**Example:**
Three options for storing credentials:Update issue #42 to add label "critical"
### Option 1: VS Code User Settings (Quick)
{Close an issue with an optional comment.
"github.copilot.chat.mcpServers": {
"knowing-mcp": {```typescript
"env": {{
"GH_TOKEN": "ghp_...", issue_number: number; // Required
"AZURE_OPENAI_API_KEY": "..." comment?: string;
} owner?: string; // Optional: auto-detected
} repo?: string; // Optional: auto-detected
}}
}```
**Example:**
### Option 2: Global Config File (Secure)```
Create ~/.knowing-mcp.env```
GH_TOKEN=ghp_...
AZURE_OPENAI_ENDPOINT=https://...### Project Tools
AZURE_OPENAI_API_KEY=...
project-get
Secure itGet GitHub Project information.
chmod 600 ~/.knowing-mcp.env
{
### Option 3: Environment Variables (Most Secure) owner: string; // Required
Add to ~/.zshrc or ~/.bashrc}
export GH_TOKEN="ghp_..."```
export AZURE_OPENAI_API_KEY="..."
Add an issue/PR to a GitHub Project (v2).
## 🧪 Testing
# Run test suite projectId: string; // Project Node ID
npm test contentId: string; // Issue/PR Node ID
}
# Expected output:```
# ✅ Detected GitHub repo: owner/repo
# ✅ Found .git directory#### `project-draft-issue`
# ✅ server.mjs foundCreate a draft issue directly in a project.
# ✅ All checks passed!
{
🤝 Contributing projectId: string; // Project Node ID
title: string;
Contributions welcome! See CONTRIBUTING.md. body?: string;
}
📄 License```
MIT © Gullers Grupp### AI Tools
🙏 Acknowledgments#### ask-expert
Ask complex technical questions to Azure OpenAI GPT-5 (o3-pro).
- Built on Model Context Protocol by Anthropic
- Uses @octokit/rest for GitHub API🚨 CRITICAL: The expert has NO chat history. Provide COMPLETE context every time.
- Supports Azure OpenAI
## 🐛 Issues & Support{
question: string; // Required: Your technical question
- **Bug Reports**: context: string; // Required: Full context (errors, code, what you tried)
- **Feature Requests**: reasoning_effort?: "low" | "medium" | "high"; // Default: "medium"
- **Discussions**: }
⭐ Star History
Example:
If you find this useful, please star the repo! ⭐```
I'm stuck on a complex TypeScript type inference issue.
Question: How do I make this generic type work?
Made with ❤️ for developers who work across multiple projects
Context:
- Using TypeScript 5.0
- Code: [paste code here]
- Error: [paste error here]
- What I tried: [describe attempts]
#### `ask-architect`
Answer architecture questions using the workspace's `.vscode/docs/ARCHITECTURE.md`.
{ question: string; // Required }
**Example:**What happens if Dataverse goes down?
The tool will:
1. Read `.vscode/docs/ARCHITECTURE.md` from current workspace
2. Send to Azure OpenAI for analysis (off Copilot's context)
3. Return answer with citations (section + line numbers)
4. Propose documentation edits if gaps are found
## 🔧 How It Works
### Automatic Repository Detection
The MCP server detects your GitHub repository by:
1. Reading `WORKSPACE_ROOT` environment variable (set by VS Code)
2. Checking if workspace has a `.git` directory
3. Running `git config --get remote.origin.url`
4. Parsing the URL to extract owner and repo
**Supported URL formats:**
- HTTPS: `https://github.com/owner/repo.git`
- SSH: `git@github.com:owner/repo.git`
### Credential Resolution
The server looks for credentials in this order:
1. **VS Code environment variables** (from User Settings `env` block)
2. **Global config file** (`~/.knowing-mcp.env`)
3. **Process environment** (system env vars)
This allows you to:
- Set credentials once in VS Code User Settings
- Use the MCP in any workspace
- Never commit credentials to repositories
### Workspace vs Global
**Workspace-scoped MCP** (old approach):// .vscode/settings.json (per workspace) { "github.copilot.chat.mcpServers": { "mcp-gullers-dev": { "command": "node", "args": ["./tools/mcp-gullers-dev/server.mjs"] } } }
**Global MCP** (knowing-mcp):// User Settings (all workspaces) { "github.copilot.chat.mcpServers": { "knowing-mcp": { "command": "node", "args": ["/absolute/path/to/knowing-mcp/server.mjs"], "env": { "WORKSPACE_ROOT": "${workspaceFolder}" } } } }
## 🆚 Differences from mcp-gullers-dev
| Feature | mcp-gullers-dev | knowing-mcp |
|---------|----------------|-------------|
| **Scope** | Single workspace | All workspaces |
| **Repo detection** | Manual (must specify owner/repo) | Automatic (from git remote) |
| **Credentials** | Workspace `.env` file | Global (VS Code User Settings or `~/.knowing-mcp.env`) |
| **Registration** | Workspace settings | User settings |
| **Path** | Relative (`./tools/...`) | Absolute |
| **Usage** | Only in gullers-platform | Any GitHub project |
## 🧪 Testing
### Test in Current Workspace
node test-connection.mjs
### Test Manual Operation
import { execSync } from 'child_process';
// Test git detection const remoteUrl = execSync('git config --get remote.origin.url', { encoding: 'utf8' }).trim();
console.log('Remote URL:', remoteUrl);
// Expected output: // Remote URL: git@github.com:Gullers-Grupp/platform.git // or // Remote URL: https://github.com/Gullers-Grupp/platform.git
## 🐛 Troubleshooting
### "Could not determine GitHub repository"
**Cause**: Not in a git repository or no GitHub remote configured.
**Solutions:**
1. Ensure workspace has a `.git` directory:git status
2. Check git remote:git remote -v
3. Add GitHub remote if missing:git remote add origin https://github.com/owner/repo.git
4. Or specify `owner` and `repo` explicitly:Create an issue in owner/repo with title "Bug fix"
### "Missing environment variable: GH_TOKEN"
**Cause**: Credentials not configured.
**Solution**: Add credentials to VS Code User Settings or create `~/.knowing-mcp.env` (see Setup above).
### MCP not showing in Copilot
**Causes:**
1. VS Code not reloaded after config change
2. Wrong server path in User Settings
3. Node.js not in PATH
**Solutions:**
1. Reload VS Code: `Cmd+Shift+P` → "Developer: Reload Window"
2. Verify absolute path in User Settings
3. Test server manually:node /path/to/knowing-mcp/server.mjs
### "Architecture document not found"
**Cause**: Workspace doesn't have `.vscode/docs/ARCHITECTURE.md`.
**Solution**:
- Create the file in your workspace
- Or use a different workspace that has architecture docs
- The `ask-architect` tool only works in workspaces with this file
## 📖 Example Workflows
### Bug Tracking Workflow
In Copilot Chat (any workspace with GitHub remote)
- "List all open bugs"
→ Shows issues with 'bug' label
- "Create issue: Login fails on Safari with title 'Safari login bug' and label 'bug'"
→ Creates issue in current repo
- "Add comment to issue #42: Reproduced on Safari 17.2"
→ Adds your comment
- "Close issue #42 with comment 'Fixed in PR #43'"
→ Closes issue with comment
### Architecture Research Workflow
In workspace with .vscode/docs/ARCHITECTURE.md
- "What's our circuit breaker strategy?"
→ ask-architect reads docs and answers with citations
- "How do we handle Dataverse outages?"
→ Answers from architecture doc
- If gaps found:
→ Tool proposes documentation updates → Review diffs in chat → Apply edits to improve docs
### Expert Consultation Workflow
Complex TypeScript problem
"I need expert help with this TypeScript issue.
Question: How do I infer return types for this generic builder pattern?
Context:
- TypeScript 5.0
- Builder pattern with fluent API
- Current error: [paste full error]
- Code snippet: [paste code]
- What I tried: [describe 3 failed attempts]
Use high reasoning effort."
→ Gets deep analysis from GPT-5 with extended thinking
## 🔐 Security Best Practices
1. **Never commit credentials** to git repositories
2. **Use Personal Access Tokens** with minimal scopes:
- `repo` (for private repos)
- `public_repo` (for public repos only)
- `project` (for GitHub Projects)
3. **Rotate tokens** regularly
4. **Use `.knowing-mcp.env`** with restricted permissions:chmod 600 ~/.knowing-mcp.env
5. **Consider VS Code Secret Storage** for production use (requires extension development)
## 🤝 Contributing
This MCP server is part of the Gullers Platform but designed to be generally useful.
**To extend:**
1. Add new tools to `TOOLS` array in `server.mjs`
2. Add tool handler in `switch` statement
3. Update README with examples
4. Test in multiple workspaces
## 📄 License
Part of the Gullers Platform - private use only.
## 🆘 Support
For issues:
1. Check troubleshooting section above
2. Test with `node test-connection.mjs`
3. Check VS Code Developer Console: `Help` → `Toggle Developer Tools`
4. Create issue in gullers-platform repository
---
**Built with ❤️ for developers who work across multiple projects**