Post to Twitter and LinkedIn from nanoclaw.
Connect VoiceMoat to nanoclaw and hand it your content: it plans, drafts and schedules Twitter and LinkedIn posts in your voice. Every post is checked for Style and Stance, and nothing goes out until you confirm.
Connects with a personal key
Set up in two minutes
Pro, Enterprise and the $5 Pro trial
[
how it connects
]
nanoclaw connects with a personal key.
nanoclaw runs agents in containers on your own machine. Give them VoiceMoat and they can draft, check and queue your posts on their own.
1
Create a key
In VoiceMoat, open Settings, then Assistants. Press Create key and pick nanoclaw. Tick publish if it should post. Copy it: it shows once.
2
Add the server
Run ncl groups config add-mcp-server with --name voicemoat and --url set to the address.
3
Add the key
Store the line that starts with Bearer in nanoclaw's credential vault as the Authorization header for app.voicemoat.com.
[
try it in nanoclaw
]
Hand nanoclaw the whole job.
Read my last 20 LinkedIn posts, find the three that did best and draft three more like them.
list_posts · get_voice_profile · get_post_ideas
Turn this blog post into a Twitter post and a LinkedIn post in my voice, and queue both for Tuesday at 9am.
improve_post · schedule_post
Plan my week: five posts across Twitter and LinkedIn, one per content pillar, with an opening line for each.
get_voice_insights · suggest_hooks
Does this draft read like me? Fix the line that's off before it goes out.
score_voice_match · improve_post
[
what voicemoat adds
]
nanoclaw does the work. VoiceMoat keeps it yours.
Your voice, not a generic one
nanoclaw drafts from your voice profile: your tone, your openings, the phrases you never use.
get_voice_profile
Checked before it posts
Every post is checked for Style and Stance, and the line that’s off is named.
score_voice_match
Asks twice, every time
Posting needs a preview and a second call with a one-time code. Change a word and the code is refused.
publish_post, asks twice
[
faq
]
Straight answers about connecting VoiceMoat to nanoclaw.
Why does nanoclaw need a key?
Containers can't open a sign-in window, so they send a fixed header instead. Keep the key in a secret or environment variable, not in a shared repo.
Does nanoclaw see my Twitter or LinkedIn login?
Which plan do I need?
Can nanoclaw post without me seeing it?
What if my key leaks?
[
other assistants
]
Same address,
every assistant.
Every assistant connects to https://app.voicemoat.com/api/mcp. Pick yours for its steps.
