en es ja ko zh

LinkedIn Post Generator

Name: LinkedIn Post Generator
Author: NvkAnirudh

by NvkAnirudh

Overview Schema Source Related Servers Discussions Admin

JavaScript

Hybrid

LinkedIn投稿ジェネレーター

YouTube動画からプロフェッショナルなLinkedIn投稿の下書きを自動生成するモデルコンテキストプロトコル（MCP）サーバーです。このツールは、YouTube動画からトランスクリプトを抽出し、コンテンツを要約し、ユーザーの好みに合わせて魅力的なLinkedIn投稿を生成することで、コンテンツの再利用を効率化します。

特徴

YouTube トランスクリプト抽出: YouTube 動画から自動的にトランスクリプトを抽出します
コンテンツ要約: カスタマイズ可能なトーンと対象読者で簡潔な要約を生成します
LinkedIn 投稿生成: カスタマイズ可能なスタイルとトーンでプロフェッショナルな LinkedIn 投稿を作成します
オールインワンワークフロー：YouTube URLからLinkedInの投稿までを1回の操作で実行
カスタマイズオプション: トーン、対象読者、単語数などを調整して、あなたのパーソナルブランドに合わせます
MCP統合:モデルコンテキストプロトコルをサポートするAIアシスタントとシームレスに連携

インストール

地域開発

リポジトリをクローンします。

git clone https://github.com/NvkAnirudh/LinkedIn-Post-Generator.git
cd LinkedIn-Post-Generator

依存関係をインストールします:
```
npm install
```
例に基づいて.envファイルを作成します。
```
cp .env.example .env
```

API キーを.envファイルに追加します。

OPENAI_API_KEY=your_openai_api_key
YOUTUBE_API_KEY=your_youtube_api_key

サーバーを実行します。
```
npm run dev
```
MCP Inspector でテストします。
```
npm run inspect
```

Claude Desktopでの使用

このMCPサーバーは、Claude Desktopおよびモデルコンテキストプロトコルをサポートする他のAIアシスタントと連携するように設計されています。Claude Desktopで使用するには、以下の手順に従ってください。

~/Library/Application Support/Claude/claude_desktop_config.json (Mac) または%APPDATA%\Claude\claude_desktop_config.json (Windows) にある構成ファイルを編集して、Claude Desktop を構成します。

{
  "mcpServers": {
    "linkedin-post-generator": {
      "command": "npx",
      "args": [
        "-y",
        "@smithery/cli@latest",
        "run",
        "@NvkAnirudh/linkedin-post-generator",
        "--key",
        "YOUR_SMITHERY_API_KEY",
        "--config",
        "{\"OPENAI_API_KEY\":\"YOUR_OPENAI_API_KEY\",\"YOUTUBE_API_KEY\":\"YOUR_YOUTUBE_API_KEY\"}",
        "--transport",
        "stdio"
      ]
    }
  }
}

交換する：

YOUR_SMITHERY_API_KEYを Smithery API キーに置き換えます
YOUR_OPENAI_API_KEY OpenAI API キーに置き換えます
YOUR_YOUTUBE_API_KEY YouTube API キーに置き換えます（オプション）

Claudeデスクトップを再起動します
Claude Desktopでは、APIキーを再度設定しなくてもLinkedIn投稿ジェネレーターツールにアクセスできるようになりました。

構成

アプリケーションが適切に機能するには API キーが必要です。

OpenAI APIキー（必須）: コンテンツの要約と投稿の生成に使用されます
YouTube APIキー（オプション）：YouTubeメタデータの取得を強化します

これらのキーは次の 3 つの方法で提供できます。

1. Claudeデスクトップ構成経由（推奨）

Claude DesktopとSmitheryを併用する場合、Claude Desktopの設定ファイルにAPIキーを含めることをお勧めします（ Claude Desktopとの併用セクションを参照）。これにより、APIキーはMCPサーバーに自動的に渡されるため、再度設定する必要はありません。

2. 環境変数として

ローカルで実行する場合は、 .envファイルで API キーを環境変数として設定できます。

OPENAI_API_KEY=your_openai_api_key
YOUTUBE_API_KEY=your_youtube_api_key

3. APIキー設定ツールの使用

構成または環境変数を通じて API キーを提供していない場合は、 set_api_keysツールを使用して MCP インターフェースから直接設定できます。

使用法

利用可能なツール

APIキーを設定する

ツール: set_api_keys
目的: APIキーを設定する
パラメータ:
- openaiApiKey : OpenAI APIキー（必須）
- youtubeApiKey : YouTube API キー（オプション）

APIキーを確認する

ツール: check_api_keys
目的: APIキーの設定ステータスを確認する

抜粋トランスクリプト

ツール: extract_transcript
目的: YouTube動画からトランスクリプトを取得する
パラメータ:
- youtubeUrl : YouTube動画のURL

要約トランスクリプト

ツール: summarize_transcript
目的: ビデオコンテンツの簡潔な要約を作成する
パラメータ:
- transcript : ビデオのトランスクリプトテキスト
- tone ：教育的、啓発的、専門的、または会話的
- audience : 一般、技術者、ビジネス、学術
- wordCount : 要約のおおよその単語数（100～300）

LinkedIn投稿を生成する

ツール: generate_linkedin_post
目的: 概要からLinkedInの投稿を作成する
パラメータ:
- summary : ビデオコンテンツの概要
- videoTitle : YouTube動画のタイトル
- speakerName : スピーカーの名前（オプション）
- hashtags : 関連するハッシュタグ（オプション）
- tone ：一人称、三人称、または思想的リーダー
- includeCallToAction : 行動喚起を含めるかどうか

オールインワン：YouTubeからLinkedInへの投稿

ツール: youtube_to_linkedin_post
目的: YouTube URL から LinkedIn 投稿までの完全なワークフロー
パラメータ:
- youtubeUrl : YouTube動画のURL
- tone : 投稿に望ましいトーン
- さらに追加のカスタマイズオプション

ワークフローの例

set_api_keysツールを使用して API キーを設定します
YouTube URL でyoutube_to_linkedin_postツールを使用する
公開準備が整ったLinkedIn投稿の下書きを受け取る

展開

このサーバーは、MCPサーバーのホスティングと共有プラットフォームであるSmithery上にデプロイされています。デプロイメント設定はsmithery.yamlファイルで定義されています。

独自のインスタンスをデプロイするには:

Smitheryでアカウントを作成する
Smithery CLI をインストールします。
```
npm install -g @smithery/cli
```
サーバーを展開します。
```
smithery deploy
```

貢献

皆様からの投稿を歓迎いたします！LinkedIn 投稿ジェネレーターへの投稿方法は以下の通りです。

問題の報告

GitHub の問題追跡ツールを使用してバグを報告したり機能を提案したりします
再現手順、予想される動作、実際の動作など、問題に関する詳細な情報を提供してください。
バグを報告する際には、環境の詳細（OS、Node.jsのバージョンなど）を含めてください。

プルリクエスト

リポジトリをフォークする
新しいブランチを作成します（ git checkout -b feature/your-feature-name ）
変更を加える
変更によって既存の機能が損なわれないことを確認するためにテストを実行します
変更をコミットします（ git commit -m 'Add some feature' ）
ブランチにプッシュします ( git push origin feature/your-feature-name )
プルリクエストを開く

開発ガイドライン

既存のコードスタイルと規則に従う
明確でコメント付きのコードを書く
新機能のテストを含める
変更を反映するようにドキュメントを更新する

機能の提案

新しい機能や改善点のアイデアがある場合:

既存の問題をチェックして、あなたの提案がすでに提案されているかどうかを確認してください
そうでない場合は、「機能強化」というラベルを付けて新しい問題を開いてください。
機能とその潜在的なメリットを明確に説明する

ドキュメント

ドキュメントの改善はいつでも歓迎します。

タイプミスを修正したり、既存のドキュメントを明確にしたりする
例や使用例を追加する
ドキュメントの構造や構成を改善する

このプロジェクトに貢献することにより、貢献内容がプロジェクトの MIT ライセンスの下でライセンスされることに同意したことになります。

ライセンス

マサチューセッツ工科大学

Available Tools

6 tools

check_api_keysD

ParametersJSON Schema

Name	Required	Description	Default
No parameters

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

extract_transcriptD

ParametersJSON Schema

Name	Required	Description	Default
`youtubeUrl`	Yes	YouTube video URL

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

generate_linkedin_postD

ParametersJSON Schema

Name	Required	Description	Default
`summary`	Yes	Summary of the video content
`videoTitle`	Yes	Title of the YouTube video
`speakerName`	No	Name of the speaker in the video (optional)
`hashtags`	No	Relevant hashtags (optional)
`tone`	No	Tone of the LinkedIn post	first-person
`includeCallToAction`	No	Whether to include a call to action

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

set_api_keysD

ParametersJSON Schema

Name	Required	Description	Default
`openaiApiKey`	Yes	Your OpenAI API key
`youtubeApiKey`	No	Your YouTube API key (optional)

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

summarize_transcriptD

ParametersJSON Schema

Name	Required	Description	Default
`transcript`	Yes	Video transcript text
`tone`	No	Tone of the summary	professional
`audience`	No	Target audience for the summary	general
`wordCount`	No	Approximate word count for the summary

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

youtube_to_linkedin_postD

ParametersJSON Schema

Name	Required	Description	Default
`youtubeUrl`	Yes	YouTube video URL
`tone`	No	Tone of the LinkedIn post	first-person
`summaryTone`	No	Tone of the summary	professional
`audience`	No	Target audience	general
`hashtags`	No	Relevant hashtags (optional)
`includeCallToAction`	No	Whether to include a call to action

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

1 tool updatev1.0.0Jan 2, 2026
- Changedcheck_api_keys1 field changed
  - removedInput schema / additionalProperties
```
Removed value: -false
```
6 tool updatesAug 18, 2025
- First observedcheck_api_keys
- First observedextract_transcript
- First observedgenerate_linkedin_post
- First observedset_api_keys
- First observedsummarize_transcript
- First observedyoutube_to_linkedin_post

Deploy Server

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

D1.9/5.0

Scored 2026-04-18 10:40 across 6 tools

Disambiguation4/5

Most tools have distinct purposes: checking/setting API keys, extracting/summarizing transcripts, generating posts, and a combined YouTube-to-post workflow. However, 'generate_linkedin_post' and 'youtube_to_linkedin_post' could cause some confusion about when to use each, as the latter might implicitly include extraction and summarization steps.

Naming Consistency4/5

Tool names follow a consistent snake_case pattern with clear verb-action structures (e.g., 'check_api_keys', 'extract_transcript'). The only minor deviation is 'youtube_to_linkedin_post', which uses a 'source_to_destination' format instead of a verb-noun style, but it remains readable and fits the overall convention.

Tool Count5/5

With 6 tools, this server is well-scoped for its purpose of generating LinkedIn posts from various inputs. Each tool appears to serve a specific function in the workflow, from API management to content processing and post generation, without being overly sparse or bloated.

Completeness3/5

The toolset covers key steps like API setup, content extraction, summarization, and post generation, but there are notable gaps. For example, there's no tool for editing or updating existing posts, managing drafts, or handling post scheduling, which could limit agent workflows in a complete LinkedIn posting lifecycle.

Maintenance

ActivityInactive

ResponsivenessUnresponsive

Resources

GitHub Repository

Need Help?

Reddit Discussion

Related Servers

Related MCP Connectors

qpost-mcp
io.github.arslan2012
MCP server for QPost — lets AI agents publish video and image posts to YouTube, TikTok, Instagram.
Social Media
1
MysocialOAuth
io.mysocial
Social media MCP server: your Instagram, TikTok, YouTube, LinkedIn and Threads history for your AI.
Social Media
1
YouTube Transcript Downloader A
com.youtubetranscriptdownload
An MCP server that gives any LLM or agent clean YouTube transcripts on demand: a single video, a whole channel, or a playlist, plus AI cleanup of auto-generated captions. API-key auth, credit-based, same backend as the public v1 API. Get a free API key with 25 free credits at youtubetranscriptdownload.com/account.
Entertainment & Media Research & Data Web Scraping
42
PostHeroOAuth
ai.posthero
PostHero MCP server — schedule and publish social media posts from any MCP-compatible AI tool
1

Related MCP Servers

mcp-server-youtube-transcript
Search Entertainment & Media
kimtaeyoon83
A
license
A
quality
F
maintenance
A Model Context Protocol server that enables retrieval of transcripts from YouTube videos. This server provides direct access to video captions and subtitles through a simple interface.
Updated 3 months ago (2026-07-21 03:28 UTC)
1
907 npm
600
MIT
YouTube Translate MCP
Entertainment & Media Language Translation Text Summarization
brianshin22
A
license
A
quality
D
maintenance
A Model Context Protocol server that enables access to YouTube video content through transcripts, translations, summaries, and subtitle generation in various languages.
Updated 2 years ago (2025-03-17 04:34 UTC)
5
5
MIT
mcp-youtube-transcript
Web Scraping Multimedia Processing Entertainment & Media
sinco-lab
A
license
A
quality
D
maintenance
A Model Context Protocol server that enables retrieval of transcripts from YouTube videos. This server provides direct access to video transcripts and subtitles through a simple interface, making it ideal for content analysis and processing.
Updated 5 months ago (2026-05-20 08:21 UTC)
1
363 npm
39
MIT
YouTube to LinkedIn MCP Server
Text Summarization Marketing Agent Orchestration
NvkAnirudh
A
license
Not graded
quality
D
maintenance
A Model Context Protocol (MCP) server that automates generating LinkedIn post drafts from YouTube videos. This server provides high-quality, editable content drafts based on YouTube video transcripts.
Updated 2 years ago (2025-04-01 18:40 UTC)
1
MIT

LinkedIn投稿ジェネレーター

目次

特徴

インストール

地域開発

Claude Desktopでの使用

構成

1. Claudeデスクトップ構成経由（推奨）

2. 環境変数として

3. APIキー設定ツールの使用

使用法

利用可能なツール

APIキーを設定する

APIキーを確認する

抜粋トランスクリプト

要約トランスクリプト

LinkedIn投稿を生成する

オールインワン：YouTubeからLinkedInへの投稿

ワークフローの例

展開

貢献

問題の報告

プルリクエスト

開発ガイドライン

機能の提案

ドキュメント

ライセンス

Available Tools

Tool Schema Changelog

Maintenance

Resources

Related MCP Connectors

Related MCP Servers

Appeared in Searches