X (Twitter) integration for AI agents.
Let your AI agents work in X — read timelines, post updates, and monitor social context — through a routed, audited connection. Open Connector runs the OAuth, seals the token in an encrypted vault, and serves X (Twitter) tools to your agent over MCP or a typed API — credentials injected server-side, every call audited, nothing leaving your infrastructure. Open source (AGPL-3.0) and self-hostable.
Real X (Twitter) actions, managed and audited.
Your user connects X (Twitter) once; your agent can then read timelines, publish posts, and fetch social context — scoped to the OAuth permissions you grant and the tool allowlist you configure. Every action is least-privilege and written to a tamper-evident audit trail.
- 1
Your user grants X (Twitter) access once (OAuth) — the token lands in the vault.
- 2
Your agent calls a tool over MCP or the typed API; Open Connector injects the credential server-side.
- 3
Every routed call appends a hash-chained audit record — nothing leaves your infra.
X (Twitter) tool surface.
The following managed tool groups are exposed by this integration. Each item is surfaced as tool metadata so agents can discover safe actions and build reliable workflows.
- Post tools
- Create, publish, and update social posts with the scopes configured on the connected account.
- Timeline tools
- Read replies and mentions for agent-triggered response workflows.
- Profile tools
- Fetch user profile metadata and identity context to support identity-aware automations.
X (Twitter) integration, answered
- How do AI agents use X (Twitter) through Open Connector?
- Your user connects X once (OAuth). Open Connector stores the token in an encrypted vault and exposes X tools to your agent over MCP or a typed API. The agent calls a tool and Open Connector injects the credential server-side.
- Can I automate social workflows with this integration?
- Yes, after the user grants the required OAuth scopes. Open Connector keeps credentials in your infrastructure, audits each routed call, and routes actions by your allowlist.
- Where do X OAuth tokens live?
- In your own infrastructure: encrypted token storage with server-side credential injection and no raw token exposure to the agent.
Give your agents X (Twitter) — keep the keys.
Open source, self-hostable, with X (Twitter) credentials that never leave your infrastructure. Run it from source today.