# MCP ### Video Tutorial {% embed url="" %} ### Prerequisites Before continuing, make sure that the following steps have been completed on the machine you’ll be using to remotely connect to your MCP server: * NoPorts Desktop is installed. * Your NoPorts atSigns are activated, and the associated keys are saved locally. * You are signed in with your device atSign and have recorded your authentication passcode by opening the Authenticator tab and noting the displayed OTP. If these steps are not yet complete, please follow **Steps 1 through 5.3** in the [Quick Start guide for macOS or Windows](https://docs.noports.com/installation/quick-start-for-macos-and-windows) then return to this page. ### Step 1: Set up the MCP Server {% hint style="warning" %} Steps 1 through 4 are to be completed on the machine that your MCP server will be running on {% endhint %} In this example, the MCP server is implemented in **Python** using the **FastMCP** library. The reference code can be found at: In this example, the server will be running locally at: * **Host**: `127.0.0.1` * **Port**: `3000` You can choose whichever port number works best for you. {% hint style="info" %} The MCP Server must be served over a TCP Protocol to function with NoPorts. {% endhint %} ### Step 2: Set up the NoPorts Daemon Select the operating system running on the machine your MCP server is running on and follow the steps to install the NoPorts Daemon. {% tabs %} {% tab title="MacOS" %} Download the installer from GitHub by running the following command: ```bash curl -L https://github.com/atsign-foundation/noports/releases/latest/download/universal.sh -o universal.sh ``` To check if the installation downloaded correctly: ```bash stat universal.sh ``` Make the script executable and run the script by running the command below: ```bash chmod u+x universal.sh ./universal.sh ``` During installation, you’ll be prompted to enter the following items: You may be asked to enter your password if your machine requires sudo privileges. **The install type** * Enter `device` when prompted. **Your atSigns** * Client atSign: e.g., `@example01_np` * Device atSign: e.g., `@example02_np` **Your device name** * This should be the name of the machine you're currently installing on. {% endtab %} {% tab title="Linux" %} Download the installer from GitHub by running the following command: ```bash curl -L https://github.com/atsign-foundation/noports/releases/latest/download/universal.sh -o universal.sh ``` To check if the installation downloaded correctly: ```bash stat universal.sh ``` Make the script executable and run the script by running the command below: ```bash chmod u+x universal.sh ./universal.sh ``` During installation, you’ll be prompted to enter the following items: You may be asked to enter your password if your machine requires sudo privileges. **The install type** * Enter `device` when prompted. **Your atSigns** * Client atSign: e.g., `@example01_np` * Device atSign: e.g., `@example02_np` **Your device name** * This should be the name of the machine you're currently installing on. {% endtab %} {% tab title="Windows" %} Download the msi installer [from GitHub](https://github.com/atsign-foundation/noports/releases/latest/download/sshnp-windows-x64.zip). You can run the msi right from the windows-bundle.zip. Ensure both Core Tools & Daemon Service are being installed.
{% endtab %} {% endtabs %} ### Step 3: Configure Permit‑Open on Localhost:3000 1\. Edit the override configuration file: ```bash sudo vim /etc/systemd/system/sshnpd.service.d/override.conf ``` 2\. Under **“any additional command line arguments for sshnpd”**, add the following line: ```bash Environment=additional_args="--permit-open=\"localhost:3000,127.0.0.1:3000\"" ``` 3\. Apply the changes by restarting and reloading the service: ```bash sudo systemctl restart sshnpd.service sudo systemctl daemon-reload ``` ### Step 4: Initiate an authorization request Select the operating system running on the machine your MCP server is running on and follow the steps provided. {% tabs %} {% tab title="MacOS" %} Run the following command to make an authorization request: {% hint style="warning" %} Be sure to replace the following values: `@_np` with your **device atSign**, `` with the **passcode generated in step 5 of the prerequisite instructions** `@_np_key` with your **device atSign**, `` with the name of the machine you are on {% endhint %} 
~/.local/bin/at_activate enroll -a @<REPLACE>_np \
  -s <PASSCODE> \
  -p noports \
  -k ~/.atsign/keys/@<REPLACE>_np_key.atKeys \
  -d <DEVICE_NAME> \
  -n "sshnp:rw,sshrvd:rw"
Once you see this text, you're ready to continue to the next step. ``` Submitting enrollment request Enrollment ID: --------------------- Waiting for approval; will check every 10 seconds ``` {% endtab %} {% tab title="Linux" %} Run the following command to make an authorization request: {% hint style="warning" %} Be sure to replace the following values: `@_np` with your **device atSign**, `` with the **passcode generated in step 5 of the prerequisite instructions** `@_np_key` with your **device atSign**, `` with the name of the machine you are on {% endhint %} 
~/.local/bin/at_activate enroll -a @<REPLACE>_np \
  -s <PASSCODE> \
  -p noports \
  -k ~/.atsign/keys/@<REPLACE>_np_key.atKeys \
  -d <DEVICE_NAME> \
  -n "sshnp:rw,sshrvd:rw"
Once you see this text, you're ready to continue to the next step. ``` Submitting enrollment request Enrollment ID: --------------------- Waiting for approval; will check every 10 seconds ``` {% endtab %} {% tab title="Windows" %} Run the following command to make an authorization request. {% hint style="warning" %} Be sure to replace the following values: `@_np` with your **device atSign**, `` with the **passcode generated in Step 4**, `` with your **Windows username**, `@_np_key` with your **device atSign**, `` with the name of the machine you are on {% endhint %} 
at_activate.exe enroll -a "@<REPLACE>_np" `
  -s <PASSCODE> `
  -p noports `
  -k C:\Users\<USER>\.atsign\keys\@<REPLACE>_np_key.atKeys `
  -d <DEVICE_NAME> `
  -n "sshnp:rw,sshrvd:rw"
Once you see this text, you're ready to continue to the next step. ``` Submitting enrollment request Enrollment ID: --------------------- Waiting for approval; will check every 10 seconds ``` {% hint style="info" %} If you encounter a handshake exception, it usually means your root certificates are outdated. To refresh them, run the following command with administrator privileges:Install-Script -Name UpdateRootCertificates {% endhint %} {% endtab %} {% endtabs %} ### Step 5: Approve the request {% hint style="warning" %} Steps 5 through 7 are to be coompleted on the machine you'll be using to remotely connnect to your MCP server. {% endhint %} 1\. Click on Requests and approve the pending request. The request will then move to the approved enrollments list. 2\. After a few seconds, the request will also show as approved on the machine you are connecting to. ### Step 6: Create the profile in the desktop app Click on Connection and create a profile for your MCP connection. You will enter the following information 1. Profile Name - The name that will be displayed in the profile list. 2. Device atSign - Your device atSign (eg mcp\_demo\_02\_np). 3. Device Name - The name of your remote device. 4. Relay - Select the relay sever closest to you for optimum speed. 5. Local Port - The port you will use on your local machine. 6. Local Host - The hostname or IP address to bind to on your local machine. 7. Remote Host - The hostname or IP address of the machine you are connecting to. 8. Remote Port - The port that will be used on the remote machine. {% hint style="info" %} In this example, the we use details shown in the video. When following along, be sure to replace these with **your own data**. {% endhint %} | | | | ----------------- | ------------------ | | **Profile Name** | mcp\_demo | | **Device atSign** | @mcp\_demo\_02\_np | | **Device Name** | mcp\_demo | | **Relay** | @rv\_am | | **Local Port** | 3000 | | **Local Host** | | | **Remote Host** | 127.0.0.1 | | **Remote Port** | 3000 | ### Step 7: Interact with the MCP Server via Witsy **Whitsy** is an open‑source LLM client. Download and install it from [https://witsyai.com](https://witsyai.com/). 1\. Open Whitsy, select **MCP**, then click the **+** icon to add a new MCP server. 2\. Set **Type** to *streamable HTTP*, choose any **Label** you like, and enter the following URL: ```bash http://127.0.0.1:3000/mcp ``` Click **Save** and you should see a green checkmark. 3\. Go to **Chat**, then open **Customize** and enable the **process\_data** option. 4\. To test, type the following: ```bash process data using MCP "hello" ``` --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.noports.com/use-cases/mcp.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.