Every LinkedIn action, as an endpoint.
Prospecting, connecting, messaging, sequencing and reply drafting, all callable by the agent you already run.
Screenshot
Claude connected over MCP, calling the action set
A native MCP server
Search and prospect, create and launch sequences, read threads, post drafts, move stages. It is first-party, so it moves when the product moves, and it speaks the same objects the interface does. Claude, Cursor, n8n or an orchestrator you wrote yourself.
A REST API for everything else
The same surface over HTTP: sending, drafting, enrollment, stages, sequences. Feature parity on every plan, the Sandbox included, so nothing you write against the Sandbox breaks when you connect a real sender.
One key per integration
Every agent gets its own scoped key rather than sharing one workspace token. When something goes out that you did not expect, the key says which agent did it. Revoking one integration leaves the others running.
An execution environment for LinkedIn actions
Sprootal does not host your agent and does not supply the intelligence. It takes the call, applies the guardrails, performs the action and reports back. The brain stays yours.