Social Media Data in Cursor IDE
Connect Cursor to CreatorCrawl and access live social media data while you code. Use the MCP integration to pull real API responses, test endpoints, and build integrations with AI assistance.
Key Features
- Access social media data directly from the Cursor AI chat
- Test API endpoints and see real responses while coding
- AI-assisted development with live social media data context
- Build and debug integrations without leaving your editor
- Works with Cursor Agent and Composer modes
Code Example
// Add to .cursor/mcp.json in your project root:
{
"mcpServers": {
"creatorcrawl": {
"url": "https://creatorcrawl.com/api/mcp",
"transport": "streamable-http",
"headers": {
"x-api-key": "your_api_key_here"
}
}
}
}Getting Started
Get your API key
Sign up at creatorcrawl.com and copy your API key from the dashboard. You get 250 free credits, no card required.
Create the MCP config file
Create a .cursor/mcp.json file in your project root (or configure it globally in Cursor settings under MCP).
Add the CreatorCrawl server
Add the creatorcrawl MCP server with the URL https://creatorcrawl.com/api/mcp and your API key in the headers.
Use social media data in Cursor
Open Cursor Agent or Composer and ask it to look up social media data. It will use the CreatorCrawl tools automatically.
Frequently Asked Questions
Does this work in Cursor Free?
MCP support is available in Cursor Pro and Business plans. You also need a CreatorCrawl API key with credits.
Can I use this in Composer mode?
Yes. Both Cursor Agent and Composer modes can access MCP tools. Ask the AI to pull social media data and it will call the CreatorCrawl API through MCP.
Where do I put the config file?
Create a .cursor/mcp.json file in your project root for project-level config, or add it to your global Cursor settings for access across all projects.
Can the AI write code that calls the API?
Yes. Cursor can both call the API through MCP for live data and generate code that calls the REST API directly. It can use real responses as reference when writing your integration code.