Skip to content

AI and agents · By Rivtor · Updated

Local vs remote MCP for deploying private source code

A local MCP server can act within the machine and permissions where it runs; a remote MCP server operates on its host. Choose the source-transfer and authentication workflow explicitly. Agent access to an open project does not automatically give the remote server access to that folder.

See how Rivtor connects to your agent →

Identify the machine performing each action

The coding client, MCP server and deployment platform may run on three different machines. Write down which one reads source files, obtains credentials and initiates the upload. This removes a common ambiguity: an agent can inspect a file while the hosted tool it calls cannot.

In a local stdio workflow, the client launches a process with local permissions. A remote HTTP workflow exposes tools over the network. Either can perform privileged operations, so neither should be described as automatically safe or automatically insecure.

Match the source to the workflow

Source requirementCheck before deploying
Uncommitted local editsTool actually uploads the intended working directory
Private Git revisionPlatform has the required repository access
Public Git exampleRevision and source owner are correct
Existing project updateDestination project and permissions are explicit

For Rivtor, use the documented local/remote connection modes. A remote source URL and a local path are different inputs. Do not send an absolute laptop path to a remote server and assume it refers to the same files.

Keep credentials at the appropriate boundary

Store tokens in the supported private configuration rather than a committed project file. Review access scopes and avoid giving a broad account token to a tool that only needs a project-level operation. Do not copy secrets into prompts or screenshots merely to demonstrate setup.

A local uploader still sends selected source to the build platform. Inspect ignored files and secret handling. A private repository can still contain files that should never enter an image or build log.

Verify before allowing a mutation

Ask the agent to identify roots, missing variable names and the selected target first. Inspect the proposed tool input. After release, compare the intended source revision or local edit with the running application and verify a synthetic operation. An authenticated tool connection proves connectivity, not that the correct source or destination was selected.

Document these boundaries in onboarding instructions rather than promising that connecting MCP alone ships any open workspace.

References