Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: add Rijksmuseum MCP server to community servers list #410

Merged

Conversation

r-huijts
Copy link
Contributor

Description

Add Rijksmuseum MCP server to the community servers section in README.md. This server enables LLMs to interact with the Rijksmuseum API, allowing them to search artworks, retrieve artwork details, access image tiles, and explore user collections from Amsterdam's famous museum.

Server Details

  • Server: N/A (documentation update only)
  • Changes to: README.md community servers list

Motivation and Context

This addition enriches the MCP ecosystem by providing access to one of the world's largest art collections through the Rijksmuseum API. This enables LLMs to access and analyze art historical data, images, and cultural heritage information.

How Has This Been Tested?

N/A - This is a documentation update only, adding a reference to an external server.

Breaking Changes

No breaking changes - this is an additive change to the README.md file.

Types of changes

  • Documentation update

Checklist

  • I have read the MCP Protocol Documentation
  • My changes follows MCP security best practices
  • I have updated the server's README accordingly
  • My code follows the repository's style guidelines
  • I have added appropriate error handling
  • I have documented all environment variables and configuration options

Additional context

The Rijksmuseum server repository includes comprehensive documentation, setup instructions, and usage examples. The server follows the established pattern of other community servers in the README.md file.

@dsp-ant dsp-ant force-pushed the main branch 27 times, most recently from e72628a to 8622936 Compare January 13, 2025 20:47
@dsp-ant dsp-ant force-pushed the main branch 14 times, most recently from c114833 to 4f3dc11 Compare January 14, 2025 03:05
Copy link
Contributor

@jerome3o-anthropic jerome3o-anthropic left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is so cool! unfortunately it looks like some other changes have bubbled in some how, once the diff is only affecting your server definition i'd be happy to merge

removing erroneous diffs
@jerome3o-anthropic jerome3o-anthropic self-requested a review January 30, 2025 01:47
Copy link
Contributor

@jerome3o-anthropic jerome3o-anthropic left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just fixed the diff while I was here

@r-huijts
Copy link
Contributor Author

@jerome3o-anthropic i think everything is ready to merge now. tnx!

@jerome3o-anthropic jerome3o-anthropic merged commit dee94ca into modelcontextprotocol:main Jan 30, 2025
2 checks passed
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