Skip to content

Add MCP360 platform to README#3511

Open
ankurDelta4 wants to merge 2 commits intomodelcontextprotocol:mainfrom
ankurDelta4:main
Open

Add MCP360 platform to README#3511
ankurDelta4 wants to merge 2 commits intomodelcontextprotocol:mainfrom
ankurDelta4:main

Conversation

@ankurDelta4
Copy link

Description

Publishing Your Server

Note: We are no longer accepting PRs to add servers to the README. Instead, please publish your server to the MCP Server Registry to make it discoverable to the MCP ecosystem.

To publish your server, follow the quickstart guide. You can browse published servers at https://registry.modelcontextprotocol.io/.

Server Details

  • Server:
  • Changes to:

Motivation and Context

How Has This Been Tested?

Breaking Changes

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)
  • [ x] Documentation update

Checklist

  • [ x] I have read the MCP Protocol Documentation
  • My changes follows MCP security best practices
  • [ x] 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
  • I have documented all environment variables and configuration options

Additional context

@ankurDelta4
Copy link
Author

The CI failures are due to pre-existing repo issues unrelated to this documentation-only PR:

  1. Python / Build fetch, git, time failures: These are caused by an outdated uv.lock lockfile (the error message states "The lockfile at uv.lock needs to be updated, but --locked was provided"). This is a repo-wide dependency issue that needs to be fixed on main, not something introduced by README changes.

  2. README PR Check / check-readme-only failure: The error "Resource not accessible by integration" indicates a GitHub API authentication/permission issue with the check script itself, not a problem with the README content. My MCP360 entries follow the correct markdown format [text](url) used throughout the file, consistent with all other entries.

Since this is a documentation-only update, these CI infrastructure issues should not block the PR from being reviewed and merged.

CC: @modelcontextprotocol/maintainers

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant