octocat-harry-potter

This MCP server exposes a collection of automatically generated API tools for the Octocat-Harry-Potter workflow. The server is designed to integrate with MCP-compatible clients (such as Claude Desktop, Postman, or other agents) and exposes a set of tools derived from the Postman API requests you selected during generation. You can run the server locally and connect your client to the mcpServer.js endpoint; the client will discover and invoke the available tools as API endpoints.

To use, start the server in your project directory and point your MCP client to the local server. Tools will appear with descriptive names and parameters based on the generated Postman collections. You can run the server with standard Node.js execution or, if you prefer, via Docker as shown in the documentation. Tools can be invoked to fetch data, execute API requests, or simulate interactions defined by the original Postman collections.

Prerequisites:

• Node.js v16+ (v20+ recommended)
• npm (comes with Node.js)

1. Clone or download this repository to your local environment.

2. Install dependencies

npm install

3. Configure environment (optional but recommended)

• Create a .env file in the project root.
• Add environment variables required by the generated tools (placeholders). Example (placeholders; replace with real keys as needed):

# Example workspace/api keys (adjust to your workspaces)
ACME_API_KEY=
WIDGETS_API_KEY=

4. Run the MCP server

node mcpServer.js

5. Optional: Run via Docker (production or isolation)

• Build the image (from Dockerfile included):

docker build -t octocat-harry-potter-mcp-server .

• Run with an env file:

docker run -i --rm --env-file .env octocat-harry-potter-mcp-server

Tips and common considerations:

• If you use Claude Desktop or other MCP clients, you may need to register the server under a descriptive key, e.g. octocat-harry-potter, in your client configuration.
• The environment file (.env) should contain keys required by the generated tools; the README mentions workspace-based keys. If you don’t use external services, you can leave keys empty, but ensure the tools won’t attempt to read undefined variables.
• Server-Side Events (SSE) support can be enabled by starting Node with the --sse flag. Example: node mcpServer.js --sse. When using Docker, you can map ports and expose SSE as needed.
• If migrating to production, consider the provided Dockerfile and ensure .env is properly populated before deployment.
• For debugging, use the guidance in the README to locate the mcpServer.js path and confirm Node is accessible via which node.