CompShop MCP Server

Search 350+ compensation surveys by industry, region, or job title. Independent directory.

Local serverstdioTypeScript

What is the CompShop MCP server?

Search 350+ compensation surveys by industry, region, or job title. Independent directory. Exposed over MCP by the compshop mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

The independent directory of salary & compensation surveys. Search 350+ reports across 17+ vendors (Mercer, WTW, Aon, SullivanCotter, Gallagher, Pearl Meyer, Empsight, Culpepper, Milliman, MRA, LOMA, Birches Group, Western Management Group, and more) by job title, industry, geography, or publisher.

Its toolset

Everything the assistant can do here goes through one of these:

  • Framework — ** Next.js 14 (App Router) + TypeScript + Tailwind
  • Database — ** SQLite (better-sqlite3) with a file-backed DB bundled in the repo
  • Search — ** server-side FTS-ish query across vendors, reports, job families, positions, and participating orgs
  • SEO — ** ~3,500 statically-generated indexable pages (vendor / report / family / position) with JSON-LD, OG/Twitter tags, canonical URLs, and an

Configuration

You will need one environment variable: NEXT_PUBLIC_SITE_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Adding it to your client

Installation goes through your MCP client rather than a global install: point it at npm on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

When to reach for it

Among the database access options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. CompShop's toolset — Framework, Database, Search and 1 more — is a fair guide to whether it matches your workflow. It is maintained by mkibrick; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against CompShop's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Caveats

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the compshop mcp server does with a few real requests.

Available tools

ToolWhat it does
Framework** Next.js 14 (App Router) + TypeScript + Tailwind
Database** SQLite (better-sqlite3) with a file-backed DB bundled in the repo
Search** server-side FTS-ish query across vendors, reports, job families, positions, and participating orgs
SEO** ~3,500 statically-generated indexable pages (vendor / report / family / position) with JSON-LD, OG/Twitter tags, canonical URLs, and an auto-generated sitemap

How to install the CompShop MCP server

{
  "mcpServers": {
    "compshop": {
      "command": "npx",
      "args": ["-y", "npm"],
      "env": {
        "NEXT_PUBLIC_SITE_URL": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
NEXT_PUBLIC_SITE_URLEndpoint or connection string the server talks to.Yes

Example prompts to try

  • Use CompShop to Framework.
  • Use CompShop to Database.
  • Use CompShop to Search.

Frequently asked questions

It connects CompShop to MCP-compatible AI assistants such as Claude and Cursor, exposing 4 tools (Framework, Database, Search, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with CompShop directly.