Timeline

Provides local management of scheduled social media posts and campaigns via MCP with track-based organization.

javascript

0

GitHub Stars

javascript

Language

7 months ago

First Indexed

3 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "derekalia-timeline-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "timeline-mcp"
      ],
      "env": {
        "POSTY_WORKSPACE": "YOUR_WORKSPACE_PATH"
      }
    }
  }
}

Timeline MCP is a local server that lets your AI assistants manage a content calendar by scheduling posts across multiple platforms. It stores data locally in a workspace, organizes campaigns into tracks, and automates the flow from prompts to published posts. This makes it easy to coordinate multi-platform campaigns without leaving your environment.

How to use

You interact with Timeline MCP through an MCP client. Start by configuring a local server that your AI assistant can reach, then tell your assistant what you want to schedule. You can create campaigns, organize them into tracks, add posts with prompts and timing, and monitor or adjust scheduled events as needed. All data stays in your local workspace so you retain full control over your content calendar.

How to install

Prerequisites: Node.js 18+ and a Posty workspace with an SQLite database.

Prepare your MCP config snippet. Use the following to enable Timeline MCP in your MCP settings. This config tells the client to run Timeline MCP locally using npx and to provide the workspace path via an environment variable.

{
  "mcpServers": {
    "timeline": {
      "command": "npx",
      "args": ["-y", "timeline-mcp"],
      "env": {
        "POSTY_WORKSPACE": "/path/to/your/workspace"
      }
    }
  },
  "envVars": []
}

Additional setup steps

Create or choose a workspace directory for your Posty SQLite database and ensure the path is accessible from your environment.
If you are using a client, ensure it can read the configured POSTY_WORKSPACE environment variable. Replace the placeholder path with the actual path to your workspace.

Notes on running

Start the MCP client after saving your config. The Timeline MCP server will be invoked by the client using the provided command and arguments.
The server stores generated media and event data under your workspace in a tracks folder for each track and event, including an info.json with event metadata.

What you can do with Timeline MCP

Track management lets you list, add, and remove content tracks to organize campaigns.

Scheduled events allow you to add posts with prompts, timing, and platform targets; you can list, update, or remove events as your plan evolves.

Supported platforms include X (Twitter), Reddit (with subreddit targeting), LinkedIn, Instagram, TikTok, and YouTube.

Examples

Ask your AI assistant to schedule a campaign. For instance: create a product launch track, generate five teaser posts for X, and schedule one post per day at 10 AM across the campaign duration.

Available tools

list_tracks

List all content tracks so you can see existing campaigns and organize your calendar.

add_track

Create a new track to group related posts and campaigns.

remove_track

Delete a track and all its associated events.

add_event

Schedule a new post with prompts, timing, and target platform.

list_events

Display scheduled posts with filters for track, status, platform, or date range.

update_event

Modify details of a scheduled post before publishing.

remove_event

Delete a scheduled post from the calendar.