Enhance documentation and build process for MCP server

- Update the build process to improve development efficiency using `tsup`.
- Revise README to provide clearer instructions and enhance understanding of MCP server capabilities.
- Include new details and features related to incident management and Datadog integration.

Signed-off-by: katsumata <12413150+winor30@users.noreply.github.com>

Author: winor30

README.md

@@ -1,76 +1,129 @@
 # Datadog MCP Server
 
-MCP server for interacting with Datadog API
+MCP server for the Datadog API, enabling incident management and more.
 
-This is a TypeScript-based MCP server that implements a simple notes system. It demonstrates core MCP concepts by providing:
+## Features
 
-- Resources representing text notes with URIs and metadata
-- Tools for creating new notes
-- Prompts for generating summaries of notes
+- **Incident Management**: Enable listing and retrieving Datadog incidents through dedicated tools.
+- **Extensible Design**: Intended for future integrations with additional Datadog APIs.
 
-## Features
+## Tools
 
-### Resources
+1. `list_incidents`
 
-- List and access notes via `note://` URIs
-- Each note has a title, content and metadata
-- Plain text mime type for simple content access
+   - Retrieve a list of incidents from Datadog.
+   - **Inputs**:
+     - `filter` (optional string): Filter parameters for incidents (e.g., status, priority).
+     - `pagination` (optional object): Pagination details like page size/offset.
+   - **Returns**: Array of Datadog incidents and associated metadata.
 
-### Tools
+2. `get_incident`
 
-- `create_note` - Create new text notes
-  - Takes title and content as required parameters
-  - Stores note in server state
+   - Retrieve detailed information about a specific Datadog incident.
+   - **Inputs**:
+     - `incident_id` (string): Incident ID to fetch details for.
+   - **Returns**: Detailed incident information (title, status, timestamps, etc.).
 
-### Prompts
+3. _(Planned)_: Additional tools for creating, updating, or resolving incidents, as well as for managing other Datadog resources (e.g., dashboards, monitors).
 
-- `summarize_notes` - Generate a summary of all stored notes
-  - Includes all note contents as embedded resources
-  - Returns structured prompt for LLM summarization
+## Setup
 
-## Development
+### Datadog Credentials
 
-Install dependencies:
+You need valid Datadog API credentials to use this MCP server:
 
-```bash
-npm install
-```
+- `DATADOG_API_KEY`: Your Datadog API key
+- `DATADOG_APP_KEY`: Your Datadog Application key
+- `DATADOG_SITE` (optional): The Datadog site (e.g. `datadoghq.eu`)
 
-Build the server:
+Export them in your environment before running the server:
 
 ```bash
-npm run build
+export DATADOG_API_KEY="your_api_key"
+export DATADOG_APP_KEY="your_app_key"
+export DATADOG_SITE="your_datadog_site"
 ```
 
-For development with auto-rebuild:
+## Installation
 
 ```bash
-npm run watch
+pnpm install
+pnpm build
+pnpm watch   # for development with auto-rebuild
 ```
 
-## Installation
+## Usage with Claude Desktop
 
-To use with Claude Desktop, add the server config:
+To use this with Claude Desktop, add the following to your `claude_desktop_config.json`:
 
-On MacOS: `~/Library/Application Support/Claude/claude_desktop_config.json`
+On MacOS: `~/Library/Application Support/Claude/claude_desktop_config.json`  
 On Windows: `%APPDATA%/Claude/claude_desktop_config.json`
 
+```json
+{
+  "mcpServers": {
+    "github": {
+      "command": "npx",
+      "args": ["-y", "@modelcontextprotocol/server-github"],
+      "env": {
+        "GITHUB_PERSONAL_ACCESS_TOKEN": "<YOUR_TOKEN>"
+      }
+    }
+  }
+}
+```
+
+```json
+{
+  "mcpServers": {
+    "datadog": {
+      "command": "/path/to/mcp-server-datadog/build/index.js",
+      "env": {
+        "DATADOG_API_KEY": "<YOUR_API_KEY>",
+        "DATADOG_APP_KEY": "<YOUR_APP_KEY>",
+        "DATADOG_SITE": "<YOUR_SITE>" // Optional
+      }
+    }
+  }
+}
+```
+
+Or specify via `npx`:
+
 ```json
 {
   "mcpServers": {
     "mcp-server-datadog": {
-      "command": "/path/to/mcp-server-datadog/build/index.js"
+      "command": "npx",
+      "args": ["-y", "@winor30/mcp-server-datadog"],
+      "env": {
+        "DATADOG_API_KEY": "<YOUR_API_KEY>",
+        "DATADOG_APP_KEY": "<YOUR_APP_KEY>",
+        "DATADOG_SITE": "<YOUR_SITE>" // Optional
+      }
     }
   }
 }
 ```
 
-### Debugging
+## Debugging
 
-Since MCP servers communicate over stdio, debugging can be challenging. We recommend using the [MCP Inspector](https://github.com/modelcontextprotocol/inspector), which is available as a package script:
+Because MCP servers communicate over standard input/output, debugging can sometimes be tricky. We recommend using the [MCP Inspector](https://github.com/modelcontextprotocol/inspector). You can run the inspector with:
 
 ```bash
 npm run inspector
 ```
 
-The Inspector will provide a URL to access debugging tools in your browser.
+The inspector will provide a URL you can open in your browser to see logs and send requests manually.
+
+## Contributing
+
+Contributions are welcome! Feel free to open an issue or a pull request if you have any suggestions, bug reports, or improvements to propose.
+
+## License
+
+This project is licensed under the [MIT License](./LICENSE).
+
+```
+
+```

package.json

@@ -25,7 +25,7 @@
   "scripts": {
     "build": "tsup &&  node -e \"require('fs').chmodSync('build/index.js', '755')\"",
     "prepare": "npm run build",
-    "watch": "tsc --watch",
+    "watch": "tsup --watch",
     "inspector": "npx @modelcontextprotocol/inspector build/index.js",
     "lint": "eslint . --ext .ts,.js",
     "format": "prettier --write ."