Skip to content

Add social-media/adaptlypost: AdaptlyPost social media manager - #64

Open
TarasShyn wants to merge 2 commits into
nanocoai:mainfrom
TarasShyn:add-adaptlypost-template
Open

TarasShyn wants to merge 2 commits into
nanocoai:mainfrom
TarasShyn:add-adaptlypost-template

Conversation

@TarasShyn

Copy link
Copy Markdown

What this template does

A social media manager agent for one brand. It drafts posts in the brand's voice, shows them, and after an explicit "yes" schedules or publishes them on Instagram, X, Bluesky, Mastodon, TikTok, Threads, LinkedIn, Facebook, Pinterest and YouTube through the user's own AdaptlyPost account. Then it reads each network's result separately, explains failures, retries once the cause is fixed, and answers performance questions from AdaptlyPost's analytics.

  • MCP: one streamable-http server, https://mcp.adaptlypost.com/mcp, hosted by AdaptlyPost. No stdio, no packages, nothing runs locally.
  • Skills: adaptlypost (operating logic, with references for media upload, analytics, credentials and onboarding) and welcome.
  • Task: weekly-review.md, Mondays 9 AM, read only, ships paused.
  • Hard guard: the key's workspace role. A Contributor key cannot schedule or publish, so AdaptlyPost itself refuses and the agent saves a draft. The README explains why a gateway approval rule can't do this for an MCP server: every tool call is the same POST /mcp.

Disclosure: I'm the founder of AdaptlyPost, the paid service this template connects to. The README says so up front; users bring their own key, and no credential, referral link or billing ships in the template.

Where it lives

social-media/adaptlypost/

Services and credentials

See Connect your AdaptlyPost key in the template README: API host mcp.adaptlypost.com, Authorization: Bearer injected by OneCLI, the role table in place of scopes (keys carry a workspace role, not scopes), and the plan note (every plan includes API access; 7-day trial).

Validation

  • node scripts/check-templates.mjs -> OK
  • node scripts/build-index.mjs then git diff --exit-code index.json -> clean
  • NanoClaw parseTemplate + prepareTemplateTasks (main @ d4ff64f4) on the folder -> empty skip report, 2 skills, 1 MCP server, 1 task with a valid cron
  • Unauthenticated POST https://mcp.adaptlypost.com/mcp -> 401 with WWW-Authenticate: Bearer resource_metadata=...; the server takes a plain API key as Authorization: Bearer, which is what OneCLI injects
  • Not stamped in a live NanoClaw install. The same hosted MCP server and tool set are in production use from Claude, Cursor, ChatGPT and our OpenClaw plugin; the NanoClaw-specific part is OneCLI injecting Authorization: Bearer for mcp.adaptlypost.com, the same path feat: add PostOnce social media template #61 exercised for a streamable-http server

Before you open this

  • node scripts/build-index.mjs run and the regenerated index.json committed
  • node scripts/check-templates.mjs passes
  • New template, so no version bump needed
  • No secrets anywhere in the diff
  • Read Acceptance and ownership and the full PR checklist

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant