automate-idea-to-social

This MCP server exposes the automate-idea-to-social automation suite through the Model Context Protocol, enabling you to publish and manage content across multiple social platforms from a unified interface. It wraps the underlying automate-idea-to-social tooling inside an MCP-compatible endpoint, allowing you to discover available agents (YouTube, Twitter, Facebook, Instagram, TikTok, Reddit, Blog, Translation, etc.), create automation tasks, monitor their progress, and retrieve results. You can trigger actions like video uploads, social posts with media, metadata management, and multi-language content flows via standardized MCP commands. The server is designed to run inside Docker and communicates over standard I/O with clients or IDEs that support MCP.

To use it, configure your MCP client or VS Code integration with the provided JSON snippet. The key is to map the MCP server under the automations namespace and provide any environment-driven configuration your agents require (for example, credentials or account-specific settings). The Docker-based setup runs the container with access to Docker on the host and passes necessary environment variables (such as APP_PROFILES and USER_HOME) to align with the underlying automation framework. Depending on the agents you intend to use, you may supply additional environment variables (for instance, Instagram credentials) as part of the args section.

Once configured, you can list agents, inspect their configurations, create automation tasks, and poll task status. The server supports asynchronous task execution with proper error handling, making long-running automation flows reliable within development and CI environments.

Prerequisites:

• Docker installed on the host
• Access to run containers (permissions to use docker.sock)

Installation steps:

1. Ensure Docker is installed and running on your machine. Verify by running: docker version

2. Prepare the MCP configuration by adding the following JSON to your MCP client or IDE configuration (adjust <MY_HOME_DIRECTORY> to your actual home path):

   { "mcpServers": { "automate-idea-to-social-mcp": { "command": "docker", "args": [ "run", "-u", "0", "-i", "--rm", "-v", "/var/run/docker.sock:/var/run/docker.sock", "-e", "APP_PROFILES=docker", "-e", "USER_HOME=<MY_HOME_DIRECTORY>", "poshjosh/aideas-mcp:0.0.1" ], "env": { } } } }

3. If you need to pass additional environment variables for specific agents (e.g., Instagram), extend the args section with the -e entries, for example:

   { "mcpServers": { "automate-idea-to-social-mcp": { "args": [ "-e", "INSTAGRAM_USER_EMAIL=<MY_INSTAGRAM_EMAIL>", "-e", "INSTAGRAM_USER_PASS=<MY_INSTAGRAM_PASSWORD>" ] } } }

4. Start your MCP client or IDE with the configured JSON. The server will launch the docker-based MCP runtime and expose the MCP endpoints through standard I/O as defined by the MCP protocol.

Tips and notes:

• The Docker container maps the host Docker socket, enabling the MCP server to run automation tasks inside Docker containers as needed by the underlying automate-idea-to-social system.
• Replace <MY_HOME_DIRECTORY> with your actual home path to ensure user-specific configurations resolve correctly inside the container.
• If you need to use specific platform credentials (e.g., Instagram), pass them as environment variables in the args section using -e flags.
• Review the environment.md documentation referenced in the README for a full list of available environment variables and their purposes.
• Ensure your host system has sufficient CPU/RAM for running multiple automation tasks in parallel.