Share files from an AI agent

1. Sign in at nudgehost.com and open your dashboard. A free account works.
2. Scroll to API keys. Under Create a key, type a name for the agent, such as "Claude Code", and click Create key.
3. Copy the key from the "Copy your new key now" box. It starts with nh_sk_ and is shown only once.
4. Click I have saved it.

Keep the key in an environment variable named NUDGEHOST_API_KEY rather than in a config file. On macOS or Linux, add this line to your shell profile and open a new terminal.

export NUDGEHOST_API_KEY="nh_sk_your_key_here"

A key can do anything your account can, with no narrower scopes. Give each agent its own key, so you can revoke one from the same list without touching the others.

Save this as .mcp.json in the folder you start Claude Code from. Claude Code fills in ${NUDGEHOST_API_KEY} from your environment. The Claude app needs no key or file, because you add NudgeHost to Claude with a custom connector and sign in instead.

{
  "mcpServers": {
    "nudgehost": {
      "type": "http",
      "url": "https://www.nudgehost.com/api/mcp",
      "headers": {
        "Authorization": "Bearer ${NUDGEHOST_API_KEY}"
      }
    }
  }
}

Start Claude Code in that folder and approve the nudgehost server when it asks. Run /mcp and check that nudgehost shows four tools.

Add this to ~/.cursor/mcp.json to use NudgeHost in every project. Cursor fills in ${env:NUDGEHOST_API_KEY} from your environment.

{
  "mcpServers": {
    "nudgehost": {
      "url": "https://www.nudgehost.com/api/mcp",
      "headers": {
        "Authorization": "Bearer ${env:NUDGEHOST_API_KEY}"
      }
    }
  }
}

Open Customize in Cursor's sidebar and check that nudgehost is switched on.

Other clients connect the same way. Point them at the server URL over streamable HTTP and send the key in an Authorization: Bearer header. The server accepts MCP versions 2025-06-18, 2025-11-25 and 2026-07-28.

Ask in plain words, for example "Publish report.html to NudgeHost and give me the link." The agent picks the tool and replies with a nudgehost.com link, or a nudgehost.site address for a ZIP site.

The link works the same as one you get when you upload a file and copy its link. Anyone who has it can open the file without signing in. The file also appears in your dashboard, where you can swap the file without changing the URL or, on a paid plan, add a password.

Scripts, CI jobs and agents without MCP can make the same upload in three requests, and in an n8n workflow the NudgeHost node's Upload operation makes all three once you install the NudgeHost node in n8n. Send each one to www.nudgehost.com, because the bare nudgehost.com redirects and the redirect drops the Authorization header.

1. Start the upload with the file's name, type and exact size in bytes.

curl -X POST https://www.nudgehost.com/api/v1/uploads \
  -H "Authorization: Bearer nh_sk_REPLACE_WITH_YOUR_OWN_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "filename": "report.pdf",
    "contentType": "application/pdf",
    "fileSize": 182734
  }'

2. Send the file to the upload.url in the reply, with the headers it lists, within 5 minutes.

curl -X PUT "UPLOAD_URL_FROM_STEP_1" \
  -H "Content-Type: application/pdf" \
  --data-binary @report.pdf

3. Finish the upload with the id from step 1. The url in the reply is the link.

curl -X POST \
  https://www.nudgehost.com/api/v1/uploads/ID_FROM_STEP_1/complete \
  -H "Authorization: Bearer nh_sk_REPLACE_WITH_YOUR_OWN_KEY"

Listing and deleting files, error codes and rate limits are in the API documentation.

Files an agent uploads count toward your plan the same as your own.

Once a free account holds 3 active links, the next upload is refused with a message pointing to the Pro plan. A password can be set from the dashboard only, not through the API.

If a call fails, our troubleshooting guide quotes the size and link-limit messages and what to do about each.