Rename mcp.json to server.json (#106)
<!-- Provide a brief summary of your changes --> Rename mcp.json to server.json ## Motivation and Context <!-- Why is this change needed? What problem does it solve? --> ## How Has This Been Tested? <!-- Have you tested this in a real application? Which scenarios were tested? --> ## Breaking Changes <!-- Will users need to update their code or configurations? --> ## Types of changes <!-- What types of changes does your code introduce? Put an `x` in all the boxes that apply: --> - [ ] 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 <!-- Go over all the following points, and put an `x` in all the boxes that apply. --> - [ ] I have read the [MCP Documentation](https://modelcontextprotocol.io) - [ ] My code follows the repository's style guidelines - [ ] New and existing tests pass locally - [ ] I have added appropriate error handling - [ ] I have added or updated documentation as needed ## Additional context <!-- Add any other context, implementation notes, or design decisions --> Related to #86 Co-authored-by: Avinash Sridhar <sridharavinash@users.noreply.github.com>
This commit is contained in:
parent
3df06d38d9
commit
d16328e8c1
1 changed files with 5 additions and 5 deletions
|
|
@ -47,7 +47,7 @@ The tool has been simplified to use **GitHub OAuth device flow authentication ex
|
|||
|
||||
## Example
|
||||
|
||||
1. Prepare your `mcp.json` file with your server details:
|
||||
1. Prepare your `server.json` file with your server details:
|
||||
|
||||
```json
|
||||
{
|
||||
|
|
@ -90,7 +90,7 @@ The tool has been simplified to use **GitHub OAuth device flow authentication ex
|
|||
2. Run the publisher tool:
|
||||
|
||||
```bash
|
||||
./bin/mcp-publisher --registry-url "https://mcp-registry.example.com" --mcp-file "./mcp.json"
|
||||
./bin/mcp-publisher --registry-url "https://mcp-registry.example.com" --mcp-file "./server.json"
|
||||
```
|
||||
|
||||
3. Follow the authentication instructions in the terminal if prompted.
|
||||
|
|
@ -103,5 +103,5 @@ The tool has been simplified to use **GitHub OAuth device flow authentication ex
|
|||
- **Automatic Client ID**: The GitHub Client ID is automatically retrieved from the registry's health endpoint
|
||||
- **Token Storage**: The authentication token is saved in `.mcpregistry_token` in the current directory
|
||||
- **Internet Required**: Active internet connection needed for GitHub authentication and registry communication
|
||||
- **Repository Access**: Ensure the repository and package mentioned in your `mcp.json` file exist and are accessible
|
||||
- **Repository Access**: Ensure the repository and package mentioned in your `server.json` file exist and are accessible
|
||||
- **OAuth Permissions**: You may need to grant the OAuth app access to your GitHub organizations if publishing org repositories
|
||||
|
|
|
|||
Loading…
Reference in a new issue