BlackTwist MCP Server for CursorGive Cursor instant access to 12 tools to Create Post, Delete Post, Get Account Settings, and more
Cursor is an AI-first code editor built on VS Code that integrates LLM-powered coding assistance directly into the development workflow. Its Agent mode enables autonomous multi-step coding tasks, and MCP support lets agents access external data sources and APIs during code generation.
Ask AI about this App Connector for Cursor
The BlackTwist app connector for Cursor is a standout in the Marketing Automation category — giving your AI agent 12 tools to work with, ready to go from day one.
Vinkius delivers Streamable HTTP and SSE to any MCP client
Vinkius Desktop App
The modern way to manage MCP Servers — no config files, no terminal commands. Install BlackTwist and 3,400+ MCP Servers from a single visual interface.




{
"mcpServers": {
"blacktwist": {
"url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
}
}
}
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
About BlackTwist MCP Server
Connect your BlackTwist account to any AI agent and take full control of your social media presence on Threads and Bluesky through natural conversation.
Cursor's Agent mode turns BlackTwist into an in-editor superpower. Ask Cursor to generate code using live data from BlackTwist and it fetches, processes, and writes. all in a single agentic loop. 12 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
What you can do
- Post & Thread Orchestration — Draft and schedule high-fidelity posts or entire threads to your connected accounts programmatically in real-time
- Advanced Analytics Intelligence — Retrieve detailed engagement metrics, monitor posting consistency, and access high-fidelity daily performance recaps
- Provider Management Architecture — List and manage your connected social media providers and coordinate your digital voice across multiple profiles
- Automated Audience Growth — Access and monitor auto-plug templates and follow-up settings to perfectly coordinate your brand's growth strategy
- Infrastructure Monitoring — Access your current subscription status, post quotas, and account settings directly through your agent for instant reporting
The BlackTwist MCP Server exposes 12 tools through the Vinkius. Connect it to Cursor in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.
All 12 BlackTwist tools available for Cursor
When Cursor connects to BlackTwist through Vinkius, your AI agent gets direct access to every tool listed below — spanning social-scheduling, engagement-analytics, content-management, and more. Every call is secured with network, filesystem, subprocess, and code evaluation entitlements inside a sandboxed runtime. Beyond a simple connection, you get a full AI Gateway with real-time visibility into agent activity, enterprise governance, and optimized token usage.
You must specify the providerId and the content of the post(s). Create or schedule a new post
If it was scheduled, it will be cancelled. Delete a post
Get account settings
) for your social media accounts. Get engagement metrics
Get yesterday’s activity summary
Get details for a specific post
Get posting consistency data
Get current plan and quota
Get follow-up settings for a thread
Useful for getting providerIds. List connected social media accounts
List auto-plug/follow-up templates
List your posts and drafts
Connect BlackTwist to Cursor via MCP
Follow these steps to wire BlackTwist into Cursor. The entire setup takes under two minutes — your credentials stay safe behind the Vinkius.
Open MCP Settings
Cmd+Shift+P (macOS) or Ctrl+Shift+P (Windows/Linux) → search "MCP Settings"Add the server config
mcp.json file that opensSave the file
Start using BlackTwist
Why Use Cursor with the BlackTwist MCP Server
Cursor AI Code Editor provides unique advantages when paired with BlackTwist through the Model Context Protocol.
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
BlackTwist + Cursor Use Cases
Practical scenarios where Cursor combined with the BlackTwist MCP Server delivers measurable value.
Code generation with live data: ask Cursor to generate a security report module using live DNS and subdomain data fetched through MCP
Automated documentation: have Cursor query your API's tool schemas and generate TypeScript interfaces or OpenAPI specs automatically
Infrastructure-as-code: Cursor can fetch domain configurations and generate corresponding Terraform or CloudFormation templates
Test scaffolding: ask Cursor to pull real API responses via MCP and generate unit test fixtures from actual data
Example Prompts for BlackTwist in Cursor
Ready-to-use prompts you can give your Cursor agent to start working with BlackTwist immediately.
"List all social media accounts connected to BlackTwist."
"Schedule a Threads post 'Check out our new API!' for tomorrow at 2 PM."
"Show my engagement metrics and daily activity recap."
Troubleshooting BlackTwist MCP Server with Cursor
Common issues when connecting BlackTwist to Cursor through the Vinkius, and how to resolve them.
Tools not appearing in Cursor
Server shows as disconnected
BlackTwist + Cursor FAQ
Common questions about integrating BlackTwist MCP Server with Cursor.
What is Agent mode and why does it matter for MCP?
Where does Cursor store MCP configuration?
mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.