docs: add degit usage and MCP Inspector instructions to README #18
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
This PR addresses issue #[issue_number] by updating the README to provide easier setup instructions for users wanting to create a new MCP server from this template.
Changes
Simplified Getting Started with
degitThe primary method for creating a new project is now using
degit, which allows users to scaffold a new project with a single command:npx degit nickytonline/mcp-typescript-template my-mcp-server cd my-mcp-serverThis eliminates the need for users to:
.gitdirectoryThe original GitHub template approach is still documented as an alternative method for users who prefer that workflow.
Added MCP Inspector Documentation
A new "Testing Your MCP Server" section documents how to use the MCP Inspector for testing and debugging:
This section explains what the inspector provides:
Benefits
Verification
Closes #[issue_number]
Original prompt
Fixes #10
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.