Curb Cut MCP

What curb-cut-mcp does

The curb-cut-mcp MCP server gives an assistant access to Curb Cut’s workplace accommodation workflow. It supports research and drafting rather than transmission: an assistant can look up accommodation options, consult cost evidence, and prepare a response for review. The server exposes five tools, and none can send a message or submit a request.

Curb Cut is designed around a worker asking for support without naming a diagnosis. Its underlying workflow can accept requests through web, text, voice, email, Slack direct messages, or an assistant. The MCP interface is one of those assistant-facing entry points; the README identifies the MCP process as node channels/mcp-server.mjs.

This belongs in the Workplace & Productivity category for workflows that help workers and access teams handle accommodation questions. It is intended for information gathering and controlled drafting, not autonomous communication.

How it works

The MCP process runs alongside a Curb Cut deployment and uses the deployment’s Salesforce-backed workflow. Curb Cut describes a single Apex REST message endpoint shared by its channels, while the MCP server is listed separately as a five-tool interface. The available material does not provide individual tool names or schemas, so integrations should inspect the server configuration or source before calling specific tools.

The design keeps the worker in control of disclosure. Curb Cut states that nothing leaves unless the person personally approves it. The workflow also has no diagnosis field, does not infer personal information, and does not accept a telephone number as a reachability value.

Setup and configuration

Clone the repository and change into its directory before running the project’s checks or starting the MCP process. The server command shown in the deployment table is:

node channels/mcp-server.mjs

For a complete Salesforce installation, follow DEPLOY.md. The deployment requires Agentforce. Text and voice channels additionally require an organisation-owned Twilio number and the relay under channels/; Slack requires an app created from the supplied workspace manifest. Four Salesforce Custom Labels hold deployment-specific values such as the number, site URL, and support address.

The repository also includes offline structural checks through tests/invariants.py. Those checks validate project structure but are not a substitute for configuring a Salesforce org.

Tools and capabilities

The curb-cut-mcp MCP server provides five tools focused on:

• Looking up workplace accommodation options.
• Retrieving evidence about accommodation costs.
• Drafting accommodation-related responses.
• Supporting an assistant-mediated Curb Cut conversation.
• Keeping the workflow non-sending and reviewable.

The source material does not document separate tool names, argument formats, return schemas, authentication settings, or versioned API contracts. Developers should verify those details in the repository before building a client integration.

Limitations and notes

This server looks up information and drafts content; it does not send. A human or worker must remain responsible for approval and communication. The broader Curb Cut system intentionally excludes diagnosis storage, inference, automated sign-language recognition, and telephone fallback. Signed video is routed to a human with a text acknowledgement rather than machine-translated.

The README records a demo Salesforce deployment, but its addresses and phone number are specific to that deployment and are not the settings for a new installation. The MCP listing also does not document client-specific setup instructions or environment variable names.