Max MCP Server
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Max MCP Serverget my workspace profile settings"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Max MCP Server (Digital Crew)
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.
What it does
The server registers tools that proxy to Digital Crew’s workspace profile API (/api/v1/workspace-profile-settings):
Tool | Purpose |
| Fetch workspace profile (company info) for the authenticated workspace |
| 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/.
Requirements
Node.js (see Next.js 15 requirements)
pnpm (see
packageManagerinpackage.json)
Configuration
Set these environment variables (e.g. in .env.local for local dev, or in your host’s env for production):
Variable | Required | Description |
| Yes | Base URL of the Digital Crew API (no trailing slash) |
| 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.
Getting started
pnpm install
# Create .env.local with DIGITALCREW_API_BASE_URL (and optional token vars)
pnpm devThe MCP endpoint is:
Local:
http://localhost:3000/mcpProduction:
https://<your-deployment>/mcp
Point your MCP client at that URL using Streamable HTTP transport.
Optional: smoke-test with the bundled script
scripts/test-streamable-http-client.mjs lists tools via Streamable HTTP. It expects the @modelcontextprotocol/sdk client package available in your environment (install it if the script is not runnable yet):
node scripts/test-streamable-http-client.mjs http://localhost:3000Note: SSE is currently disabled in
app/mcp/route.ts(disableSse: true). The olderscripts/test-client.mjs(SSE) is not aligned with the default setup unless you enable SSE and Redis per Vercel’s MCP pattern.
Stack
Next.js App Router
mcp-handler(Vercel MCP adapter)Zod for tool input schemas
Deploying on Vercel
Enable Fluid compute for efficient execution.
Adjust
maxDurationinapp/mcp/route.tsif your plan allows (e.g. up to 800s on Pro/Enterprise).SSE: If you switch
disableSsetofalse, attach Redis and setREDIS_URLas required by the adapter. See also the Next.js MCP template.
Learn more
Digital Crew — AI workforce platform
Max — Outreach control center — Max product site
Model Context Protocol — MCP specification
License
Private project ("private": true in package.json). Use and deployment are governed by your Digital Crew agreements.
This server cannot be installed
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Digital-Crew-Technologies/max-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server