spences10 / spences10/mcp-sequentialthinking-tools
Add project to MCP registry
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 590
- Forks
- 84
- PR merge metrics
- No merged PRs in 30d
Description
Add MCP registry publishing to this project:
-
Add to package.json:
- "mcpName": "io.github.spences10/[PROJECT-NAME]"
- Scripts:
- "sync-server-json": "node -e "const pkg = require('./package.json'); const server =
require('./server.json'); server.version = pkg.version; server.packages[0].version = pkg.version;
require('fs').writeFileSync('./server.json', JSON.stringify(server, null, 2));"" - "publish-mcp": "pnpm run sync-server-json && mcp-publisher publish"
- "sync-server-json": "node -e "const pkg = require('./package.json'); const server =
-
Add to .gitignore: ".mcpregistry_*"
-
Run: mcp-publisher init
-
Update server.json to match package version and remove any dummy environment variables
-
Authenticate once: mcp-publisher login github
-
Publish: pnpm run publish-mcp
Future workflow: After publishing to npm, just run pnpm run publish-mcp
Replace [PROJECT-NAME] with each tool's name. The authentication persists across projects so you only need step 5
once.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with package.json, .gitignore, and server.json, then verify how the current package version and server metadata are represented. Follow the issue's mcp-publisher init, login, and pnpm publish-mcp steps. Done means the registry metadata is valid, dummy environment variables are removed, and publishing completes successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- release, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100