Dreamwork MCP server

Dreamwork's public MCP source lives here. The client calls the hosted Dreamwork API; it does not include the API, database, workers, or hosted OAuth service.

Connect over HTTP at https://mcp.dreamworkhq.com/mcp, or run the stdio client with npx -y @dreamworkhq/mcp. Public job browsing works without a key.

For source development, use Node 22 and pnpm 10.23.0:

pnpm install --frozen-lockfile
pnpm check
pnpm test
pnpm build
pnpm test:package

The MCP client is in apps/mcp. packages/api-contracts and packages/assistant-contracts contain its source dependencies; they are bundled into the published CLI. source-export.json records the release's source commit. See CONTRIBUTING.md for how changes reach a release.

@dreamworkhq/mcp

MCP server for Dreamwork — job-search tools for AI agents. Gives any MCP client (Claude Desktop, Cursor, the MCP Inspector, etc.) what it needs to find roles, rank them, tailor applications, apply, and track outcomes for one person over time.

This server is a thin gateway: it calls the Dreamwork API over HTTPS and holds no database access of its own. Transport is stdio — stdout carries only JSON-RPC frames.

Install

No install step is required — MCP clients run it on demand with npx. The examples below use npx -y @dreamworkhq/mcp.

Configure

Claude Desktop

Add an entry to your claudedesktopconfig.json (~/Library/Application Support/Claude/claudedesktopconfig.json on macOS):

{
  "mcpServers": {
    "dreamwork": {
      "command": "npx",
      "args": ["-y", "@dreamworkhq/mcp"],
      "env": {
        "DREAMWORK_API_KEY": "sk_..."
      }
    }
  }
}

Restart Claude Desktop after editing. Put credentials in the env block — don't wrap command in a shell or an env-loader (dotenvx run -- …, etc.): on a stdio server any banner such a wrapper prints to stdout will corrupt the JSON-RPC stream and hang tool calls.

Cursor and other clients

Any stdio MCP client works. Cursor uses the same config shown above — point the command at npx -y @dreamworkhq/mcp and pass DREAMWORKAPIKEY in the environment. To sanity-check with the Inspector:

DREAMWORK_API_KEY=sk_... npx @modelcontextprotocol/inspector npx -y @dreamworkhq/mcp

Hosted endpoint

Dreamwork also serves these tools over Streamable HTTP at https://mcp.dreamworkhq.com/mcp. In claude.ai, Claude Desktop, or ChatGPT, add that URL as a custom connector and sign in to Dreamwork. There is nothing to install and no key to paste. The consent screen asks which scopes the connector gets.

Clients that set request headers can send an agent key to the same URL instead. In Claude Code:

claude mcp add --transport http dreamwork https://mcp.dreamworkhq.com/mcp \
  --header "Authorization: Bearer sk_..."

Authentication

Generate an agent key from your Dreamwork profile: sign in at dreamworkhq.com, open your profile → Agent key section (or use the Get your agent key button on the Agents page), then set it as DREAMWORKAPIKEY (format sk_...).

When you generate a key you choose what it may do: read, write, apply, send mail. New keys get read and write, so a key made without a decision cannot submit an application or mail a recruiter. Pick the narrowest set that lets your agent work.

Guest mode: with no key set, the server still starts and exposes the public, read-only tools (browselistings, getlisting, getplatformcontext, getupgradelink). Account tools return a short "No agent key" message until a key is set.

Environment variables

Shortened. The full README is on GitHub.