max-mcp-server

MCP server for Max, the AI sales agent from Digital Crew. Max is built for lead qualification, cold outreach, and pipeline growth—see the product story on max.digitalcrew.tech.

This repo hosts a Next.js app that exposes MCP tools over Streamable HTTP so Max (or any MCP-capable client) can read and update workspace profile settings against the Digital Crew backend API.

The server registers tools that proxy to Digital Crew’s workspace profile API (/api/v1/workspace-profile-settings):

| Tool | Purpose | |------|--------| | get_workspace_profile | Fetch workspace profile (company info) for the authenticated workspace | | update_workspace_profile | Create or update workspace profile (PUT upsert) |

Tool definitions and validation use Zod (features/workspace-profile/mcp/schema.ts). Registration lives under features/workspace-profile/mcp/.

• Node.js (see Next.js 15 requirements)
• pnpm (see packageManager in package.json)

Set these environment variables (e.g. in .env.local for local dev, or in your host’s env for production):

| Variable | Required | Description | |----------|----------|-------------| | DIGITALCREW_API_BASE_URL | Yes | Base URL of the Digital Crew API (no trailing slash) | | DIGITALCREW_API_TOKEN or DIGITALCREW_BEARER_TOKEN | Optional* | Default Bearer token for API calls |

\*If you omit these, callers must supply auth per request: `Authorization: Bearer <token>` on the MCP HTTP request, or the optional bearer_token argument on a tool call. Precedence is: tool bearer_token → MCP Authorization → env.

pnpm install
# Create .env.local with DIGITALCREW_API_BASE_URL (and optional token vars)

pnpm dev

The MCP endpoint is:

• Local: http://localhost:3000/mcp
• Production: `https