mcp -gravatar-remote

This MCP server exposes six tools to access Gravatar data via MCP endpoints: get_profile_by_id, get_profile_by_email, get_inferred_interests_by_id, get_inferred_interests_by_email, get_avatar_by_id, and get_avatar_by_email. Each tool returns structured JSON or image data representing a Gravatar profile, its AI-inferred interests, or avatar images with customizable options such as size, default fallbacks, and rating. You can interact with these tools by making MCP requests to the server’s endpoints using the corresponding tool names and required inputs. For example, to fetch a profile by email, provide the email address and receive a JSON profile object; to retrieve an avatar, specify an identifier (or email) and optional parameters like size and default option to tailor the image delivered.

Prerequisites:

• Node.js v22 or newer installed on the host
• Internet access to install dependencies

1. Clone the repository or install the package from npm (if published): git clone https://github.com/automattic/mcp-server-gravatar-remote.git cd mcp-server-gravatar-remote

2. Install dependencies: npm install

3. Configure environment variables (optional but recommended):

   • PORT: port to run the MCP server (default 8787)
   • MCP_BASE_PATH: base path for MCP endpoints (default /mcp)

4. Start the MCP server: npm start

5. Verify the server is running by querying http://localhost:8787/mcp or the port you configured.

Note: If you are wiring this through a proxy (mcp-remote), you can connect clients to the remote proxy as shown in the examples in the README.

Tips and notes:

• The server exposes six core tools for interacting with Gravatar data; ensure inputs match the required fields (profileIdentifier, email, avatarIdentifier) depending on the tool.
• For get_avatar_by_id/get_avatar_by_email you can customize size (1-2048), defaultOption (404, mp, identicon, etc.), forceDefault, and rating (G, PG, R, X).
• If no avatar exists and you choose 404 as the default option, the request will return an HTTP 404.
• When deploying behind proxies or in containers, remember to map the port you expose (commonly 8787) to a host port and adjust MCP_BASE_PATH if needed.
• If you plan to connect via the mcp-remote proxy, configure the client with the proper URL (e.g., http://localhost:8787/mcp) as shown in the Setup section of the README.