remote

The Port Remote MCP Server acts as a bridge between Port.io and your preferred development environment, enabling secure, remote communication for IDEs, agents, and LLM-powered tools. It exposes the standard MCP endpoints that allow your client to establish a connection, exchange messages, and receive responses from the connected tools. With this server, you can offload heavy processing to your local or cloud environment while keeping a streamlined interface through Port.io.

To use it, start the server with the command provided by your package manager (the recommended option is via npx to avoid local installation): npx -y port-labs-remote-mcp-server. Once running, configure your Port.io integration to point at the server's address and port. The MCP server will handle secure messaging, routing, and any plugin or capability integrations defined in your Port.io setup. You can leverage capabilities such as intent routing, tool invocation, and responses from your IDE or agent platform through the Port MCP interface provided by this server.

Prerequisites:

• Node.js (14.x or newer) and npm installed on your machine
• Internet access to fetch packages

Option A: Run without installation (recommended for quick start)

• Ensure you have npm and Node.js installed
• Use npx to run the server without installation: npm i -g npm # ensure npm is up to date npx -y port-labs-remote-mcp-server

Option B: Install locally for repeated use

• Install the package globally: npm install -g port-labs-remote-mcp-server
• Run the server: npx port-labs-remote-mcp-server # or the exact binary if provided

Option C: Docker (if available in your environment)

• Follow the project’s Docker guidance to pull and run the image, then expose the required port for MCP communications.

Environment variables (optional, based on deployment):

• PORT: The port on which the MCP server will listen (default may be 8080 or 8000 depending on build).
• MCP_TOKEN: Optional authentication token for securing MCP connections.
• LOG_LEVEL: Set to debug/info/warn/error to control logging verbosity.

Tips and common considerations:

• If you use npx, the server will run without a persistent install. For long-running or production setups, consider installing the package locally or globally.
• Ensure network access between Port.io and the MCP server host; open firewall rules for the configured port.
• Secure your MCP communications using authentication tokens or TLS if supported by the Port MCP implementation.
• Check the Port MCP documentation linked in the repository README for environment-specific configuration options and capabilities (e.g., tool invocation, streaming responses, and plugin integrations).
• If you encounter issues starting the server, verify Node.js/npm versions, network access, and that the correct package name (port-labs-remote-mcp-server) is being used.