Skip to content

Conversation

@mcpm-registry-bot
Copy link
Contributor

Summary

This PR adds a new MCP server manifest generated from the repository: https://github.com/modelcontextprotocol/servers/tree/main/src/memory

Changes

  • Added new manifest JSON file in mcp-registry/servers/
  • Manifest was automatically generated using the chatxiv.org API

Test plan

  • Verify the generated JSON is valid
  • Check that all required fields are present
  • Validate installation instructions work correctly

🤖 Generated with Claude Code

@coderabbitai
Copy link

coderabbitai bot commented Aug 18, 2025

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Join our Discord community for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

  • Visit our Status Page to check the current availability of CodeRabbit.
  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@qodo-merge-pro
Copy link
Contributor

CI Feedback 🧐

A test triggered by this PR failed. Here is an AI-generated analysis of the failure:

Action: validate-manifests

Failed stage: Validate Server JSON Files [❌]

Failure summary:

The action failed while validating JSON files in mcp-registry/servers. It reported that
mcp-registry/servers/modelcontextprotocol-servers.json is not valid JSON:
- Error: SyntaxError: Bad
control character in string literal in JSON at position 240
- After successfully parsing several
other JSON files, the workflow stopped on this file and exited with Failed because of file error.

Relevant error logs:
1:  ##[group]Runner Image Provisioner
2:  Hosted Compute Agent
...

234:  Contents of 'mcp-registry/servers/notion-mcp.json' has been parsed as json object
235:  Contents of 'mcp-registry/servers/netket.json' has been parsed as json object
236:  Contents of 'mcp-registry/servers/neovim.json' has been parsed as json object
237:  Contents of 'mcp-registry/servers/neo4j.json' has been parsed as json object
238:  Contents of 'mcp-registry/servers/nemad.json' has been parsed as json object
239:  Contents of 'mcp-registry/servers/needle-mcp.json' has been parsed as json object
240:  Contents of 'mcp-registry/servers/naver.json' has been parsed as json object
241:  Contents of 'mcp-registry/servers/nasa.json' has been parsed as json object
242:  Contents of 'mcp-registry/servers/n8n.json' has been parsed as json object
243:  Contents of 'mcp-registry/servers/mysql.json' has been parsed as json object
244:  Contents of 'mcp-registry/servers/multicluster-mcp-sever.json' has been parsed as json object
245:  Contents of 'mcp-registry/servers/mssql.json' has been parsed as json object
246:  Contents of 'mcp-registry/servers/mongodb.json' has been parsed as json object
247:  Contents of 'mcp-registry/servers/mongodb-lens.json' has been parsed as json object
248:  Contents of 'mcp-registry/servers/monday-com.json' has been parsed as json object
249:  ##[error]Error: Contents of 'mcp-registry/servers/modelcontextprotocol-servers.json' aren't a valid json: json: SyntaxError: Bad control character in string literal in JSON at position 240
250:  ##[error]Failed because of file error
251:  Post job cleanup.

@mcpm-registry-bot mcpm-registry-bot bot force-pushed the add-manifest-modelcontextprotocol-servers-tree-main-src-memory branch from ced4e9a to e37471d Compare August 21, 2025 03:39
@mcpm-registry-bot mcpm-registry-bot bot force-pushed the add-manifest-modelcontextprotocol-servers-tree-main-src-memory branch from e37471d to 175daff Compare August 21, 2025 03:40
@JoJoJoJoJoJoJo JoJoJoJoJoJoJo changed the title feat: Add MCP manifest for modelcontextprotocol-servers-tree-main-src-memory chore: Add MCP manifest for modelcontextprotocol-servers-tree-main-src-memory Aug 23, 2025
@GabrielDrapor
Copy link
Contributor

  • [ ]

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.

2 participants