Get the FREE Ultimate OpenClaw Setup Guide →

usekeen

MCP server that streams up-to-date package docs to AI coding assistants like Claude, Cursor & Windsurf.

Installation
Run this command in your terminal to add the MCP server to Claude Code.
Run in terminal:
Command
claude mcp add --transport stdio use-keen-usekeen-mcp-server npx -y usekeen-mcp \
  --env USEKEEN_API_KEY="your_api_key_here"

How to use

This MCP server exposes the UseKeen integration for the UseKeen API, enabling Claude and other AI assistants to search documentation via the usekeen_package_doc_search tool. The server authenticates with your UseKeen API key and provides a focused capability to retrieve package and service documentation, including implementation details, examples, and specifications. The tool accepts a required package_name and an optional query to narrow results, returning documentation blocks with summaries and URLs that you can present to the user. Use the npx deployment option to run the server locally or in your environment, and supply your API key to authorize requests.

How to install

Prerequisites:

  • Node.js installed on your machine (for NPX usage) or access to a Docker-enabled environment
  • A UseKeen API key
  • Optional: Claude Desktop or VS Code with MCP extension for best experience

Option 1: NPX (Recommended)

  1. Ensure Node.js is installed.
  2. Run the MCP server with NPX: npx usekeen-mcp

Option 2: Docker

  1. Ensure Docker is installed and running.
  2. Run the container with your API key: docker run -e USEKEEN_API_KEY=your_api_key_here mcp/usekeen

Option 3: Local Development (Manual installation)

  1. Clone the repository and navigate to the project folder.
  2. Copy the environment file and add your API key: cp .env.example .env

    edit .env to set USEKEEN_API_KEY

  3. Install dependencies: npm install
  4. Build and run: npm run build USEKEEN_API_KEY=your_api_key npm start

Additional notes

Environment variables: Ensure USEKEEN_API_KEY is set in your environment when running the server. If using Docker, pass the key via -e USEKEEN_API_KEY. The server normalizes MCP results to include a content array for compatibility. If you see MCP result shape errors, verify the tool returns content blocks in the format { content: [{ type: 'text', text: '...' }] }. Common issues include invalid API keys, network connectivity, or downtime on the UseKeen service. The NPX approach is convenient for quick experiments, while Docker provides a portable, isolated runtime.

Related MCP Servers

Sponsor this space

Reach thousands of developers