Integrations
Connect Pre-Trip to Claude, Cursor, or any MCP client, so a source-cited compliance check rides along while you draft. Same engine as the scanner and the API.
Pre-Trip ships a Model Context Protocol server: it gives an AI assistant two tools, scan_content (screen a piece of copy, get a pass or a cited fix list) and get_coverage (list valid states and verticals). Because MCP is model-controlled, the assistant runs the check while you write. For a hard pre-publish gate that must block on a fail, call the REST API instead. Both ride the same engine, and your draft is scanned, not kept.
A small local server you run beside your assistant, authenticated with your API key. Works with Claude Desktop, Cursor, and any MCP host. Set it up below.
A remote server you add by URL and sign in to, no install and no key to paste. In private beta while we finish the sign-in flow. Ask for access.
Grab the server and install its dependencies:
curl -L -o pretrip-mcp.zip https://kesey.agency/downloads/pretrip-mcp.zip
unzip pretrip-mcp.zip
cd pretrip-mcp
npm install
Note the absolute path to index.mjs; you will point your client at it next. (Publishing to npm for a one-line npx install is on the way.)
Claude Desktop. Open Settings, Developer, Edit Config, and add Pre-Trip to claude_desktop_config.json:
{
"mcpServers": {
"pretrip": {
"command": "node",
"args": ["/absolute/path/to/pretrip-mcp/index.mjs"],
"env": { "PRETRIP_API_KEY": "pt_live_your_key_here" }
}
}
}
Restart Claude Desktop, and the Pre-Trip tools appear.
Cursor. Add the same block to .cursor/mcp.json in your project, or the global Cursor MCP config. Any MCP host that speaks stdio works the same way: run node index.mjs with PRETRIP_API_KEY in the environment.
In the middle of drafting, just ask:
Check this ketamine clinic landing page for California
compliance before I publish it: [paste your copy]
The assistant calls scan_content and reads back the verdict and the cited fix list. If it is unsure which vertical or state to use, it calls get_coverage first.
The server sends the copy you ask it to check to the Pre-Trip API and stores nothing. Aggregate scan metadata is recorded against your API key for usage and billing, never the copy. See the Trust page for how we draw that line, and the Privacy Policy for the full account. Pre-Trip is a rigorous screen, not legal advice, and a pass is not a legal opinion. Counsel decides; we help you arrive prepared.