Skip to content

v0.7.0 — x.com (Twitter) MCP integration

Choose a tag to compare

View all tags
@igun997 igun997 released this 02 Jul 08:02
v0.7.0
9045a2e
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Features

x.com (Twitter) MCP integration — full multi-account channel ported in-process from x-utils (cookie auth, no shell-out):

  • 13 core x_* tools: x_user, x_identify, x_post, x_delete, x_search, x_user_tweets, x_tweet, x_replies, x_followers, x_following, x_dm, plus account + watch management.
  • Account persistence + liveness (x_account_save/list/delete): accounts keyed (tenant_id, label); cookies write-only (never returned/logged); liveness cron.
  • Contact social handles: x_username / threads_username on Contact.
  • x_replies: top-level reply tweets per conversation thread, paginated.
  • Signed-webhook watches (x_watch_save/list/delete/events): per-watch webhook_url + rotatable webhook_secret + custom headers; HMAC-SHA256 X-Zetta-Signature; exported SignWebhook/VerifyWebhookSignature; poller cron.
  • x_identify: acting-account self summary.
  • threads_daily_summary MCP tool.

Fixes

  • Liveness + x_identify self-resolution: resolve the acting account's own profile via twid → UserByRestId instead of a stored screen_name + invalid from:me search fallback. Fixes functional accounts being wrongly marked dead and lets x_identify work from raw cookies.

Migrations

0011_x_accounts, 0012_contact_social_handles, 0013_x_watches.

Security

  • cookies / webhook_secret are sensitive: never logged/echoed; MCP outputs expose has_secret only.
  • Webhooks HMAC-signed; built-in headers override agent-supplied ones so security headers can't be clobbered.

Full changelog: v0.6.0...v0.7.0

Assets 2
Loading