Social Media MCP Server for Grok and Cursor

Ask Grok what's trending and it can tell you. Ask whether your last post on that trend worked, and it has nothing to go on. That answer sits in Fedica.

With Fedica connected, Grok works from the data behind your accounts:

• Engagement for any stretch of days: interactions, impressions, engagement rate, and top posts, set against the period before.
• Best times to post by weekday and hour, converted to your timezone.
• Follower, following, and post counts over time, so you can see new followers and unfollows for each period. The same history powers follower growth tracking.
• Who your followers are: follower demographics by language, timezone, gender, occupation, and age, plus account quality and activity scores.

Then ask Grok to draft the follow-up and schedule it. It's one conversation from "what worked?" to the next post in the queue.

The launch announcement usually gets written last, in a different app, after the release notes are done. With Fedica in Cursor, the agent that helped write the changelog can turn it into posts and schedule them while the details are still fresh.

• One request, several versions: a full write-up for LinkedIn, a short one for X, and a thread for Bluesky and Mastodon, each sent to the right account.
• Pick a date, time, and timezone, or add the posts to one of your content calendar Pipelines.
• Images and video go along with alt text.
• Ask what's in the queue to see every pending post in order. Release date moved? Replace any post that hasn't gone out.

The research reports in your Fedica account are readable too, once their status shows Complete. Ask about an analyze report to size up a competitor's audience, or a compare report to see how many followers two accounts share, the data behind common followers.

A follower quality audit sorts an audience into bots, low quality, normal, and influencer accounts. Keyword and hashtag search reports cover sample, full-archive, and count-only runs, with a sentiment filter when the search used one. You can name a report the way you remember it, like "the launch-week search," and skip the report ID.

Fedica is added to Grok as a custom connector:

1. Go to grok.com/connectors.
2. Click New Connector, then choose Custom.
3. Enter the server URL:

   https://mcp.fedica.com/mcp

4. Sign in to Fedica and approve access.

Start a new chat and ask Grok which Fedica accounts it can see. On a Grok Business or Enterprise team, an admin may need to set up the connector first.

Grok Bot has no settings file for MCP servers. You add Fedica by asking the bot:

1. Send this message, including the words "custom MCP server":

   Add a custom MCP server called fedica at https://mcp.fedica.com/mcp

2. Check that the name and URL the bot shows match, then click Add it.
3. On the connect card, click Authorize, sign in to Fedica in your browser, and approve access.
4. Type @ in the chat and attach fedica to your task.

Grok Bot runs on a cloud computer, not your laptop, and Fedica's server is hosted, so there's nothing to tunnel or install.

1. Open .cursor/mcp.json in your project, or ~/.cursor/mcp.json to use Fedica in every project, and add:

   {
     "mcpServers": {
       "fedica": {
         "url": "https://mcp.fedica.com/mcp",
         "auth": {
           "CLIENT_ID": "https://cursor.com/oauth/mcp-client.json",
           "scopes": ["read", "publish"]
         }
       }
     }
   }

2. Save the file. If you already have other servers in it, add the fedica entry inside the existing mcpServers block.
3. Open Cursor's settings, find fedica in the MCP list, and sign in to Fedica in your browser when prompted.

Ask the agent which Fedica accounts it can see to check the connection.