spences10 / spences10/mcp-sequentialthinking-tools

Add project to MCP registry

Open
#40 0 comments 0 reactions 0 assignees View on GitHub

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:

  1. 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"
  2. Add to .gitignore: ".mcpregistry_*"

  3. Run: mcp-publisher init

  4. Update server.json to match package version and remove any dummy environment variables

  5. Authenticate once: mcp-publisher login github

  6. 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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. 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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.