Track MCP LogoTrack MCP
Track MCP LogoTrack MCP

The world's largest repository of Model Context Protocol servers. Discover, explore, and submit MCP tools.

Product

  • Categories
  • Top MCP
  • New & Updated

Company

  • About

Legal

  • Privacy Policy
  • Terms of Service
  • Cookie Policy

© 2025 TrackMCP. All rights reserved.

Built with ❤️ by Krishna Goyal

    Cooper Hewitt Mcp

    MCP for interacting with the Cooper Hewitt Collection API

    2 stars
    TypeScript
    Updated Oct 3, 2025

    Documentation

    Cooper Hewitt Model Context Protocol (MCP) Server

    Description

    A Model Context Protocol (MCP) server for interacting with the Cooper Hewitt Museum's collection API. This tool allows searching and retrieving detailed information about museum objects programmatically.

    Prerequisites

    • Node.js (version 16+ recommended)
    • npm (Node Package Manager)

    Installation

    1. Clone the repository:

    bash
    git clone https://github.com/behole/cooper-hewitt-mcp.git
    cd cooper-hewitt-mcp

    2. Install dependencies:

    bash
    npm install

    3. Set up API Token

    • Create a .env file in the project root
    • Obtain an API token from the Cooper Hewitt API
    • Add your token to the .env file:
    code
    COOPER_HEWITT_API_TOKEN=your_api_token_here

    4. Update your claude_desktop_config.json

    bash
    "cooper-hewitt": {
          "command": "node",
          "args": ["path to your index.js"]
        }

    Available Tools

    Search Objects

    • Name: search-objects
    • Description: Search for objects in the Cooper Hewitt collection
    • Parameters:
    • query (string, required): Search terms
    • page (number, optional): Page number of results
    • perPage (number, optional): Number of results per page

    Get Object Details

    • Name: get-object
    • Description: Retrieve detailed information about a specific museum object
    • Parameters:
    • id (string, required): Unique identifier of the museum object

    Running the Server

    bash
    node index.js

    Development

    • Ensure all dependencies are installed
    • Run tests (if applicable)
    • Check code formatting

    Contributing

    1. Fork the repository

    2. Create your feature branch (git checkout -b feature/AmazingFeature)

    3. Commit your changes (git commit -m 'Add some AmazingFeature')

    4. Push to the branch (git push origin feature/AmazingFeature)

    5. Open a Pull Request

    To-Do's (Very Much a WIP) ->

    • Fix image handingling in the artifacts on Claude Desktop

    License

    Specify your license - e.g., MIT, Apache 2.0

    Contact

    []

    Acknowledgments

    • Cooper Hewitt, Smithsonian Design Museum
    • Model Context Protocol SDK

    Similar MCP

    Based on tags & features

    • GL

      Glm Mcp Server

      TypeScript·
      3
    • NS

      Ns Private Access Mcp

      TypeScript·
      3
    • MC

      Mcp Wave

      TypeScript00
    • OP

      Openai Gpt Image Mcp

      TypeScript·
      75

    Trending MCP

    Most active this week

    • PL

      Playwright Mcp

      TypeScript·
      22.1k
    • SE

      Serena

      Python·
      14.5k
    • MC

      Mcp Playwright

      TypeScript·
      4.9k
    • MC

      Mcp Server Cloudflare

      TypeScript·
      3.0k
    View All MCP Servers

    Similar MCP

    Based on tags & features

    • GL

      Glm Mcp Server

      TypeScript·
      3
    • NS

      Ns Private Access Mcp

      TypeScript·
      3
    • MC

      Mcp Wave

      TypeScript00
    • OP

      Openai Gpt Image Mcp

      TypeScript·
      75

    Trending MCP

    Most active this week

    • PL

      Playwright Mcp

      TypeScript·
      22.1k
    • SE

      Serena

      Python·
      14.5k
    • MC

      Mcp Playwright

      TypeScript·
      4.9k
    • MC

      Mcp Server Cloudflare

      TypeScript·
      3.0k