Allows managing Bluesky social media accounts and creating posts with platform-specific settings.
Enables management of Facebook accounts and creation of posts with content type specification through the postType parameter.
Provides integration with Google Business Profile for creating business posts with enhanced features like CTAs, offers, and coupon codes.
Supports Instagram account management and post creation with specialized features for Reels including audio selection and feed sharing options.
Enables Pinterest account management and pin creation with support for destination links, titles, and image accessibility settings.
Allows management of Threads accounts and creation of posts with channel specification options.
Provides TikTok account management and video posting with content settings including privacy controls, brand content flags, and engagement settings.
Supports YouTube account management and video uploading with metadata configuration, content settings, and compliance options.
Simplified MCP Server
A Model Context Protocol (MCP) server that provides seamless integration between Claude, Cursor, Kiro ( and other MCP supported platforms) and Simplified's API. This server enables LLMs to interact with Simplified's services through standardized MCP tools, allowing for social media account management and post creation across multiple platforms.
Features
- Full MCP Protocol Support: Built using the official @modelcontextprotocol/sdk
- Social Media Management: Comprehensive social media account and post management
- Multi-Platform Support: Support for Facebook, Instagram, Twitter, LinkedIn, TikTok, YouTube, Pinterest, Threads, Google Business Profile, and Bluesky
- Type-Safe Implementation: Written in TypeScript with full type safety
- Robust Error Handling: Comprehensive error handling with detailed error messages
- Configurable Logging: Adjustable logging levels for debugging and monitoring
- Platform-Specific Features: Advanced platform-specific settings for Google Business Profile, TikTok, YouTube, Instagram, and more
- Scheduling Support: Create scheduled posts with platform-specific settings
- Authentication Management: Secure API token handling with automatic retry logic
Installation
Prerequisites
- Node.js 18.0.0 or higher
- npm 8.0.0 or higher
- A Simplified API token
Install from NPM
Install from Source
pack DXT file
Configuration
The server is configured using environment variables. Create a .env
file in your project root or set these variables in your environment:
Required Configuration
Variable | Description | Example |
---|---|---|
SIMPLIFIED_API_TOKEN | Your Simplified API token | sk_live_abc123... |
Optional Configuration
Variable | Description | Default | Options |
---|---|---|---|
SIMPLIFIED_API_BASE_URL | Simplified API base URL | https://api.simplified.com | Any valid URL |
LOG_LEVEL | Logging verbosity level | info | debug , info , warn , error |
REQUEST_TIMEOUT | API request timeout (ms) | 30000 | Any positive number |
RETRY_ATTEMPTS | Number of retry attempts | 3 | Any non-negative number |
RETRY_DELAY | Delay between retries (ms) | 1000 | Any positive number |
Workflow Tool Configuration
The server supports dynamic workflow tools that automatically discover and register tools based on available workflows. This feature is disabled by default and can be enabled through environment variables.
Variable | Description | Default | Range/Options |
---|---|---|---|
WORKFLOWS_ENABLED | Enable dynamic workflow tools | false | true , false |
WORKFLOW_DISCOVERY_INTERVAL | Auto-refresh interval (ms) | 0 (disabled) | 0-86400000 (0 = disabled) |
WORKFLOW_EXECUTION_TIMEOUT | Execution timeout (ms) | 300000 (5 min) | 1000-3600000 |
WORKFLOW_MAX_CONCURRENT_EXECUTIONS | Max concurrent executions | 10 | 1-100 |
WORKFLOW_FILTER_PATTERNS | Comma-separated name patterns | `` (none) | Wildcard patterns |
WORKFLOW_STATUS_CHECK_INTERVAL | Status polling interval (ms) | 5000 | 1000-300000 |
WORKFLOW_RETRY_ATTEMPTS | Retry attempts for failures | 3 | 0-10 |
Example Configuration
Environment-Specific Configuration Examples
Development Environment
Production Environment
Usage
Programmatic Usage
Integration with Claude
Add the server to your Claude MCP configuration:
Install DXT extension:
Extensions -> Advanced settings -> Install Extension...
Choose simplified-mcp.dxt file. Add your token.
Integration with Kiro
Add the server to your Kiro MCP configuration:
Available Tools
The server provides comprehensive social media management tools with platform-specific features, plus dynamic workflow tools for extended functionality:
Social Media Tools
Tools for managing social media accounts and posts.
get_social_media_accounts
Retrieve all connected social media accounts.
Parameters:
network
(optional): Filter by platform (facebook, instagram, linkedin, tiktok, youtube, pinterest, threads, google, bluesky, tiktokBusiness)
Example:
create_social_media_post
Create a new social media post with platform-specific settings for Google, TikTok, Threads, YouTube, Facebook, LinkedIn, Instagram, and Pinterest.
Parameters:
message
(required): Post message/content (1-5000 characters)accountId
(required): Social media account IDaction
(required): Action to perform (schedule, add_to_queue, draft)date
(optional): Scheduled date for the post (format: YYYY-MM-DD HH)media
(optional): Array of media file URLs to attach (max 10 items)additional
(optional): Platform-specific post settings and metadata
Basic Example:
Media Files
The media
parameter accepts an array of URL strings pointing to your media files:
Media Requirements:
- Maximum 10 media files per post
- URLs must be publicly accessible
- Supported formats vary by platform (images: JPG, PNG, GIF; videos: MP4, MOV, etc.)
Platform-Specific Features
The additional
parameter supports platform-specific configurations:
Google Business Profile
TikTok / TikTok Business
YouTube
Threads
Dynamic Workflow Tools
The server supports dynamic workflow tools that automatically discover and register tools based on workflows provided by a workflows-list-tool
. This feature enables the server to expose workflow-based functionality as standard MCP tools without requiring code changes.
Enabling Workflow Tools
To enable dynamic workflow tools, set the following environment variable:
When enabled, the server will:
- Query the
workflows-list-tool
to discover available workflows - Automatically register MCP tools for each discovered workflow
- Handle workflow execution through standard MCP tool calls
- Provide status checking capabilities for running workflows
Workflow Tool Discovery
The server discovers workflows by calling a workflows-list-tool
that should return an array of workflow definitions. Each workflow must conform to this schema:
Using Workflow Tools
Once discovered, workflow tools appear in the standard MCP tools list and can be called like any other tool:
Workflow Execution Flow
- Tool Call: MCP client calls a workflow tool with parameters
- Execution Start: Server makes POST call to workflow execution endpoint
- Status Polling: Server polls workflow status with minimum 1000ms intervals
- Result Return: Server returns workflow results in standard MCP format
Example execution response:
Workflow Status Checking
The server provides a built-in workflow-status-check
tool for monitoring workflow executions:
Status response includes:
- Current execution status (RUNNING, COMPLETED, FAILED, CANCELLED)
- Start and end times
- Progress information (if available)
- Input parameters and output results
- Error details (if failed)
Workflow Configuration Options
Discovery and Refresh
Execution Management
Workflow Filtering
Error Handling
Workflow Tool Examples
Data Processing Workflow
Report Generation Workflow
Machine Learning Workflow
Platform-Specific Options Reference
Platform | Available Options | Description |
---|---|---|
Google Business Profile | title , topicType , couponCode , callToActionUrl , callToActionType , termsConditions | Business post enhancements with CTAs and offers |
TikTok/TikTok Business | brandContent , privacyStatus , duetDisabled , stitchDisabled , commentDisabled | Content settings and engagement controls |
YouTube | title , license , privacyStatus , selfDeclaredMadeForKids | Video metadata and compliance settings |
audioName , shareToFeed , postType | Reel-specific settings and feed sharing | |
link , title , imageAlt | Pin destination and accessibility | |
audience | Professional audience targeting | |
postType | Content type specification | |
Threads | channel | Publishing method |
Workflow Tools
Dynamic tools automatically generated from discovered workflows. These tools are only available when WORKFLOWS_ENABLED=true
.
workflow-status-check
Check the status of a running workflow execution.
Parameters:
workflowId
(required): The original workflow IDexecutionId
(required): The workflow execution ID (UUID)
Example:
Response:
Dynamic Workflow Tools
Each discovered workflow becomes an individual MCP tool with the naming pattern workflow-{workflow-name}
. The tool parameters are dynamically generated based on the workflow's input schema.
Example Workflow Tools:
workflow-data-analysis
- Analyze datasets and generate insightsworkflow-report-generator
- Create automated reportsworkflow-image-processor
- Process and transform imagesworkflow-email-campaign
- Send targeted email campaignsworkflow-backup-system
- Perform system backups
Dynamic Tool Example:
Dynamic Tool Response:
Error Handling
The server provides comprehensive error handling with detailed error messages:
Error Types
- Configuration Errors: Missing or invalid configuration
- Authentication Errors: Invalid or expired API tokens
- API Errors: Errors from Simplified's API
- Tool Execution Errors: Errors during tool execution
- Validation Errors: Invalid tool parameters
- Workflow Discovery Errors: Issues discovering or validating workflows
- Workflow Execution Errors: Failures during workflow execution
- Workflow Timeout Errors: Workflow execution exceeding timeout limits
Error Response Format
Workflow-Specific Error Examples
Workflow Discovery Error
Workflow Execution Error
Workflow Timeout Error
Development
Building from Source
Running Tests
Development Mode
Project Structure
Workflow Configuration Guide
Understanding Workflow Tools
Workflow tools extend the server's capabilities by automatically discovering and registering tools based on external workflow definitions. This allows you to expose complex business processes, data pipelines, and automation workflows as simple MCP tools.
Configuration Parameters Explained
WORKFLOWS_ENABLED
Purpose: Master switch for workflow functionality
Default: false
Recommendation: Set to true
only when you have a workflows-list-tool
available
WORKFLOW_DISCOVERY_INTERVAL
Purpose: How often to refresh the list of available workflows
Default: 0
(disabled)
Range: 0-86400000
ms (0 = disabled, max = 24 hours)
Recommendation:
- Development:
60000
(1 minute) for rapid iteration - Production:
600000
(10 minutes) for stability - Set to
0
if workflows rarely change
WORKFLOW_EXECUTION_TIMEOUT
Purpose: Maximum time to wait for workflow completion
Default: 300000
ms (5 minutes)
Range: 1000-3600000
ms (1 second to 1 hour)
Recommendation: Set based on your longest-running workflow
WORKFLOW_MAX_CONCURRENT_EXECUTIONS
Purpose: Limit simultaneous workflow executions to prevent resource exhaustion
Default: 10
Range: 1-100
Recommendation:
- Development:
3-5
for resource-constrained environments - Production:
10-20
based on server capacity
WORKFLOW_FILTER_PATTERNS
Purpose: Control which workflows are exposed as tools
Default: `` (empty - all workflows exposed)
Format: Comma-separated wildcard patterns
Examples:
WORKFLOW_STATUS_CHECK_INTERVAL
Purpose: How often to poll workflow status during execution
Default: 5000
ms (5 seconds)
Range: 1000-300000
ms (1 second to 5 minutes)
Recommendation: Balance between responsiveness and API load
WORKFLOW_RETRY_ATTEMPTS
Purpose: Number of retry attempts for failed workflow operations
Default: 3
Range: 0-10
Recommendation:
- Development:
1
for faster failure feedback - Production:
3-5
for reliability
Configuration Best Practices
Development Environment
Production Environment
Testing Environment
Configuration Validation
The server validates all workflow configuration on startup and provides detailed error messages for invalid values:
Performance Considerations
API Rate Limiting
- Set
WORKFLOW_DISCOVERY_INTERVAL
to at least 60 seconds to avoid rate limits - Use
WORKFLOW_STATUS_CHECK_INTERVAL
of at least 2 seconds for status polling - Consider the total API load: discovery + (concurrent executions × status checks)
Resource Management
- Monitor memory usage with high
WORKFLOW_MAX_CONCURRENT_EXECUTIONS
- Long-running workflows may require increased
WORKFLOW_EXECUTION_TIMEOUT
- Use workflow filtering to reduce the number of registered tools
Monitoring Recommendations
Troubleshooting
Common Issues
Server Won't Start
Problem: Server fails to start with configuration error.
Solution:
- Verify your
.env
file containsSIMPLIFIED_API_TOKEN
- Check that your API token is valid
- Ensure Node.js version is 18.0.0 or higher
Authentication Errors
Problem: API calls fail with authentication errors.
Solution:
- Verify your API token is correct and not expired
- Check that the token has the necessary permissions
- Ensure the API base URL is correct
Tool Execution Failures
Problem: Tools return errors or unexpected results.
Solution:
- Check the tool parameters match the expected schema
- Verify the API endpoint exists and is accessible
- Check server logs for detailed error information
Connection Issues
Problem: Cannot connect to Simplified API.
Solution:
- Check your internet connection
- Verify the API base URL is accessible
- Check if there are any firewall restrictions
- Use the health check tool to diagnose connectivity
Workflow Tool Issues
Problem: Workflow tools are not appearing in the tools list.
Solution:
- Verify
WORKFLOWS_ENABLED=true
is set in your environment - Check that the
workflows-list-tool
is available and responding - Verify workflow definitions match the expected schema
- Check server logs for workflow discovery errors
Problem: Workflow execution times out or fails.
Solution:
- Increase
WORKFLOW_EXECUTION_TIMEOUT
for longer-running workflows - Check workflow status using the
workflow-status-check
tool - Verify workflow parameters match the expected schema
- Check if the workflow execution system is available
Problem: Too many concurrent workflow executions causing errors.
Solution:
- Reduce
WORKFLOW_MAX_CONCURRENT_EXECUTIONS
to limit resource usage - Implement workflow queuing in your application
- Monitor system resources during peak usage
Problem: Workflow discovery is too frequent and causing API rate limits.
Solution:
- Increase
WORKFLOW_DISCOVERY_INTERVAL
to reduce API calls - Set to 0 to disable automatic discovery and use manual refresh
- Implement workflow caching in your application
Problem: Only some workflows are being discovered.
Solution:
- Check
WORKFLOW_FILTER_PATTERNS
configuration - Verify workflow names match your filter patterns
- Remove filters to see all available workflows
Debug Mode
Enable debug logging for detailed troubleshooting:
Health Check
Use the built-in health check tool to verify server status:
Workflow Troubleshooting Guide
Workflow Discovery Issues
Symptom: No workflow tools appear in tools list despite WORKFLOWS_ENABLED=true
Diagnostic Steps:
- Enable debug logging:
LOG_LEVEL=debug
- Check server startup logs for workflow discovery messages
- Verify
workflows-list-tool
is available and responding
Common Causes & Solutions:
Symptom: Workflows discovered but tools not registered
Diagnostic Steps:
- Check for tool name conflicts in logs
- Verify workflow names are valid MCP tool names
- Look for schema validation errors
Solutions:
Workflow Execution Issues
Symptom: Workflow execution times out
Diagnostic Steps:
- Check workflow execution logs
- Verify workflow is actually running
- Monitor workflow status manually
Solutions:
Symptom: Workflow execution fails immediately
Diagnostic Steps:
- Validate input parameters against workflow schema
- Check workflow system availability
- Verify API credentials and permissions
Solutions:
Performance Issues
Symptom: Server becomes slow or unresponsive
Diagnostic Steps:
- Check concurrent execution count
- Monitor memory and CPU usage
- Review workflow discovery frequency
Solutions:
Symptom: Excessive API calls causing rate limiting
Solutions:
Configuration Issues
Symptom: Server fails to start with workflow configuration errors
Common Errors & Solutions:
Integration Issues
Symptom: Workflows work in testing but fail in production
Diagnostic Checklist:
- Environment variable differences
- Network connectivity and firewall rules
- API endpoint availability
- Resource limits and timeouts
Production Configuration Review:
Debug Commands
Enable Maximum Debugging:
Test Workflow Discovery:
Test Workflow Execution:
Getting Help
- Check the logs: Enable debug logging to see detailed error information
- Verify configuration: Ensure all required environment variables are set
- Test connectivity: Use the health check and API status tools
- Check API documentation: Verify endpoint paths and parameters
- Test workflow tools: Start with simple workflows before complex ones
- Monitor resources: Check memory and CPU usage during workflow execution
- Report issues: Create an issue on the GitHub repository with logs and configuration details
API Reference
Server Configuration
The server accepts the following configuration options:
Tool Response Format
All tools return responses in the following format:
Success Response
Error Response
Contributing
We welcome contributions! Please see our Contributing Guide for details.
Development Setup
- Fork the repository
- Clone your fork:
git clone https://github.com/your-username/simplified-mcp-server.git
- Install dependencies:
npm install
- Create a feature branch:
git checkout -b feature/your-feature
- Make your changes and add tests
- Run tests:
npm test
- Build the project:
npm run build
- Commit your changes:
git commit -m "Add your feature"
- Push to your fork:
git push origin feature/your-feature
- Create a Pull Request
License
This project is licensed under the MIT License - see the LICENSE file for details.
Support
- API Documentation: API Docs
- Documentation: GitHub Wiki
- Issues: GitHub Issues
- Discussions: GitHub Discussions
This server cannot be installed
remote-capable server
The server can be hosted and run remotely because it primarily relies on remote services or has no dependency on the local environment.
A Model Context Protocol server that enables LLMs like Claude and Cursor to manage social media accounts and create posts across multiple platforms (including Facebook, Instagram, Twitter, LinkedIn, TikTok) through Simplified's API.
Related MCP Servers
- -securityFlicense-qualityA Model Context Protocol server that enables seamless interaction with LinkedIn for job applications, profile retrieval, feed browsing, and resume analysis through natural language commands.Last updated -22
- AsecurityAlicenseAqualityA Model Context Protocol server that enables users to manage translations for their applications through SimpleLocalize's localization platform via natural language prompts in Cursor.Last updated -23MIT License
- AsecurityAlicenseAqualityA Model Context Protocol server that loads multiple OpenAPI specifications and exposes them to LLM-powered IDE integrations, enabling AI to understand and work with your APIs directly in development tools like Cursor.Last updated -77860MIT License
- -securityFlicense-qualityA comprehensive Model Context Protocol server that enables AI assistants to interact with LinkedIn APIs for profile management, content creation, networking, messaging, and analytics.Last updated -1