Linkedin Humblebrag

io.github.pipeworx-ioPublished by GitHub account pipeworx-iov0.1.4Updated Oct 30, 2026

linkedin-humblebrag MCP — wraps StupidAPIs (keyless — no credential needed)

VerifiedStreamable HTTPWeb executableCommunication & CollaborationMedia & Design

Overview

AI-generated overview

A remote MCP endpoint that turns a stated achievement into a humorous, self-deprecating LinkedIn post ready to share.

What you can do
  • Generate a satirical LinkedIn post from an accomplishment, returning shareable text with vulnerability and humor.
  • Ask questions in plain English through the gateway's routing meta-tools, which pick a tool and fill arguments.
  • Discover and search other tools across the wider gateway catalog from the same connection.
When to use it
Useful for quickly drafting a playful, self-deprecating social post about a promotion, launch or other milestone, or for trying out the Pipeworx gateway with a single lightweight pack.
Requirements
A remote streamable HTTP endpoint; no account or API key is needed for the first calls. Optionally runs locally via npx as a stdio server. Network access to the gateway is required.
Before you install
The pack endpoint also exposes roughly 30 shared gateway meta-tools, which add context overhead and can route requests beyond this pack. The integration is unofficial and not affiliated with the upstream provider. Generated posts are meant to be shared, so review text before publishing.

Installation

In SourceWeft

  1. Open Linkedin Humblebrag in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.pipeworx-io%2Flinkedin-humblebrag/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "linkedin-humblebrag": {
      "type": "http",
      "url": "https://gateway.pipeworx.io/linkedin-humblebrag/mcp"
    }
  }
}

README

mcp-linkedin-humblebrag

linkedin-humblebrag MCP — wraps StupidAPIs (keyless — no credential needed)

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

Tools

ToolDescription
linkedin_humblebrag_generateGenerate a humorous LinkedIn post from an achievement. Input your accomplishment and get back a self-deprecating post with vulnerability and humor. Returns the post text ready to share.

Quick Start

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

json
{  "mcpServers": {    "linkedin-humblebrag": {      "url": "https://gateway.pipeworx.io/linkedin-humblebrag/mcp"    }  }}

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/linkedin-humblebrag/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:

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

Both URLs reach the same gateway and the same 1882+ 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

bash
curl -X POST https://gateway.pipeworx.io/v1/tools/linkedin_humblebrag_generate \  -H 'Content-Type: application/json' \  -d '{"achievement":"Just got promoted to Senior Software Engineer after 5 years at the company"}'

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

Standalone (no gateway account)

This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:

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

Or run it directly to confirm it starts:

bash
npx -y @pipeworx/mcp-linkedin-humblebrag

It speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call for only this pack's tools — none of the shared meta-tools the gateway connection above adds. Same source, same tools, no ask_pipeworx routing.

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 Linkedin Humblebrag data" })

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

More

License

MIT

Source: README.md at commit b5d5c7f

Tools

0
SourceWeft has not read this server's tools yet.

Version history

5
  1. v0.1.4LatestOct 29, 2026
  2. v0.1.3Sep 27, 2026
  3. v0.1.2Sep 25, 2026
  4. v0.1.1Sep 22, 2026
  5. v0.1.0Sep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts