What is MCP in Styrar?
Model Context Protocol (MCP) lets AI assistants like Claude and Cursor call Styrar tools securely with your API key or OAuth consent.
MCP for AI
Connect Styrar to Claude, Cursor, and other AI assistants. Ask your AI to draft a post, check last week's analytics, or create a trackable link, and it handles the Styrar side for you.
Any AI tool that supports MCP can connect to Styrar, no custom plugins or special integrations needed.
Draft posts, look up link performance, browse your media, tell your AI what you need and it works directly inside your Styrar workspace.
Your AI sees your actual posts, links, accounts, and analytics, not generic examples. It knows your workspace because it connects to it directly.
Your AI inherits exactly the permissions you've set. It can only do what you've already allowed in your workspace, nothing more.
Connecting takes minutes. Point your AI assistant at Styrar and start delegating the work that fills up your tabs, post drafts, link lookups, analytics summaries, and more.
Enabling AI doesn't mean losing control. Styrar keeps AI access on the same permission rails as everything else, your approvals, your roles, your rules.
Draft posts, pull analytics, and manage links from the IDE via the MCP server and API key.
Ask your assistant to queue content or summarize performance without opening another tab.
Standardize repeatable social tasks through AI tools while RBAC keeps client workspaces separate.
Model Context Protocol (MCP) lets AI assistants like Claude and Cursor call Styrar tools securely with your API key or OAuth consent.
Any MCP-compatible client can connect. We document setup for Claude Desktop, Cursor, and other tools that support remote MCP over HTTP.
No. AI actions respect the same roles, capabilities, and approval flows as the dashboard.
Use a dashboard API key (Bearer) for HTTP MCP, or complete OAuth consent where your client requires it. See Settings → API Keys.
Connect Styrar to Claude, Cursor, or any AI assistant. Takes about two minutes.