Hellofew

com.hellofewPublished by hellofew.comOfficial publisherv1.0.0Updated Nov 7, 2026

LinkedIn outreach you approve: read drafted messages, approve or skip leads, read replies.

VerifiedStreamable HTTPWeb executableCommunication & CollaborationBusiness & Commerce

Overview

AI-generated overview

Hellofew lets an assistant review LinkedIn outreach drafts, approve or skip leads, and read replies in a workspace you control.

What you can do
  • Read drafted LinkedIn outreach messages awaiting your decision
  • Approve or skip individual leads in the outreach queue
  • Read replies from contacted leads
  • No tool list is published, so exact operations beyond these are not documented
When to use it
Useful if you run LinkedIn outreach through Hellofew and want an assistant to help triage drafted messages, decide which leads to approve or skip, and follow up on replies without opening the web app.
Requirements
A remote MCP endpoint at hellofew.com over streamable HTTP. Requires a Hellofew workspace key, obtained from the provider's integrations page, sent as a bearer token in the Authorization header.
Before you install
The workspace key is a secret sent in the Authorization header; keep it out of logs and shared transcripts. Approving leads triggers real outreach to real people, so review decisions carefully. Replies and lead data are handled through the Hellofew service.

Installation

In SourceWeft

  1. Open Hellofew in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. 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/com.hellofew%2Fhellofew/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": {
    "hellofew": {
      "type": "http",
      "url": "https://hellofew.com/api/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestNov 7, 2026

Score

67% 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 listed15 pts

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

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.