docs: Update README to remove missing image references

Maxim Titovich · Maxim Titovich · commit c6afbe17125a · 2025-03-10T09:22:45.000+01:00
diff --git a/README.md b/README.md
@@ -148,7 +148,7 @@ If you encounter the error "server.setRequestHandler is not a function" or simil
 2. Try reinstalling the package: `npm install -g cursor-azure-devops-mcp`
 3. Check that your `.env` file is correctly set up with your Azure DevOps credentials
 
-![Command Mode Setup](https://raw.githubusercontent.com/yourusername/cursor-azure-devops-mcp/main/docs/images/command-mode-setup.png)
+> **Note**: Screenshots for setup will be provided in a future update.
 
 #### Option 2: SSE Mode (Alternative)
 
@@ -177,7 +177,7 @@ The SSE mode connects to an HTTP server with Server-Sent Events:
    ```
 8. Click "Add"
 
-![SSE Mode Setup](https://raw.githubusercontent.com/yourusername/cursor-azure-devops-mcp/main/docs/images/sse-mode-setup.png)
+> **Note**: Screenshots for setup will be provided in a future update.
 
 ### Windows Users
 
@@ -305,191 +305,4 @@ To test the connection to Azure DevOps:
 
 ```bash
 npm run test-connection
-```
-
-## Publishing
-
-To publish to npm:
-
-```bash
-npm run build
-npm publish
-```
-
-## Continuous Integration and Deployment
-
-This project uses GitHub Actions for automated builds, testing, and publishing.
-
-### Status Badges
-
-The status badges at the top of the README provide real-time information about the project:
-
-- **CI**: Shows the status of the continuous integration workflow (build and tests)
-- **Publish**: Indicates the status of the npm publishing workflow
-- **Version Bump**: Indicates the status of the version bump workflow
-- **npm version**: Shows the latest published version on npm
-- **License**: Indicates the project license type
-
-### CI Workflow
-
-The CI workflow runs on every push to the main and develop branches, as well as on pull requests:
-
-- Builds the project with Node.js 16.x, 18.x, and 20.x
-- Runs linting and formatting checks
-- Performs security checks to prevent sensitive data exposure
-- Ensures the build completes successfully
-
-You can see the workflow details in `.github/workflows/ci.yml`.
-
-### CD Workflow (Publishing)
-
-The publishing workflow runs when:
-- Any change is pushed to the main branch (except documentation & config files)
-- A new GitHub release is created
-- Manually triggered via GitHub Actions interface
-
-It performs the following steps:
-1. Runs all checks and builds the package
-2. Extracts the package version from package.json
-3. Checks if that version already exists on npm
-4. If the version exists, automatically bumps the patch version
-5. Creates a GitHub release for the new version
-6. Publishes the package to npm
-
-To use this workflow, you need to:
-1. Add an `NPM_TOKEN` secret to your GitHub repository settings
-2. Either:
-   - Push code changes to the main branch (auto-versioning will handle the rest)
-   - Manually trigger the workflow from the Actions tab
-   - Create a GitHub release
-
-The workflow supports automatic version bumping when a version conflict is detected, making continuous delivery seamless without manual version management.
-
-You can see the workflow details in `.github/workflows/publish.yml`.
-
-## Troubleshooting
-
-### Summary of Common Issues and Solutions
-
-1. **Best Practices for Connection**:
-   - Use Command mode when possible (more reliable)
-   - If using SSE mode, set the port directly in the command line with `PORT=9836 npm run sse-server`
-   - Always verify the server is running before trying to connect from Cursor
-
-2. **Port Configuration**:
-   - The most reliable way to change the port is using the environment variable directly: `PORT=9836 npm run sse-server`
-   - Make sure to use the same port in Cursor when adding the MCP server: `http://localhost:9836/sse`
-
-3. **Session Management Issues**:
-   - If you see "Session not found" errors in the console, try restarting both the server and Cursor
-   - Clear Cursor's application data (Help > Clear Application Data) if problems persist
-
-4. **Connection Errors**:
-   - For "Failed to create client" errors, make sure the server is running and accessible
-   - Check that no firewalls or security software are blocking the connection
-   - Try using a different port if the default port (3000) is in use
-
-### MCP Server Not Connecting
-
-- Make sure your Azure DevOps credentials in the `.env` file are correct
-- Check that your personal access token has the necessary permissions:
-  - Code (read)
-  - Pull Request Threads (read)
-  - Work Items (read)
-- If using SSE mode, ensure the server is running before adding the MCP server in Cursor
-
-### Command Not Found
-
-- If running with npx, make sure you have Node.js installed
-- If using the global installation, try reinstalling: `npm install -g cursor-azure-devops-mcp`
-
-### SSE Connection Issues
-
-If you encounter JSON validation errors when connecting via SSE mode:
-
-1. **Use Command Mode Instead**: The command mode is more reliable and recommended for most users.
-
-2. **Check Cursor Version**: Ensure you're using Cursor version 0.46.9 or newer, as older versions had known issues with SSE connections.
-
-3. **Run with Debug Logs**: Start the SSE server with debug logs:
-   ```bash
-   DEBUG=* npm run sse-server
-   ```
-
-4. **Port Conflicts**: Make sure no other service is using port 3000. You can change the port by setting the `PORT` environment variable:
-   ```bash
-   PORT=3001 npm run sse-server
-   ```
-   Then use `http://localhost:3001/sse` as the SSE endpoint URL.
-
-5. **Network Issues**: Make sure your firewall isn't blocking the connection.
-
-6. **Verify Server is Running**: Make sure you can access the server's home page at `http://localhost:3000`
-
-### "Cannot set headers after they are sent to the client" Error
-
-If you encounter this error when running the SSE server:
-
-1. **Check for duplicate header settings**: This error occurs when the application tries to set HTTP headers after they've already been sent. In the SSE implementation, make sure you're not manually setting headers that the `SSEServerTransport` already sets.
-
-2. **Avoid manual header manipulation**: The `SSEServerTransport` class from the MCP SDK handles the necessary headers for SSE connections. Don't set these headers manually:
-   ```javascript
-   // Don't set these manually in your route handlers
-   res.setHeader('Content-Type', 'text/event-stream');
-   res.setHeader('Cache-Control', 'no-cache, no-transform');
-   res.setHeader('Connection', 'keep-alive');
-   ```
-
-3. **Check response handling**: Ensure you're not sending multiple responses to the same request. Each HTTP request should have exactly one response.
-
-### Port Configuration Issues
-
-If you're changing the port in your `.env` file but the server still runs on port 3000, try one of these solutions:
-
-1. **Set the PORT directly in the command line**:
-   ```bash
-   PORT=9836 npm run sse-server
-   ```
-   
-   This is the most reliable way to change the port. The server will output the actual port it's using:
-   ```
-   Server running on port 9836
-   SSE endpoint: http://localhost:9836/sse
-   Message endpoint: http://localhost:9836/message
-   ```
-
-2. **Verify your `.env` file is being loaded**:
-   Make sure your `.env` file is in the root directory of the project and has the correct format:
-   ```
-   PORT=9836
-   HOST=localhost
-   AZURE_DEVOPS_ORG_URL=https://dev.azure.com/your-organization
-   AZURE_DEVOPS_TOKEN=your-personal-access-token
-   AZURE_DEVOPS_PROJECT=YourProject
-   LOG_LEVEL=info
-   ```
-
-3. **Use Command mode instead**:
-   The Command mode is more reliable and doesn't require managing a separate HTTP server.
-
-### Connecting to Cursor with Custom Port
-
-If you're running the SSE server on a custom port (e.g., 9836), make sure to use the correct port when adding the MCP server in Cursor:
-
-1. Start the server with your custom port:
-   ```bash
-   PORT=9836 npm run sse-server
-   ```
-
-2. In Cursor IDE, when adding the MCP server, use the correct port in the SSE endpoint URL:
-   ```
-   http://localhost:9836/sse
-   ```
-
-## License
-
-MIT
-
-## Contributing
-
-Contributions are welcome! Please feel free to submit a Pull Request.
+```
