Hypernym MCP Server exposes semantic analysis and compression tools via MCP. It implements two core tools: analyze_text, which performs full semantic analysis including categorization and compression metrics, and semantic_compression, which returns a compressed version of the input text while preserving meaning. You can interact with these tools either through the MCP stdio transport for integration with MCP-enabled agents, or via the HTTP/HTTPS JSON-RPC 2.0 endpoints when the server is running in HTTP mode. To use through MCP, configure your .mcp.json to point at the server in stdio mode and start the server using npm run start:stdio. Each tool accepts text input and optional parameters like min_compression_ratio and min_semantic_similarity to control compression strength and semantic retention. The server also supports HTTP endpoints for direct API passthrough to Hypernym.

Prerequisites:

• Node.js (LTS version) and npm installed
• Git installed
• Access to Hypernym API with URL and API key

Installation steps:

1. Clone the repository git clone https://github.com/hypernym/hypernym-mcp-server.git cd hypernym-mcp-server

2. Install dependencies npm install

3. Create a .env file (or use the provided env vars in mcp_config) touch .env

4. Configure environment variables HYPERNYM_API_URL=https://fc-api-development.hypernym.ai HYPERNYM_API_KEY=your_api_key_here PORT=3000

   Optional for HTTPS

   SSL_KEY_PATH=/path/to/your/server.key SSL_CERT_PATH=/path/to/your/server.crt

5. Build (if applicable) and run npm run build # if a build step is defined npm start # to run in HTTP/HTTPS mode npm run start:stdio # to run in stdio transport mode for MCP

6. (Optional) Generate self-signed certs for development npm run generate-certs

Environment variables and config:

• HYPERNYM_API_URL and HYPERNYM_API_KEY are required for API access.
• PORT sets the listening port for HTTP/HTTPS mode; default is 3000 if not specified.
• SSL_KEY_PATH and SSL_CERT_PATH enable HTTPS when provided.
• MCP_USE_STDIO can force stdio transport; ensure your MCP consumer uses stdio if you rely on that transport. If you encounter connectivity or API errors, verify that the Hypernym API URL is reachable from your deploy environment and that the API key has the necessary permissions. For MCP integrations, use the stdio transport configuration to ensure proper tool discovery and invocation.