REMOTE_SERVER_TRANSPORT_MODULE reference

Author: hillarysanders

Procfile

@@ -1,2 +1,2 @@
-web: uvicorn src.${REMOTE_SERVER_TYPE:-streamable_http_server}:app --host=0.0.0.0 --port=${PORT:-8000} --workers=${WEB_CONCURRENCY:-1}
+web: uvicorn src.${REMOTE_SERVER_TRANSPORT_MODULE:-streamable_http_server}:app --host=0.0.0.0 --port=${PORT:-8000} --workers=${WEB_CONCURRENCY:-1}
 mcp-python: python -m src.stdio_server

README.md

@@ -36,7 +36,7 @@ heroku buildpacks:set heroku/python -a $APP_NAME
 heroku config:set API_KEY=$(openssl rand -hex 32) -a $APP_NAME
 heroku config:set STDIO_MODE_ONLY=<true/false> -a $APP_NAME
 # set the remote server type (module) that your web process will use (only relevant for web deployments)
-heroku config:set REMOTE_SERVER_TYPE=<streamable_http_server/sse_server>
+heroku config:set REMOTE_SERVER_TRANSPORT_MODULE=<streamable_http_server/sse_server>
 ```
 *Note: we recommend setting `STDIO_MODE_ONLY` to `true` for security and code execution isolation security in non-dev environments.*
 
@@ -157,7 +157,7 @@ You only need to do this once, unless you spin back down to 0 web dynos to save
 
 By default, this app deploys a Streamable HTTP MCP server - if you want to deploy an SSE server, run:
 ```bash
-heroku config:set REMOTE_SERVER_TYPE=sse_server
+heroku config:set REMOTE_SERVER_TRANSPORT_MODULE=sse_server
 ```
 Which will affect which server is run in the Procfile.
 

app.json

@@ -16,7 +16,7 @@
             "description": "Only allow tool requests via STDIO mode?",
             "value": "false"
         },
-        "REMOTE_SERVER_TYPE": {
+        "REMOTE_SERVER_TRANSPORT_MODULE": {
             "description": "Tranport module name used for deployed web app (applicable when web formation size is >0). `streamable_http_server` or `sse_server`.",
             "value": "streamable_http_server"
         }

tests/README.md

@@ -9,7 +9,7 @@ These pytest tests run **every MCP transport** this repo supports, both locally
 | `http_local`      | Streamable HTTP on `localhost:8000/mcp/`                  | — |
 | `sse_local`       | SSE on `localhost:8000/mcp/sse`                           | — |
 | `stdio_local`     | STDIO (example client boots its own server)               | — |
-| `remote`          | Transport named in **`$REMOTE_SERVER_TYPE`** (`streamable_http_server` or `sse_server`) served by your web dyno | **Yes** |
+| `remote`          | Transport named in **`$REMOTE_SERVER_TRANSPORT_MODULE`** (`streamable_http_server` or `sse_server`) served by your web dyno | **Yes** |
 | `remote_stdio`    | STDIO via a **one-off Heroku dyno**                       | **No** – works even at `web=0` |
 
 *If the web dyno is asleep or scaled to `0`, the `remote` tests auto-skip.