NudgeHost MCP server

NudgeHost is a file-hosting service for people and AI agents. Upload any file and get a link in seconds.

This repository describes NudgeHost's remote MCP server and holds its registry entry. The server runs at https://www.nudgehost.com/api/mcp, so there is nothing here to install or run. Full documentation is at nudgehost.com/docs/api.

Registry entry

The server is listed in the official MCP Registry as com.nudgehost/file-hosting. server.json in this repository is that entry.

Related MCP server: Onimi Pages Remote MCP

You need an API key or a sign-in

The MCP server's tools act on a NudgeHost account, the same account you upload with on the website. Every request carries either an API key or, from a client that supports sign-in such as Claude, an access token from signing in to NudgeHost. A free account is enough. Every plan can use the API, including the free one. A free account made from 12 November 2026 holds 1 key at a time, and Lite and older free accounts hold 2.

1. Sign up at nudgehost.com.

2. Open the API keys panel of your dashboard and create a key. It is shown once, so copy it before you close the panel.

3. Set the environment variable NUDGEHOST_API_KEY to that key, then start or restart your client.

Send every request to www.nudgehost.com. The apex, nudgehost.com, redirects to www, and the Authorization header is dropped on that hop, so a good key comes back 401. The setups below already use www.

The four tools

Connecting a client

These setups are copied from Connecting a client on the docs page.

Each setup below names an environment variable, NUDGEHOST_API_KEY, rather than the key itself, so the key stays out of the config file. Set that variable to an API key from your dashboard, then start or restart the client so it reads the new value.

Claude Code. Put this in .mcp.json in the folder you start Claude Code from. Tested 13 October 2026, on its default runtime and with MCP_PROTOCOL_NEGOTIATION set to legacy.

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

Cursor. Add this entry to ~/.cursor/mcp.json, which Cursor reads for every project. Tested 13 October 2026.

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

Codex CLI. Add this table to ~/.codex/config.toml. It needs no feature flag. Tested 13 October 2026.

[mcp_servers.nudgehost]
url = "https://www.nudgehost.com/api/mcp"
bearer_token_env_var = "NUDGEHOST_API_KEY"

The Codex CLI test covered connecting and listing links.

Cursor plugin

This repository is also a Cursor plugin. Its mcp.json points Cursor at the server above, and .cursor-plugin/plugin.json declares one required setting, NUDGEHOST_API_KEY, for an API key from the API keys panel of your NudgeHost dashboard. The plugin holds no key itself.

Example

Publishing a ZIP as a site from Cursor walks through the three steps that turn a folder into a live site.

Rate limits

Each key gets a fixed number of requests per 60 second window, set by the account's plan.

• Free: 20 requests per 60 seconds

• Lite: 20 requests per 60 seconds

• Pro: 60 requests per 60 seconds

• Studio: 150 requests per 60 seconds

The MCP tools and the REST API share one budget per key. A client that signs in gets one budget per account instead, shared by every app signed in to it. Upload size and the number of live links also depend on the plan, and the pricing page has the current figures.

Licence

The text and examples in this repository are under the MIT licence. The NudgeHost service has its own terms.