NvkAnirudh LinkedIn Post Generator

WHAT IT CONNECTS

What NvkAnirudh LinkedIn Post Generator gives an AI Agent

• **YouTube Transcript Extraction**: Automatically extract transcripts from any YouTube video
• **Content Summarization**: Generate concise summaries with customizable tone and target audience
• **LinkedIn Post Generation**: Create professional LinkedIn posts with customizable style and tone
• **All-in-One Workflow**: Go from YouTube URL to LinkedIn post in a single operation
• **Customization Options**: Adjust tone, audience, word count, and more to match your personal brand
• **MCP Integration**: Works seamlessly with AI assistants that support the Model Context Protocol
• Clone the repository:
• Install dependencies:
• Create a `.env` file based on the example:
• Add your API keys to the `.env` file:
• Run the server:
• Test with MCP Inspector:
• Configure Claude Desktop by editing the configuration file at `~/Library/Application Support/Claude/claude_desktop_config.json` (Mac) or `%APPDATA%\Claude\claude_desktop_config.json` (Windows):
• `YOUR_SMITHERY_API_KEY` with your Smithery API key
• `YOUR_OPENAI_API_KEY` with your OpenAI API key
• `YOUR_YOUTUBE_API_KEY` with your YouTube API key (optional)
• Restart Claude Desktop
• In Claude Desktop, you can now access the LinkedIn Post Generator tools without needing to set API keys again
• **OpenAI API Key** (required): Used for content summarization and post generation
• **YouTube API Key** (optional): Enhances YouTube metadata retrieval
• Tool: `set_api_keys`
• Purpose: Configure your API keys
• Parameters:
• `openaiApiKey`: Your OpenAI API key (required)
• `youtubeApiKey`: Your YouTube API key (optional)
• Tool: `check_api_keys`
• Purpose: Verify your API key configuration status
• Tool: `extract_transcript`
• Purpose: Get the transcript from a YouTube video
• Parameters:
• `youtubeUrl`: URL of the YouTube video
• Tool: `summarize_transcript`
• Purpose: Create a concise summary of the video content
• Parameters:
• `transcript`: The video transcript text
• `tone`: Educational, inspirational, professional, or conversational
• `audience`: General, technical, business, or academic
• `wordCount`: Approximate word count for the summary (100-300)
• Tool: `generate_linkedin_post`
• Purpose: Create a LinkedIn post from a summary
• Parameters:
• `summary`: Summary of the video content
• `videoTitle`: Title of the YouTube video
• `speakerName`: Name of the speaker (optional)
• `hashtags`: Relevant hashtags (optional)
• `tone`: First-person, third-person, or thought-leader
• `includeCallToAction`: Whether to include a call to action
• Tool: `youtube_to_linkedin_post`
• Purpose: Complete workflow from YouTube URL to LinkedIn post
• Parameters:
• `youtubeUrl`: YouTube video URL
• `tone`: Desired tone for the post
• Plus additional customization options
• Set your API keys using the `set_api_keys` tool
• Use the `youtube_to_linkedin_post` tool with a YouTube URL
• Receive a complete LinkedIn post draft ready to publish
• Create an account on Smithery
• Install the Smithery CLI:
• Deploy the server:
• Use the [GitHub issue tracker](https://github.com/NvkAnirudh/LinkedIn-Post-Generator/issues) to report bugs or suggest features
• Please provide detailed information about the issue, including steps to reproduce, expected behavior, and actual behavior
• Include your environment details (OS, Node.js version, etc.) when reporting bugs
• Fork the repository
• Create a new branch (`git checkout -b feature/your-feature-name`)
• Make your changes
• Run tests to ensure your changes don't break existing functionality
• Commit your changes (`git commit -m 'Add some feature'`)
• Push to the branch (`git push origin feature/your-feature-name`)
• Open a Pull Request
• Follow the existing code style and conventions
• Write clear, commented code
• Include tests for new features
• Update documentation to reflect your changes
• Check existing issues to see if your suggestion has already been proposed
• If not, open a new issue with the label 'enhancement'
• Clearly describe the feature and its potential benefits
• Fix typos or clarify existing documentation
• Add examples or use cases
• Improve the structure or organization of the documentation