Skip to content
CribScore
Skip to content
CribScore Docs

MCP

Local MCP (npm)

Run the CribScore MCP server locally with `npx` for zero install, or pin via `npm install` for repeatable deploys.

Fast start#

One command, no install state. The package on npm is `@cribscore/mcp`. `npx -y` pulls the latest published version and runs it over stdio.

npx -y @cribscore/mcp

Pinned install#

When you ship to production, pin the version. Install once, run with explicit env, and lock the version with your package manager's lockfile.

  • Package: @cribscore/mcp
  • npm: https://www.npmjs.com/package/@cribscore/mcp
  • Source: https://github.com/musa8026/CribScore/tree/main/apps/mcp
Shellbash
# install once
npm install @cribscore/mcp

# run with explicit env
export MCP_API_KEY="YOUR_API_KEY"
export MCP_API_BASE_URL="https://api.cribscore.co"
npx cribscore-mcp

Runtime inputs#

Authentication and transport defaults are env-driven. Only `MCP_API_KEY` is required; the others have sane production defaults.

  • `MCP_API_KEY` — bearer token (required).
  • `MCP_API_BASE_URL` — defaults to `https://api.cribscore.co`. Override for local API testing only.
  • `MCP_TIMEOUT_MS` — per-tool timeout. Defaults to 30000.

Verify the install#

Call the `cribscore_search_facilities` tool from your agent client. A successful response confirms transport, auth, and tool routing all work end-to-end.

Related#