Rijksmuseum MCP Client for Rijksmuseum MCP Server

by r-huijts

MCP Client 4 stars
  • desktop-chat

An Electron-based desktop application that integrates with the Rijksmuseum MCP server using the Model Context Protocol (MCP). This client enables AI-powered interactions with the Rijksmuseum's art collection through a chat interface.

About

What is Rijksmuseum MCP Client for Rijksmuseum MCP Server?

An Electron-based desktop application that integrates with the Rijksmuseum MCP server using the Model Context Protocol (MCP). It enables AI-powered interactions with the Rijksmuseum's art collection through a chat interface.

How to use Rijksmuseum MCP Client for Rijksmuseum MCP Server?

Clone and set up the required Rijksmuseum MCP Server, then clone this client, install dependencies, create a .env file with your Rijksmuseum API key and server path, and run npm run dev for development or npm run build to build. Use the chat interface to query the collection.

Key features of Rijksmuseum MCP Client for Rijksmuseum MCP Server

- Search and explore Rijksmuseum's art collection
- Chat interface with AI-powered responses
- Image display support for artworks
- Real-time API integration via MCP
- Built with Electron and TypeScript

Use cases of Rijksmuseum MCP Client for Rijksmuseum MCP Server

- Discover artworks by querying the collection through natural language
- View high‑resolution images of museum pieces
- Integrate AI‑driven research into art history or curation

FAQ from Rijksmuseum MCP Client for Rijksmuseum MCP Server

What does this client do that a regular web browser doesn’t?

It provides an AI‑powered chat interface that queries the Rijksmuseum MCP server, returning contextual, conversation‑based results instead of requiring manual API calls or browsing.

What are the system requirements?

Node.js v18 or higher, npm or yarn, Git, and the separate Rijksmuseum MCP Server.

How do I get a Rijksmuseum API key?

The README does not specify the process, but a valid RIJKSMUSEUM_API_KEY must be placed in the .env file.

Is the client free?

Yes, it is open‑source under the MIT License.

What are the known limitations?

The README does not document any; the client depends on the Rijksmuseum MCP Server and the Rijksmuseum API for functionality.

Details

Author
r-huijts
GitHub stars
4
Category
desktop-chat
Repository
r-huijts/rijksmuseum-mcp-client

Rijksmuseum MCP Client for Rijksmuseum MCP Server

An Electron-based desktop application that integrates with the Rijksmuseum MCP server using the Model Context Protocol (MCP). This client enables AI-powered interactions with the Rijksmuseum's art collection through a chat interface.

Features

- 🎨 Search and explore Rijksmuseum's art collection
- 💬 Chat interface with AI-powered responses
- 🖼️ Image display support for artworks
- 🔄 Real-time API integration
- 🛠️ Built with Electron and TypeScript
- 🤖 Model Context Protocol (MCP) integration

Prerequisites

- Node.js v18 or higher
- npm or yarn
- Git
- Rijksmuseum MCP Server - Required for API integration

Dependencies

This client is designed to work with the Rijksmuseum MCP Server. You'll need to:

1. Clone and set up the Rijksmuseum MCP Server:

git clone https://github.com/r-huijts/rijksmuseum-mcp.git
cd rijksmuseum-mcp
npm install
npm run build

2. Configure the server path in your .env file (see Environment Variables section)

Installation

1. Clone the repository:

git clone [repository-url]
cd electron-mcp-client

2. Install dependencies:

npm install

3. Create a .env file in the root directory with your API keys:

RIJKSMUSEUM_API_KEY=your-rijksmuseum-api-key
MCP_SERVER_PATH=/path/to/rijksmuseum-mcp/build/index.js

Development

Start the development server:

npm run dev

Build the application:

npm run build

Project Structure

electron-mcp-client/
├── src/               # Source code
│   ├── main.ts       # Main process code
│   └── index.html    # Renderer process entry
├── dist/             # Build output
├── .env.example      # Environment variables example
└── package.json      # Project configuration

Environment Variables

- RIJKSMUSEUM_API_KEY: Your Rijksmuseum API key
- MCP_SERVER_PATH: Path to the Rijksmuseum MCP server executable

Contributing

1. Fork the repository
2. Create your feature branch (git checkout -b feature/amazing-feature)
3. Commit your changes (git commit -m 'Add some amazing feature')
4. Push to the branch (git push origin feature/amazing-feature)
5. Open a Pull Request

License

This project is licensed under the MIT License - see the LICENSE file for details.

Acknowledgments

- Rijksmuseum API
- Model Context Protocol
- Electron
- Rijksmuseum MCP Server