Skip to main content
Glama
mcp-htmlentities

mcp-htmlentities

by pipeworx-io

mcp-htmlentities

HTML entities MCP.

Part of Pipeworx — an MCP gateway connecting AI agents to 1865+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.

Tools

Tool

Description

encode_html

Encode text to HTML entities. mode "basic" (default) escapes only & < > " '; mode "extended" also converts every non-ASCII character to a numeric entity. Keyless, offline.

decode_html

Decode HTML entities (named like &amp; and numeric like © / ©) back to plain text. Keyless, offline.

Related MCP server: mcp-base64

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "htmlentities": {
      "url": "https://gateway.pipeworx.io/htmlentities/mcp"
    }
  }
}

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/htmlentities/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — ask_pipeworx, discover_tools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via ask_pipeworx, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.

Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://gateway.pipeworx.io/mcp"
    }
  }
}

Both URLs reach the same gateway and the same 1865+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.

No MCP client? Call it over HTTP

curl -X POST https://gateway.pipeworx.io/v1/tools/encode_html \
  -H 'Content-Type: application/json' \
  -d '{"text":"Hello & welcome to \"my site\""}'

No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/encode_html. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.

Run it from npm

@pipeworx/mcp-htmlentities is a local stdio bridge to the Pipeworx gateway: your MCP client starts it with npx, and it forwards every call to the same https://gateway.pipeworx.io/htmlentities/mcp endpoint shown above. It needs network access; there is no offline mode.

{
  "mcpServers": {
    "htmlentities": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-htmlentities"]
    }
  }
}

Without a key it calls anonymously, capped at 50 calls a day. A free account raises that to 200 a day: get a key at https://pipeworx.io/signup and add "env": { "PIPEWORX_API_KEY": "<your key>" } to the server entry. The key is sent as a Bearer token, the same way a hosted connection sends it, so calls are metered and billed exactly as they are there.

It lists only this pack's tools by default. Set PIPEWORX_META_TOOLS=1 to also list ask_pipeworx and the other gateway-wide tools.

Behind an HTTPS proxy: Node's built-in fetch does not read HTTPS_PROXY by default. Newer Node releases honour it when NODE_USE_ENV_PROXY=1 is set; check your Node version's documentation.

Using with ask_pipeworx

Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:

ask_pipeworx({ question: "your question about Htmlentities data" })

The gateway picks the right tool and fills the arguments automatically.

More

License

MIT

Tool Schema Changelog

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

Loading tool schema changelog…

    Related MCP Connectors

    • SimpleTexting MCP server for ChatGPT, Claude and any AI agent: list conversations, send message, schedule message, schedule campaign, add contact to list, assign conversation, list segments and list keywords in your own SimpleTexting account. Cotlet works in the account through your Cloud Browser, a real Chrome where you sign in to SimpleTexting yourself; Cotlet does not store your password and you need no SimpleTexting API key. About the official SimpleTexting API: Yes, SimpleTexting has a REST API on any paid plan, but only on approval, and it has no official MCP server (checked 23 Oct 2026). You send support your use case and a written acknowledgment of the terms, and a token follows. Setup and FAQ: https://cotlet.dev/integrations/simpletexting-api-mcp-server

    • 17hats MCP server for ChatGPT, Claude and any AI agent: add contact, create project, send quote, send invoice and record payment in your own 17hats account. Cotlet works in the account through your Cloud Browser, a real Chrome where you sign in to 17hats yourself; Cotlet does not store your password and you need no 17hats API key. About the official 17hats API: 17hats publishes no public API. Its only key is for Zapier, on the new subscription plan, and that integration "is limited to importing, updating and syncing Contacts" (checked 9 Nov 2026). Setup and FAQ: https://cotlet.dev/integrations/17hats-api-mcp-server

      https://cotlet.dev/mcp/v1/17hats
    • Mautic MCP server for ChatGPT, Claude and any AI agent: list contacts, merge contacts, change contact segments, set Do Not Contact, create segment, get email stats and activate or pause campaign in your own Mautic account. Cotlet works in the account through your Cloud Browser, a real Chrome where you sign in to Mautic yourself; Cotlet does not store your password and you need no Mautic API key. About the official Mautic API: Mautic has a full REST API but no official MCP server (checked 23 Oct 2026). The API is off until an admin switches it on under Configuration > API Settings, and calls need OAuth2 or basic auth set up on that instance. Setup and FAQ: https://cotlet.dev/integrations/mautic-api-mcp-server

      https://cotlet.dev/mcp/v1/mautic
    • HappyFox MCP server for ChatGPT, Claude and any AI agent: search tickets, reply to ticket, add private note, update ticket, apply canned action and list queues in your own HappyFox account. Cotlet works in the account through your Cloud Browser, a real Chrome where you sign in to HappyFox yourself; Cotlet does not store your password and you need no HappyFox API key. About the official HappyFox API: HappyFox has a full REST API (version 1.1) for tickets, contacts and assets, but no official MCP server for working tickets (checked 20 Oct 2026). The API uses an API key and auth code from an app an admin enables, and it takes status, priority, assignee and custom fields as integer IDs. Setup and FAQ: https://cotlet.dev/integrations/happyfox-api-mcp-server

    Related MCP Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables encoding and decoding of text between Base64, Base64URL, Base32, and Hex formats, supporting offline keyless operations.
      109 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides tools to inspect Unicode characters, escape/unescape strings in various formats (JS, HTML, URL), all offline and keyless.
      76 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Encode latitude/longitude to geohash strings and decode geohashes to coordinates with offline, keyless operation.
      74 npm
      MIT