[claude]

Requested by Max Isbey · Slack thread

Description

Before: The repo ships a sequentialthinking reference server under src/sequentialthinking, and it is referenced across the README, AGENTS.md, the contributing/release/security docs, the .claude/skills guides, issue templates, two workflows, the smoke/sweep/release scripts and their tests, and the root package.json and lockfile.

After: The server directory and every reference to it are gone. Server counts in docs and scripts now say six servers (three TypeScript, three Python), the smoke and sweep scripts no longer try to launch it, and the lockfile no longer carries its workspace entry or its unused transitive dependencies.

How: git rm -r src/sequentialthinking; removed its entries from README.md, AGENTS.md, CONTRIBUTING.md, RELEASING.md, SECURITY.md, .changeset/README.md, docs/ai-software-factory.md, the skill guides under .claude/skills/, the two issue-template dropdowns, sdk-watch.yml and typescript.yml comments, scripts/smoke-servers.mjs and scripts/lib/sweep.mjs plus their tests; dropped the dependency from the root package.json; regenerated package-lock.json with the repo's tooling (only the removed workspace and its unused transitive deps changed). docs/agent-guidance-inception.md and docs/contribution-model.md are left as-is since they describe the state at the time they were written.

Server Details

• Server: sequentialthinking
• Changes to: entire server removed

Motivation and Context

Remove the sequentialthinking server and all references to it from the repository.

How Has This Been Tested?

At the repo root on Node 22: npm ci, npm run build, npm test --workspaces --if-present (everything 258, filesystem 340, memory 175 passed), and npm run validate:guards (format, lint, coverage, skills, action-pin and script tests, 689 passed). A case-insensitive grep for sequential.?thinking|server-sequential-thinking across the tree returns nothing.

Breaking Changes

The @modelcontextprotocol/server-sequential-thinking package will no longer be built or published from this repository.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update

Checklist

• I have read the MCP Protocol Documentation
• My changes follows MCP security best practices
• I have updated the server's README accordingly
• I have tested this with an LLM client
• My code follows the repository's style guidelines
• New and existing tests pass locally
• I have added appropriate error handling

Additional context

Merged main on 2026-10-11 to resolve conflicts with the repository tooling overhaul; the diff is 51 files, 69 insertions, 2444 deletions. No changeset is added because no remaining package's version changes.

🤖 Generated with Claude Code

https://claude.ai/code/session_01WgDQSktc6zqp83pR1Y4qgZ

---

Generated by Claude Code

[changeset-bot]

⚠️ No Changeset found

Latest commit: 13710f0

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[cliffhall]

@maxisbey

Not sure why the maintainers weren't consulted about this and no reason was stated for the removal. This server still gets nearly 100k downloads per week from npm. We are in the midst of a refactor to modern era for all our servers, which are primarily of instructional use.

If you feel this was closed in error, please contact us in the MCP Contributors Discord's #reference-servers-dev channel.