Cursor Latent Mile: Local 35mm colour developing and scans request_status
How to: Cursor Latent Mile: Local 35mm colour developing and scans request_status
Add Latent Mile: Local 35mm colour developing and scans to Cursor
-
01
Open ~/.cursor/mcp.json and merge this in. Keep any servers already there.
{
"mcpServers": {
"latentmile": {
"url": "https://latentmile.forevenza.com/mcp"
}
}
}-
02
Save the file and restart Cursor.
-
03
Ask for something request_status does. Cursor lists the server's tools on connect and calls request_status itself — you do not invoke it by name.
-
04
If nothing happens, check the server is running and that Latent Mile: Local 35mm colour developing and scans's identifier in your config matches the one above exactly.
Use .cursor/mcp.json in a project root instead to scope it to that project. Cursor merges both. Cursor docs
Same tool, other clients
This list was read from the server itself, by connecting to it and calling tools/list on 14 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.