Automate Launch Posts with the Amp Coding Agent

You can have Amp write and schedule your launch posts in the same thread where it ships the code: add the PostAxis MCP server to amp.mcpServers, sign in once, and Amp can read your diff or changelog, draft a version per network and put it on your PostAxis calendar. This guide is for developers and small product teams who already use Amp and want announcements to stop being the step that gets skipped.

The setup takes about two minutes. The rest of this post is the part that matters: prompts that work, what Amp does behind each one, and how to keep it from posting something you did not mean to.

What you can automate with Amp

Amp already knows what changed, because it just changed it. That makes it a good fit for anything that starts from the code:

• Release announcements written from CHANGELOG.md or the commits since the last tag, scheduled for a time you pick.
• Feature posts from a branch or PR, so the person who built it is not also the person who has to write the tweet.
• A weekly "what's new" digest for Telegram or LinkedIn, summarised from the week's merged work.
• Queue checks that list what is scheduled this week and fix posts that would break a network's rules.
• Drafts for review when you want Amp to do the writing and a human to press the button.

What you need

• A PostAxis account. Every plan starts with a 7-day free trial and includes MCP access with OAuth sign-in.
• At least one social account connected under Accounts in PostAxis (Instagram, TikTok, YouTube, X, LinkedIn, Facebook Pages, Threads or Telegram channels).
• Amp, either the editor extension or the CLI. Both read the same amp.mcpServers setting.
• Optional: the PostAxis API add-on, only if Amp cannot complete the browser sign-in and you need to fall back to an API key.

How to connect Amp to PostAxis (step by step)

1. Create your PostAxis account. Sign up at app.postaxis.io. The trial includes MCP access, so you do not need to pay before trying this.

2. Connect your social accounts. Open Accounts in PostAxis and connect the networks you want Amp to post to. Amp can only post to accounts connected here, and it never sees your social media passwords.

3. Open your Amp settings. In VS Code, open your user settings.json. For the CLI, edit ~/.config/amp/settings.json.

4. Add the PostAxis entry. Paste the block below. If amp.mcpServers already exists, add only the "postaxis" entry inside it.

{
  "amp.mcpServers": {
    "postaxis": {
      "url": "https://postaxis.io/api/mcp"
    }
  }
}

5. Sign in. The first time Amp uses the server, a PostAxis page opens in your browser. Log in and approve access. That is OAuth: Amp gets a token scoped to PostAxis, not your password.

6. Check it works. Start a new thread and ask:

Which PostAxis accounts can you post to?

Amp should call list_accounts and answer with your connected accounts by network. If it lists them, you are done. If it says there are none, go back to step 2.

If Amp never opens the sign-in page, you can use an API key instead (it needs the API add-on). Create one under Settings → API keys and add a header to the same entry:

{
  "amp.mcpServers": {
    "postaxis": {
      "url": "https://postaxis.io/api/mcp",
      "headers": { "Authorization": "Bearer YOUR_API_KEY" }
    }
  }
}

Your user settings.json lives outside the repo, which is where a key belongs. Never put it in a project-level file you commit.

4 workflows you can copy

Turn a release into posts

Use this right after you tag a release. Amp reads the changelog it may have just written and turns it into posts that suit each network.

Read CHANGELOG.md and find the entry for the latest version. Write an X post
(one sentence on the headline change, no hashtags) and a LinkedIn post (three
short paragraphs: what changed, who it helps, where to read more). Schedule both
for 17:00 Europe/London today. Show me both texts before you save anything.

What Amp does: reads the file, calls list_accounts to find your X and LinkedIn accounts, calls get_platform_rules to check the caption limits, shows you the drafts, then calls create_post once with a caption per account. One post, two versions, one scheduled time. PostAxis checks each version against its network's rules before it is saved.

Announce what you merged

When a feature lands mid-week and deserves its own moment, ask from the branch itself.

Summarise the feature in this branch for people who use the product, not for
developers. Write a short X post and a Threads post (Threads can be a little
more relaxed). Schedule both for tomorrow at 10:00 America/New_York.

What Amp does: reads the diff and commit messages, writes in user terms, then list_accounts → create_post with per-account captions. If you have a screenshot hosted somewhere public, add "attach the screenshot at https://…" and Amp will call upload_media_from_url first and attach it. PostAxis does not create images, so the screenshot has to exist already.

Plan a launch week in one go

For a bigger launch you want several posts spread over days, not one. This is where create_posts_bulk and its dry run earn their keep.

We launch the new API on Tuesday. Using docs/launch.md, plan five posts:
Monday teaser on X, Tuesday 09:00 announcement on X and LinkedIn, Tuesday 15:00
Telegram post with the full details, Wednesday 11:00 LinkedIn post with a code
example, Thursday 10:00 X post answering the most likely question.
All times Europe/Berlin. Validate the whole plan first and show me the result.

What Amp does: builds the plan and calls create_posts_bulk with validate_only=true. That checks every post against every network's rules and saves nothing. You see any problems (a LinkedIn post that runs long, a Monday post with no time) before a single post exists. When you reply "looks good, save it", Amp calls create_posts_bulk again without the flag. A bulk call takes up to 50 posts, and it cannot publish immediately, so everything in it is scheduled or saved as a draft.

Fix what won't publish

Before a big week, ask Amp to audit the queue.

List my scheduled posts for this week. Check each one against the current
platform rules and tell me which would fail. Fix the captions that are too long,
but ask before changing anything else.

What Amp does: list_posts for the date range, get_platform_rules for the networks involved, get_post on anything suspicious, then update_post for the fixes you allowed. Updates only work before a post goes out, which is exactly when you want them.

Network limits Amp works within

These come straight from PostAxis's rules for each network. Amp can fetch them at any time with get_platform_rules.

Video must be MP4 or MOV, 3 to 300 seconds, in 16:9, 9:16, 4:3, 3:4 or 1:1, and a post cannot mix images and video.

PostAxis rejects a post that breaks these rules before it is saved, and the error says what to change. For a coding agent that is useful feedback: Amp reads the error, shortens the caption or drops the extra image, and tries again, the same way it would react to a failing test.

Tips for better posts

• Put your voice in AGENTS.md. Amp reads an AGENTS.md file in your repo for project guidance. Add a short "Social posts" section: who the audience is, words you never use, whether you use emoji, how you link to the changelog. Every announcement then starts from the same rules.
• Validate first. For anything with more than one or two posts, ask for validate_only before saving. It costs nothing and saves a round of cleanup in the calendar.
• Say the timezone every time. "17:00" means nothing to a server. "17:00 Europe/London" does. Without one, the agent uses whatever timezone it was told earlier, or UTC.
• Ask for drafts when the stakes are high. "Save these as drafts" puts them under Drafts in PostAxis, where someone can read and schedule them from the calendar.
• Write for users, not reviewers. Commit messages are written for the team. Tell Amp to describe the change in terms of what a user can now do, or the post will read like a diff.
• Keep posting in its own thread. If a coding thread is long, start a fresh one for the announcement and point Amp at the changelog. Less context, cleaner posts.

Troubleshooting

Amp doesn't open a sign-in page. Use an API key header instead, as shown above. Keys are created under Settings → API keys and need the API add-on.

Amp says no accounts are connected. Connect at least one account under Accounts in PostAxis. If you have several workspaces, name the one you mean: "use my Acme workspace".

401 Unauthorized, or "sign in again". The sign-in expired or was revoked. Trigger the sign-in again from Amp. With an API key, check it is still active under Settings → API keys.

A post was rejected before saving. PostAxis checked the network rules and something did not fit: caption length, image count, video length or format. Ask Amp to read the error and fix it.

Posts landed at the wrong time. Add the timezone to the request, for example "10:00 America/New_York", and ask Amp to update the scheduled posts with update_post.

FAQ

Can Amp post to social media automatically?

Yes, once PostAxis is added to amp.mcpServers. Amp can draft, schedule or publish posts to any account you connected in PostAxis, including X, LinkedIn, Threads, Telegram, Instagram, TikTok, YouTube Shorts and Facebook Pages.

Does it work in the Amp CLI?

Yes. The CLI reads the same amp.mcpServers setting from ~/.config/amp/settings.json, so the setup is identical.

Does Amp write a different version for each network?

It can, and it should. Name the networks in one request and Amp sends one post with a caption per account, so X gets a short line and LinkedIn gets a longer read. PostAxis rejects any version that breaks that network's limits before saving.

Is it free?

MCP access with OAuth is included in every PostAxis plan, and every plan starts with a 7-day free trial. You only need the API add-on if you connect with an API key instead of signing in.

Does Amp see my social media passwords?

No. You connect social accounts inside PostAxis, and Amp only gets access to PostAxis through the sign-in you approve. You can revoke it any time under Settings → API keys, in the Connected agents list.

How do I stop Amp from posting?

Revoke it under Settings → API keys → Connected agents, or revoke its API key if you used one. Access stops immediately. Anything already scheduled stays in your calendar, where you can edit or delete it.

Amp is at its best when the announcement is part of finishing the work, not a chore for later. The Amp agent page has the setup in short form, the PostAxis MCP reference lists every tool, and the complete guide to AI agents for social media compares Amp with other agents. If you also use other coding agents, see how the same flow works in Claude Code and OpenCode. Ready to try it? Start your free trial.