Social Media MCP Server

social-media-mcp
documentation
# Social Media Integration Summary

## Current Status

| Platform | Status | Notes |
|----------|--------|-------|
| Mastodon | ✅ Working | Successfully posting real content |
| Twitter | ✅ Working | Successfully posting real content |
| LinkedIn | ⚠️ Mock Mode | Using mock implementation due to authentication issues |

## Mastodon Integration

The Mastodon integration is fully functional and posting real content to the Mastodon account. We fixed the following issues:

1. **Authentication Timing**: Fixed the asynchronous authentication process to ensure authentication completes before posting
2. **Content Length**: Shortened content to fit within Mastodon's 500 character limit

The latest post is available at: https://mastodon.social/@tayler_ramsay/114117710454587930

## Twitter Integration

The Twitter integration is fully functional and posting real content to the Twitter account. No issues were identified.

## LinkedIn Integration

The LinkedIn integration is currently using mock mode due to authentication issues. We made the following changes:

1. **Updated Credentials**: Added the new client ID and client secret provided
2. **Updated API Endpoints**: Changed the posting endpoint to use `/rest/posts` as specified in the LinkedIn API documentation
3. **Updated Request Format**: Modified the request format to match the LinkedIn API requirements

However, we're still encountering an authentication error:

```
LinkedIn API Error Request failed with status code 401 {"response":{"status":401, "statusText":"Unauthorized", "data":{"status":401, "serviceErrorCode":65600, "code":"INVALID_ACCESS_TOKEN", "message":"Invalid access token"}}}
```

### LinkedIn Authentication Issue

The current issue is that we're trying to use the client secret as an access token, which is not valid. LinkedIn requires a proper OAuth 2.0 access token, which is obtained through the OAuth flow:

1. Redirect user to LinkedIn authorization page
2. User grants permission
3. LinkedIn redirects back with an authorization code
4. Exchange the authorization code for an access token

This process requires user interaction and cannot be done programmatically without user involvement.

## Next Steps

1. **LinkedIn Authentication**: To fix the LinkedIn integration, we have:
   - Created a proper OAuth 2.0 flow script (`scripts/linkedin-oauth.js`) to obtain a valid access token
   - The script opens a browser for the user to authenticate
   - After authentication, the script captures and logs the access token
   - The user can then add the access token to the configuration

   To use the script:
   ```bash
   cd scripts
   npm install
   npm run linkedin-oauth
   ```

   The script now includes enhanced browser detection and fallback mechanisms:
   - First tries to open in the default browser
   - If that fails, tries specific browsers (Chrome, Edge, Firefox)
   - If all browser attempts fail, falls back to platform-specific commands
   - As a last resort, displays the URL for manual opening
   - This helps avoid issues where LinkedIn tries to open in the app instead of a browser
   
   The script now uses LinkedIn's default redirect URI:
   ```
   https://www.linkedin.com/developers/tools/oauth/redirect
   ```
   
   This means:
   - LinkedIn will display the authorization code on their page after authentication
   - You'll need to copy this code and paste it back into the terminal
   - The script will then exchange the code for an access token
   
   If you encounter a "redirect_uri does not match the registered value" error, see [LinkedIn Redirect URI Configuration](./linkedin-redirect-uri.md) for detailed instructions on how to fix it.
   
   If you encounter a "unauthorized_scope_error" error, see [LinkedIn OAuth Scopes](./linkedin-scope.md) for information on how to fix scope-related issues.

   After getting the access token, update it in the configuration:
   ```bash
   # Option 1: Add to .env file
   LINKEDIN_ACCESS_TOKEN=your_access_token_here

   # Option 2: Update directly in src/config/index.ts
   ```

   Then navigate back to the main project directory and rebuild the application:
   ```bash
   cd ..
   npm run build
   ```

2. **Documentation**: We've created comprehensive documentation for all three integrations:
   - [Mastodon Integration](./mastodon-integration.md)
   - [Twitter Integration](./twitter-integration.md)
   - [LinkedIn Integration](./linkedin-integration.md)

3. **Testing**: We've tested the Mastodon integration and confirmed it's working correctly. The LinkedIn integration still needs proper authentication to work.