Deploy Apps from Cursor with Rivtor MCP
Add Rivtor as an MCP server in Cursor, authenticate using a supported method, then ask the agent to inspect and deploy your project. Choose local MCP when source files must be uploaded directly from disk.
Choose the right connection
Cursor can operate inside a project, but the hosted Rivtor MCP endpoint does not share that filesystem. A local stdio server bridges that boundary. Review the tool call, target project and detected services before allowing an operation, especially when working with an existing app.
Configure the MCP connection
Create a Rivtor token through your account’s token page. Replace the placeholder in this configuration with that token using your client’s supported secret workflow. Do not commit credentials to Git.
{
"mcpServers": {
"rivtor": {
"url": "https://api.rivtor.com/mcp",
"headers": {
"Authorization": "Bearer rvt_..."
}
}
}
}Configuration screens and client capabilities can change. Check the official Cursor MCP documentation and Rivtor’s connection reference for setup details.
Ask for a plan before deployment
Ask the agent to inspect the service roots, required environment names and data dependencies. Review the selected project and any missing secrets before approving a deploy. The first call can need input; do not tell the agent to invent credentials or disable checks to proceed.
Review this workspace for Rivtor deployment. Identify whether local upload is required, list the API and frontend directories, and explain missing configuration before changing anything.Cursor setup and troubleshooting checklist
- Add the documented server entry through Cursor's MCP configuration and confirm that Rivtor tools are enabled in the agent.
- The remote URL configuration can deploy supported Git sources; it does not upload the open workspace automatically. Use local MCP or the CLI for an uncommitted folder.
- If a tool is unavailable, inspect the server's enabled state and authentication. If a deployment needs a secret, supply it through the supported secret workflow instead of putting it in source.
Keep deployment credentials in your private client configuration. Reconnect after replacing an expired token; never paste a credential into a public support question.
Read the deployment result
A deployment status and an application verification verdict answer different questions. Inspect the live URLs, verification issues and skipped checks. Read structured cause and fix fields when a release fails, then repair the relevant service and retry deliberately.
Frequently asked questions
Does connecting MCP deploy my app?
No. Connecting makes tools available. A deploy is a separate operation against a selected project.
Can the remote server read local files?
No. Use the local MCP server or CLI for uploading folders. Remote deployment uses supported Git sources, starters or inline files.
Where do the app and database run?
Rivtor’s container apps and data services run in India. Static assets can be served through Cloudflare’s edge. Check the current limits and evaluate dynamic latency for your users.