mcp

This MCP server exposes two core action sets for InterviewReady. The GET ACTIONS allow clients to fetch the most relevant InterviewReady content, including blogs, resources, and course materials, enabling streamlined access to study material and references. The UPDATE ACTIONS enable users to augment their personal workspace by adding notes to a notepad and by scheduling Google reminders for future classes or deadlines. In practice, you can use this MCP server from any MCP-compatible client (such as Claude Desktop or Cursor) to retrieve curated materials and to manage reminders and notes from a single interface. The server is designed to be extensible, so you can tailor what content is returned and what updates are accepted by adjusting your client requests.

To interact with the server, send the appropriate GET requests to fetch content or POST/PUT-like requests to update notes or create reminders, depending on the client implementation. Reminder tools include create-reminder and get-reminders, which you can use to set and fetch reminders for upcoming classes or deadlines. These tools are available for use from any MCP-compatible client integrated with the InterviewReady MCP server.

Prerequisites:

• Node.js (recommended LTS) and npm or pnpm
• Basic familiarity with running terminal commands

Steps:

1. Clone the repository git clone <repository-url> && cd <repository-folder>

2. Install dependencies (pnpm is recommended as per the project setup) pnpm install

3. Build the server pnpm run build

4. Run the server locally (example) node mcp-server/build/index.js

5. Verify the server is running (the MCP should be reachable at the configured port/endpoint as per your environment)

Notes:

• If you prefer using npm, you can typically run equivalent npm install and npm run build commands, depending on the repository scripts.

Tips and notes:

• The server is intended to be run via a path-relative build/index.js as shown in the project setup with Claude Desktop or Cursor. Ensure {path-to-repo} is replaced with your actual repository path when configuring clients.
• Environment variables can be supplied per deployment if the MCP needs API keys or special configuration. Use the env block in mcp_config to document placeholders, e.g., "env": { "GOOGLE_API_KEY": "<your-key>" }.
• The server currently exposes content retrieval (GET actions) and user data updates (UPDATE actions) including a notepad and reminders. If you expand capabilities, consider documenting new actions clearly for clients.
• When integrating with Claude Desktop or Cursor, use the provided JSON config blocks to point the desktop client at the built index.js file. Ensure you replace {path-to-repo} with the actual path.
• If you encounter issues, check the build artifacts under mcp-server/build and confirm the index.js path used by your client configuration matches the output of the build process.