LinkedIn Decision Maker Finder

io.github.piotrv1001Published by GitHub account piotrv1001v1.0.0Updated Oct 24, 2026

Find decision makers at any company: name, job title and LinkedIn profile URL. No login needed.

The publisher's own server: Finder Jobs

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingBusiness & Commerce

Overview

AI-generated overview

A remote Apify-hosted MCP server that lets an assistant find decision makers at a company, returning names, job titles and LinkedIn profile URLs.

What you can do
Look up decision makers at a given company and return their names, job titles and LinkedIn profile URLs. No login to LinkedIn is required for the lookup.
When to use it
Useful when you need to identify senior contacts or decision makers at a target company for outreach, research or sales prospecting, without logging into LinkedIn yourself.
Requirements
A remote endpoint hosted on Apify; no local runtime or package. Requires an Apify API token sent as a bearer token in the Authorization header. Usage is billed to your Apify account.
Before you install
You must supply your own Apify API token in the Authorization header, and usage is billed to your Apify account, so calls may incur costs. Results are sent to and processed by Apify's hosted service.

Installation

In SourceWeft

  1. Open LinkedIn Decision Maker Finder 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/io.github.piotrv1001%2Flinkedin-decision-maker-finder/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-decision-maker-finder": {
      "type": "http",
      "url": "https://piotrv1001--linkedin-decision-maker-finder.apify.actor/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.0LatestSep 16, 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.

Other Finder integrations