Glean MCP Server implementation

.github/workflows/ci.yml

@@ -0,0 +1,37 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+    branches: [main]
+
+jobs:
+  test:
+    name: Test
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        node-version: [18.x, 20.x, 22.x]
+    env:
+      VOLTA_FEATURE_PNPM: 1
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+
+      - name: Setup Node.js and pnpm with Volta
+        uses: volta-cli/action@v4
+        with:
+          node-version: ${{ matrix.node-version }}
+
+      - name: Install dependencies
+        run: pnpm install --frozen-lockfile
+
+      - name: Run linter
+        run: pnpm lint
+
+      - name: Build
+        run: pnpm build
+
+      - name: Run tests
+        run: pnpm test

CONTRIBUTING.md

@@ -0,0 +1,73 @@
+# Contributing to @gleanwork/mcp-server
+
+Thank you for your interest in contributing to the Glean MCP Server! This document provides guidelines and instructions for development.
+
+## Development Setup
+
+1. Clone the repository:
+
+```bash
+git clone https://github.com/gleanwork/mcp-server.git
+cd mcp-server
+```
+
+1. Install dependencies:
+
+```bash
+pnpm install
+```
+
+1. Run tests:
+
+```bash
+pnpm test
+```
+
+1. Build the project:
+
+```bash
+pnpm run build
+```
+
+## Running the Server Locally
+
+The server communicates via stdio, making it ideal for integration with AI models and other tools:
+
+```bash
+node build/index.js
+```
+
+Input and output follow the JSON-RPC 2.0 protocol, with each message on a new line.
+
+## Making Changes
+
+1. Fork the repository
+2. Create your feature branch: `git checkout -b feature/my-feature`
+3. Commit your changes: `git commit -am 'Add new feature'`
+4. Push to the branch: `git push origin feature/my-feature`
+5. Submit a pull request
+
+## Code Style
+
+- Use TypeScript for all new code
+- Follow the existing code style (enforced by ESLint and Prettier)
+- Include JSDoc comments for public APIs
+- Write tests for new functionality
+
+## Testing
+
+- Add unit tests for new features
+- Ensure all tests pass before submitting a pull request
+- Use the provided test utilities and fixtures
+
+## Documentation
+
+- Update documentation for any changed functionality
+- Include examples for new features
+- Keep the README.md and API documentation up to date
+
+## Need Help?
+
+- Documentation: [docs.glean.com](https://docs.glean.com)
+- Issues: [GitHub Issues](https://github.com/gleanwork/mcp-server/issues)
+- Email: [support@glean.com](mailto:support@glean.com)

LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2020 gleanwork/mcp-server
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.