Power your agent
The publisher's own URL. Not a PlugMCP endpoint.
Host a copy with our keys and logs.
https://mcp.moltlinestudio.com/humanizerThe Claude button above opens Claude with the name and URL filled in. You still confirm it there.
claude mcp add --transport http com.moltlinestudio-humanizer https://mcp.moltlinestudio.com/humanizerRun in a terminal.
{ "mcpServers": { "com.moltlinestudio-humanizer": { "command": "npx", "args": [ "-y", "mcp-remote", "https://mcp.moltlinestudio.com/humanizer" ] } }}claude_desktop_config.json
Remote URL or a command on your machine? How the two installs differ
Run on PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
LaunchFrom the publisher
A thin, dependency-free stdio bridge to Moltline Studio's fleet of 22 hosted MCP servers.
Most modern MCP clients can connect to the fleet directly over Streamable HTTP — no install needed (see Direct connection below). This bridge exists for clients that only speak the stdio transport: it proxies newline-delimited JSON-RPC between your client and the hosted server, verbatim, with no telemetry and no dependencies beyond the Python 3.9+ standard library.
Find AI-isms with evidence and fingerprint a writing voice from samples. 3 of 5 free.
MOLTLINE_LICENSE in your MCP client's environment; the bridge sends it as the X-Moltline-License header and never writes it to argv, URLs or logs. See auth.md.Find it on: Smithery · MCPize · Glama · Clawmart · MCP Registry
Machine-readable discovery: api-catalog · per-server card at https://mcp.moltlinestudio.com/<server>/.well-known/mcp/server-card.json · fleet health.
If your MCP client supports Streamable HTTP (Claude Desktop, Claude Code, Cursor, and most current clients do), point it straight at the hosted endpoint — nothing to install:
{
"mcpServers": {
"moltline-timeops": {
"type": "http",
"url": "https://mcp.moltlinestudio.com/timeops"
}
}
}
Swap timeops for any slug in the table above.
Run directly (recommended) — the bridge is a single stdlib-only file, so a clone is all you need:
git clone https://github.com/GarphenGate/moltline-mcp.git
python3 moltline-mcp/moltline_mcp.py timeops # any of the 22 slugs; default: catalog
Docker — see Docker below if you prefer a container.
A PyPI package is planned; until then, use the methods above.
Point your MCP client at the script with an absolute path:
{
"mcpServers": {
"moltline-timeops": {
"command": "python3",
"args": ["/absolute/path/to/moltline-mcp/moltline_mcp.py", "timeops"]
}
}
}
Or run it through Docker (after docker build -t moltline-mcp .):
{
"mcpServers": {
"moltline-timeops": {
"command": "docker",
"args": ["run", "-i", "--rm", "moltline-mcp", "timeops"]
}
}
}
python3 moltline_mcp.py [server] [--timeout SECONDS] [--list] [--version]
server — one of the 22 slugs (default catalog); anything else fails fast with the valid list.--timeout — per-request timeout in seconds (default 300, or env MOLTLINE_TIMEOUT).--list — print the server slugs and exit.MOLTLINE_BASE_URL — override the fleet base URL (for testing).MOLTLINE_LICENSE — your Moltline license, sent as the X-Moltline-License
header to unlock premium tools. Omit it and the bridge runs free-tier only.MOLTLINE_DEBUG=1 — diagnostic logging on stderr (stdout stays protocol-clean).
The license is never logged; debug output reports only whether one is configured.The bridge also runs containerized (stdio in, network egress to the fleet required):
docker build -t moltline-mcp .
docker run -i --rm moltline-mcp timeops # any of the 22 slugs; default: catalog
See Client configuration for the matching mcpServers entry.
One process per server connection. Each JSON-RPC message read from stdin is POSTed to https://mcp.moltlinestudio.com/<server>; JSON and SSE-framed responses are relayed back to stdout as newline-delimited JSON. The bridge tracks the server-assigned Mcp-Session-Id and echoes the negotiated MCP-Protocol-Version, per the Streamable HTTP transport spec. It never inspects, stores, or reports your traffic.
The bridge ships with an offline test suite - no network, no dependencies:
python -m unittest -v
Twenty-two tests cover the parts that actually break in a transport bridge:
newline-delimited framing, SSE event splitting (multiple events, multi-line
data: payloads, a trailing event with no blank line, comments and named
events), session-id capture and reuse, protocol-version negotiation on
initialize only, and error relay - a JSON-RPC error document is passed
through verbatim, anything else becomes a well-formed -32603. CI runs them
on Python 3.9, 3.12 and 3.13, plus a Docker build and container smoke test.
MOLTLINE_LICENSE in the environment and the bridge forwards it as the X-Moltline-License request header. It is deliberately not a command-line flag: argv is world-readable through ps. It is never placed in a URL and never logged. Details: auth.md.MIT © 2026 Moltline Studio
© 2026 MCP Directory.
Find AI-isms with evidence and fingerprint a writing voice from samples. 3 of 5 free.
{ "mcpServers": { "com.moltlinestudio-humanizer": { "url": "https://mcp.moltlinestudio.com/humanizer", "headers": {} } }}Tools
No tool list yet. Remote servers get one after the first health check.
FAQ
Copy the http config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.
No required environment variable is listed on this record.
Moltline Humanizer is reached over HTTP.
Last checked 2026-11-08. Find AI-isms with evidence and fingerprint a writing voice from samples. 3 of 5 free.