LinkedNav

io.github.linglistackPublished by GitHub account linglistackv1.0.0Updated Oct 24, 2026

Run LinkedIn outreach from your AI chat: find leads, launch campaigns, send, and reply.

VerifiedStreamable HTTPWeb executableCommunication & CollaborationBusiness & Commerce

Overview

AI-generated overview

Lets an assistant run LinkedIn outreach from chat: find leads, launch campaigns, send messages, and reply.

What you can do
LinkedNav connects an AI assistant to a LinkedIn outreach workflow. According to the registry description, it lets the assistant find leads, launch campaigns, send outreach messages, and reply to responses, all from within the chat. No individual tools are listed in the manifest, so the exact operations available are not documented here.
When to use it
Useful when you want an assistant to help with LinkedIn prospecting and outreach without switching to a separate dashboard, for example building lead lists, starting campaigns, or drafting and sending replies.
Requirements
A remote MCP endpoint at mcp.linkednav.com over streamable HTTP. Authentication is required via OAuth, and requests carry an Authorization header containing a LinkedNav API key in the form Bearer . The key is created in the LinkedNav web app. A LinkedNav account and network access are needed.
Before you install
The Authorization header carries a secret API key; keep it private and revoke it if exposed. The server can send messages and replies on LinkedIn and launch campaigns, which are outward-facing actions that may reach real people and may consume paid plan limits. Review what the assistant is about to send before approving it.

Installation

In SourceWeft

  1. Open LinkedNav in the dashboard and add it to a workspace.
  2. Connect the required 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.linglistack%2Flinkednav-mcp/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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "linkednav": {
      "type": "http",
      "url": "https://mcp.linkednav.com/"
    }
  }
}

README

This repository has no README.

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

60% 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.

  • License10 pts

    Declare a license in the repository or the registry entry.