Skip to main content
Glama
Sign In
whamlink-mcp

whamlink-mcp

by billkinddev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

whamlink-mcp

An MCP server for whamlink — let any MCP client (Claude Desktop, IDEs, agents) publish a single file to a permanent, shareable link.

Setup

  1. Get an API key: register at https://whamlink.com/app, then create a key under Keys.

  2. Add the server to your MCP client config, passing the key via WHAMLINK_API_KEY.

Claude Desktop (claude_desktop_config.json)

{
  "mcpServers": {
    "whamlink": {
      "command": "npx",
      "args": ["-y", "whamlink-mcp"],
      "env": { "WHAMLINK_API_KEY": "wl_your_key_here" }
    }
  }
}

Running from source instead of npm: "command": "node", "args": ["/path/to/whamlink/mcp/dist/index.js"] (after npm install && npm run build in mcp/).

Environment

  • WHAMLINK_API_KEY (optional) — your whamlink API key. If unset, the server still starts; the agent can register to create an account in-session (save the returned key here to persist).

  • WHAMLINK_BASE_URL (optional) — defaults to https://whamlink.com.

Related MCP server: htmldrop-mcp

Tools

Tool

What it does

register

Create an account on the user's behalf (consent + real email). Lets a new user go zero-to-published without setting a key first.

publish_link

Publish HTML / Markdown / PDF / image / text → a permanent URL. Public by default; set visibility to private / password / email to gate it.

list_links

List your published links (id, slug, mode, visibility, URL).

set_link_access

Change a link's visibility, password, shared-email list, allowNetwork, or title.

replace_link_content

Replace a link's content in place — the URL stays the same.

delete_link

Permanently delete a link.

PDF and image files aren't supported over MCP (tool args are JSON, which can't carry binary) — use the whamlink dashboard or the multipart API for those.

Never publish secrets, API keys, or private data. Public links are unlisted but anyone with the URL can view them; use private/password/email visibility for anything sensitive.

Develop

npm install
npm run build
npm test

Available Tools

6 tools
delete_linkB

Permanently delete a published link by its id.

Inputs: id (required).

list_linksA

List the links you've published (id, slug, title, mode, visibility, size, URL).

Inputs: no named parameters.

publish_linkA

Publish text-based content (HTML, Markdown, or plain text) to a permanent whamlink URL. Links are public (unlisted) by default; set visibility to private/password/email to gate them. (PDF/image files aren't supported over MCP — use the whamlink dashboard or multipart API for those.) Never publish secrets or private data.

Inputs: mode (required), content (required), title, password, +3 more.

registerA

Create a whamlink account on the USER'S behalf. Only call this with the user's explicit consent and their REAL email — a verification link is sent there. Returns an API key used for the rest of this session; tell the user to set it as WHAMLINK_API_KEY in their MCP config to keep it across restarts.

Inputs: name (required), email (required).

replace_link_contentC

Replace a link's content in place — the URL stays the same.

Inputs: id (required), mode (required), content (required).

set_link_accessC

Change a link's access: visibility (public/private/password/email), password, shared email list, allowNetwork, or title.

Inputs: id (required), title, password, visibility, +2 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.6/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a distinct operation: account registration, link creation, listing, deletion, content replacement, and access control. There is no overlap in functionality.

    Naming Consistency4/5

    All tools use snake_case and generally follow verb_noun pattern (delete_link, list_links, publish_link, replace_link_content, set_link_access). However, 'register' is a single verb without a noun, breaking the pattern slightly.

    Tool Count5/5

    With 6 tools, the server provides a focused set covering the core lifecycle of links (create, read, update, delete, access management) plus account setup. This is well-scoped.

    Completeness4/5

    The set covers CRUD and access control for text links. A minor gap is the lack of a tool to retrieve a single link's full details (list_links returns all, but may not include all fields). The file upload limitation is noted, but that's a domain constraint.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Resources

    Related MCP Connectors

    Related MCP Servers