UseKeen

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

2

GitHub Stars

javascript

Language

6 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs
{
  "mcpServers": {
    "use-keen-usekeen-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "usekeen-mcp"
      ],
      "env": {
        "USEKEEN_API_KEY": "your_api_key_here"
      }
    }
  }
}

This MCP Server lets the UseKeen API power Claude and other AI assistants with fast, searchable access to package and service documentation. It exposes a simple runtime you can run locally or in Docker, and it integrates with clients like Claude Desktop or VS Code to provide quick, structured tool results for your queries.

How to use

You run the UseKeen MCP Server as a local process that your MCP-enabled client can talk to. You can start it either directly with NPX, via Docker, or run it locally after cloning and building. Once running, your client can issue search queries to the server to fetch documentation snippets, examples, and specifications to help you implement or understand packages and services.

How to install

Prerequisites include having a UseKeen API key and a runtime environment you can execute MCP servers in.

Option 1: NPX (Recommended) install and run in one step.

npx usekeen-mcp

How to install

Option 2: Docker install. Run the server in a container with your API key.

docker run -e USEKEEN_API_KEY=your_api_key_here mcp/usekeen

How to install

Option 3: Local development and manual installation. Clone the project, install dependencies, build, and start.

# Clone the repository
git clone <repository-url>
cd usekeen-mcp

# Copy environment file and add your API key
cp .env.example .env
# Edit .env and add your USEKEEN_API_KEY

# Install dependencies
npm install

# Build and run
npm run build
npm start

Configuration and runtime

Choose how you want to run the server and provide your API key. The two common runtime options are NPX and Docker.

Configuration with Claude Desktop

Add a server entry to your Claude Desktop config to connect to the UseKeen MCP Server. The following blocks show two common runtimes.

Configuration with Claude Desktop NPX

{
  "mcpServers": {
    "usekeen": {
      "command": "npx",
      "args": [
        "-y",
        "usekeen-mcp"
      ],
      "env": {
        "USEKEEN_API_KEY": "your_api_key_here"
      }
    }
  }
}

Configuration with Claude Desktop Docker

{
  "mcpServers": {
    "usekeen": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "USEKEEN_API_KEY",
        "mcp/usekeen"
      ],
      "env": {
        "USEKEEN_API_KEY": "your_api_key_here"
      }
    }
  }
}

Configuration with VS Code

In VS Code, add a mcp.json (or a workspace-specific .vscode/mcp.json) to define the server. Use the NPX or Docker configuration blocks as a starting point.

Environment variables

The server requires your UseKeen API key to authenticate requests. Provide this value in the environment variable USEKEEN_API_KEY for your chosen runtime.

Troubleshooting

If you run into issues, verify that your UseKeen API key is valid and correctly set, ensure you have an active internet connection, and confirm the UseKeen service is reachable.

Build

There is no separate build step required for NPX usage. If you clone locally, install dependencies, then build and start, follow the commands shown above.

Available tools

usekeen_package_doc_search

Search documentation of packages and services to find implementation details, examples, and specifications

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational