release: 0.1.0

[stainless-app]

Automated Release PR

0.1.0 (2025-12-18)

Full Changelog: v0.0.20...v0.1.0

⚠ BREAKING CHANGES

• mcp: remove deprecated tool schemes
• mcp: Migration: To migrate, simply modify the command used to invoke the MCP server. Currently, the only supported tool scheme is code mode. Now, starting the server with just node /path/to/mcp/server or npx package-name will invoke code tools: changing your command to one of these is likely all you will need to do.

Features

• api: api update (691249c)
• api: api update (9935b0a)

Bug Fixes

• mcp: pass base url to code tool (153ba08)

Chores

• mcp: remove deprecated tool schemes (ee26040)

---

This pull request is managed by Stainless's GitHub App.

The semver version number is based on included commit messages. Alternatively, you can manually set the version number in the title of this pull request.

For a better experience, it is recommended to use either rebase-merge or squash-merge when merging this pull request.

🔗 Stainless website
📚 Read the docs
🙋 Reach out for help or questions

[stainless-app]

🧪 Testing

To try out this version of the SDK, run:

npm install 'https://pkg.stainless.com/s/whopsdk-typescript/ee26040ec829994318a21acbe5ae344c6d3f435f/dist.tar.gz'

Expires at: Sat, 17 Jan 2026 21:00:33 GMT
Updated at: Thu, 18 Dec 2025 21:00:33 GMT

[sentry]

Bug: The stdio server transport silently ignores CLI options for tool selection because the options object is not passed to launchStdioServer, causing default tools to always be enabled.
_{Severity: HIGH | Confidence: High}

🔍 Detailed Analysis

When the server is launched in stdio mode, command-line options for tool selection (like --no-tools docs) are ignored. This happens because launchStdioServer() is called without the options argument from index.ts. Consequently, inside initMcpServer, selectTools is called with undefined, and its options?.includeDocsTools ?? true logic defaults to true, always enabling the docsSearchTool. This creates a discrepancy where the tools logged at startup don't match the tools actually available to the server, which could confuse users.

💡 Suggested Fix

Pass the options object to launchStdioServer in index.ts. Update the launchStdioServer function signature in stdio.ts to accept options?: McpOptions. Then, pass these options when calling initMcpServer within launchStdioServer: initMcpServer({ server, mcpOptions: options }).

🤖 Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: packages/mcp-server/src/index.ts#L18-L24

Potential issue: When the server is launched in `stdio` mode, command-line options for
tool selection (like `--no-tools docs`) are ignored. This happens because
`launchStdioServer()` is called without the `options` argument from `index.ts`.
Consequently, inside `initMcpServer`, `selectTools` is called with `undefined`, and its
`options?.includeDocsTools ?? true` logic defaults to `true`, always enabling the
`docsSearchTool`. This creates a discrepancy where the tools logged at startup don't
match the tools actually available to the server, which could confuse users.

_{Did we get this right? 👍 / 👎 to inform future reviews.
Reference ID: 7727890}