bump sdk version, update readme

Author: jsendo

modelcontextprotocol/README.md

@@ -39,6 +39,31 @@ If you're running MCP servers for your app, you'll likely want to use the [SSE i
 
 If your user `123` wants to connect to the `slack` MCP server, your MCP client would make a request to the `/123/slack` route. [See the SSE docs below](#sse) for more detail.
 
+### Running the server via locally for development
+
+sse
+```bash
+npm run dev:sse
+```
+
+stdio
+```bash
+npm run dev:stdio
+```
+
+optionally you can add add the env var `PD_SDK_DEBUG=true` to the above commands to dump requests and responses to the Pipecream Connect API.
+
+sse
+```bash
+PD_SDK_DEBUG=true npm run dev:sse
+```
+
+stdio
+```bash
+PD_SDK_DEBUG=true npm run dev:stdio
+```
+
+
 ### Running the server via `npx`
 
 Pipedream MCP servers provide [two interfaces](https://modelcontextprotocol.io/docs/concepts/architecture#transport-layer) clients can connect to:

modelcontextprotocol/package-lock.json

@@ -7,8 +7,8 @@
     "@pipedream/mcp": "./dist/src/cli.js"
   },
   "scripts": {
-    "dev:stdio": "tsx watch src/stdio.ts",
-    "dev:sse": "tsx watch src/sse.ts",
+    "dev:stdio": "tsx watch -r dotenv/config src/stdio.ts",
+    "dev:sse": "tsx watch -r dotenv/config src/sse.ts",
     "start:stdio": "tsx src/cli.ts stdio",
     "start:sse": "tsx src/cli.ts sse",
     "start:stdio:app": "tsx src/cli.ts stdio --app",
@@ -20,7 +20,7 @@
   },
   "dependencies": {
     "@modelcontextprotocol/sdk": "^1.7.0",
-    "@pipedream/sdk": "^1.4.0",
+    "@pipedream/sdk": "^1.5.2",
     "commander": "^13.1.0",
     "cors": "^2.8.5",
     "express": "^4.21.2",

modelcontextprotocol/package.json

@@ -160,7 +160,7 @@ export async function main(appName?: string, portOption?: string) {
   })
 
   app
-    .listen(port, () => {
+    .listen(port,"0.0.0.0", () => {
       console.log(`Server is running on port ${port}`)
       console.log("Routes configured:")
       console.log("- GET / - Health check")