chore: update SDK settings

Author: stainless-app[bot]

.github/workflows/publish-npm.yml

@@ -0,0 +1,53 @@
+# This workflow is triggered when a GitHub release is created.
+# It can also be run manually to re-publish to NPM in case it failed for some reason.
+# You can run this workflow by navigating to https://www.github.com/stainless-api/dbahn-stations-typescript/actions/workflows/publish-npm.yml
+name: Publish NPM
+on:
+  workflow_dispatch:
+    inputs:
+      path:
+        description: The path to run the release in, e.g. '.' or 'packages/mcp-server'
+        required: true
+
+  release:
+    types: [published]
+
+jobs:
+  publish:
+    name: publish
+    runs-on: ubuntu-latest
+    permissions:
+      contents: write
+
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Set up Node
+        uses: actions/setup-node@v3
+        with:
+          node-version: '20'
+
+      - name: Set up pnpm
+        uses: pnpm/action-setup@v4
+
+      - name: Install dependencies
+        run: |
+          pnpm install
+
+      - name: Publish to NPM
+        run: |
+          if [ -n "${{ github.event.inputs.path }}" ]; then
+            PATHS_RELEASED='[\"${{ github.event.inputs.path }}\"]'
+          else
+            PATHS_RELEASED='[\".\", \"packages/mcp-server\"]'
+          fi
+          pnpm tsn scripts/publish-packages.ts "{ \"paths_released\": \"$PATHS_RELEASED\" }"
+        env:
+          NPM_TOKEN: ${{ secrets.DBAHN_STATIONS_NPM_TOKEN || secrets.NPM_TOKEN }}
+
+      - name: Upload MCP Server DXT GitHub release asset
+        run: |
+          gh release upload ${{ github.event.release.tag_name }} \
+            packages/mcp-server/dbahn_stations_api.mcpb
+        env:
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}

.github/workflows/release-doctor.yml

@@ -18,4 +18,5 @@ jobs:
         run: |
           bash ./bin/check-release-environment
         env:
+          NPM_TOKEN: ${{ secrets.DBAHN_STATIONS_NPM_TOKEN || secrets.NPM_TOKEN }}
 

.stats.yml

@@ -1,4 +1,4 @@
 configured_endpoints: 4
 openapi_spec_url: https://storage.googleapis.com/stainless-sdk-openapi-specs/references%2Fdbahn-stations-2a72886a1ec37a86550e3c5137230284269a32a606b28816e214905c8b06f677.yml
 openapi_spec_hash: 7c2a8cbfc4afd14d0ea8dbb3c3eb2e6a
-config_hash: 5d8388386b6c9f4327ca7e907de5078f
+config_hash: 05f9ba56e7143961fa36c22bada6d450

CONTRIBUTING.md

@@ -91,3 +91,17 @@ To format and fix all lint issues automatically:
 ```sh
 $ pnpm fix
 ```
+
+## Publishing and releases
+
+Changes made to this repository via the automated release PR pipeline should publish to npm automatically. If
+the changes aren't made through the automated pipeline, you may want to make releases manually.
+
+### Publish with a GitHub workflow
+
+You can release to package managers by using [the `Publish NPM` GitHub action](https://www.github.com/stainless-api/dbahn-stations-typescript/actions/workflows/publish-npm.yml). This requires a setup organization or repository secret to be set up.
+
+### Publish manually
+
+If you need to manually release a package, you can run the `bin/publish-npm` script with an `NPM_TOKEN` set on
+the environment.

README.md

@@ -11,12 +11,9 @@ It is generated with [Stainless](https://www.stainless.com/).
 ## Installation
 
 ```sh
-npm install git+ssh://[email protected]:stainless-api/dbahn-stations-typescript.git
+npm install dbahn-stations
 ```
 
-> [!NOTE]
-> Once this package is [published to npm](https://www.stainless.com/docs/guides/publish), this will become: `npm install dbahn-stations`
-
 ## Usage
 
 The full API of this library can be found in [api.md](api.md).

bin/check-release-environment

@@ -2,6 +2,10 @@
 
 errors=()
 
+if [ -z "${NPM_TOKEN}" ]; then
+  errors+=("The NPM_TOKEN secret has not been set. Please set it in either this repository's secrets or your organization secrets")
+fi
+
 lenErrors=${#errors[@]}
 
 if [[ lenErrors -gt 0 ]]; then

packages/mcp-server/README.md

@@ -4,33 +4,18 @@ It is generated with [Stainless](https://www.stainless.com/).
 
 ## Installation
 
-### Building
+### Direct invocation
 
-Because it's not published yet, clone the repo and build it:
+You can run the MCP Server directly via `npx`:
 
 ```sh
-git clone [email protected]:stainless-api/dbahn-stations-typescript.git
-cd dbahn-stations-typescript
-./scripts/bootstrap
-./scripts/build
-```
-
-### Running
-
-```sh
-# set env vars as needed
 export DBAHN_STATIONS_CLIENT_ID="My Client ID"
 export DBAHN_STATIONS_CLIENT_SECRET="My Client Secret"
-node ./packages/mcp-server/dist/index.js
+npx -y dbahn-stations-mcp@latest
 ```
 
-> [!NOTE]
-> Once this package is [published to npm](https://www.stainless.com/docs/guides/publish), this will become: `npx -y dbahn-stations-mcp`
-
 ### Via MCP Client
 
-[Build the project](#building) as mentioned above.
-
 There is a partial list of existing clients at [modelcontextprotocol.io](https://modelcontextprotocol.io/clients). If you already
 have a client, consult their documentation to install the MCP server.
 
@@ -40,12 +25,8 @@ For clients with a configuration JSON, it might look something like this:
 {
   "mcpServers": {
     "dbahn_stations_api": {
-      "command": "node",
-      "args": [
-        "/path/to/local/dbahn-stations-typescript/packages/mcp-server",
-        "--client=claude",
-        "--tools=all"
-      ],
+      "command": "npx",
+      "args": ["-y", "dbahn-stations-mcp", "--client=claude", "--tools=all"],
       "env": {
         "DBAHN_STATIONS_CLIENT_ID": "My Client ID",
         "DBAHN_STATIONS_CLIENT_SECRET": "My Client Secret"
@@ -55,6 +36,29 @@ For clients with a configuration JSON, it might look something like this:
 }
 ```
 
+### Cursor
+
+If you use Cursor, you can install the MCP server by using the button below. You will need to set your environment variables
+in Cursor's `mcp.json`, which can be found in Cursor Settings > Tools & MCP > New MCP Server.
+
+[![Add to Cursor](https://cursor.com/deeplink/mcp-install-dark.svg)](https://cursor.com/en-US/install-mcp?name=dbahn-stations-mcp&config=eyJjb21tYW5kIjoibnB4IiwiYXJncyI6WyIteSIsImRiYWhuLXN0YXRpb25zLW1jcCJdLCJlbnYiOnsiREJBSE5fU1RBVElPTlNfQ0xJRU5UX0lEIjoiU2V0IHlvdXIgREJBSE5fU1RBVElPTlNfQ0xJRU5UX0lEIGhlcmUuIiwiREJBSE5fU1RBVElPTlNfQ0xJRU5UX1NFQ1JFVCI6IlNldCB5b3VyIERCQUhOX1NUQVRJT05TX0NMSUVOVF9TRUNSRVQgaGVyZS4ifX0)
+
+### VS Code
+
+If you use MCP, you can install the MCP server by clicking the link below. You will need to set your environment variables
+in VS Code's `mcp.json`, which can be found via Command Palette > MCP: Open User Configuration.
+
+[Open VS Code](https://vscode.stainless.com/mcp/%7B%22name%22%3A%22dbahn-stations-mcp%22%2C%22command%22%3A%22npx%22%2C%22args%22%3A%5B%22-y%22%2C%22dbahn-stations-mcp%22%5D%2C%22env%22%3A%7B%22DBAHN_STATIONS_CLIENT_ID%22%3A%22Set%20your%20DBAHN_STATIONS_CLIENT_ID%20here.%22%2C%22DBAHN_STATIONS_CLIENT_SECRET%22%3A%22Set%20your%20DBAHN_STATIONS_CLIENT_SECRET%20here.%22%7D%7D)
+
+### Claude Code
+
+If you use Claude Code, you can install the MCP server by running the command below in your terminal. You will need to set your
+environment variables in Claude Code's `.claude.json`, which can be found in your home directory.
+
+```
+claude mcp add --transport stdio dbahn_stations_api --env DBAHN_STATIONS_CLIENT_ID="Your DBAHN_STATIONS_CLIENT_ID here." DBAHN_STATIONS_CLIENT_SECRET="Your DBAHN_STATIONS_CLIENT_SECRET here." -- npx -y dbahn-stations-mcp
+```
+
 ## Exposing endpoints to your MCP Client
 
 There are three ways to expose endpoints as tools in the MCP server: