Appearance

Use Socifyr from Cursor ​

Edit ~/.cursor/mcp.json for all projects, or .cursor/mcp.json for one project. Point it at the hosted Socifyr endpoint and read the API key from an environment variable so the key never lands in a committed file.

How do I add Socifyr to Cursor? ​

json
{
  "mcpServers": {
    "socifyr": {
      "url": "https://api.socifyr.com/api/mcp",
      "headers": {
        "Authorization": "Bearer ${env:SOCIFYR_API_KEY}"
      }
    }
  }
}

Set SOCIFYR_API_KEY in your shell profile, reload Cursor, then enable socifyr under Settings, then MCP. Create the key in the dashboard under API Keys. It belongs to one workspace.

How do I run the local server instead? ​

json
{
  "mcpServers": {
    "socifyr": {
      "command": "npx",
      "args": ["-y", "@socifyr/mcp"],
      "env": {
        "SOCIFYR_API_KEY": "sk_...",
        "SOCIFYR_WORKSPACE_ID": "69fbbf978e770da397a59a5a"
      }
    }
  }
}

The local server needs both variables and exits with an error if either is missing. For a self-hosted API, add SOCIFYR_API_URL.

What can I ask Cursor to do? ​

Cursor's agent calls the same 20 tools:

  • "Post the changelog entry in CHANGELOG.md to LinkedIn and Bluesky." Cursor reads the file, calls list_connections, then post_text.
  • "Schedule these three release notes for 9am UTC on consecutive weekdays." Cursor calls schedule_posts.
  • "Check whether yesterday's post published." Cursor calls list_posts, then check_post_status.

See Example agent prompts for more.

How do I limit what the editor agent can post? ​

Use a separate key with a daily limit and required approval. Posts from that key are held for review. See Approvals and guardrails.

FAQ ​

Why does my agent not see the tools? ​

Check that the key is url for Cursor, then reload Cursor and confirm the server is enabled. Errors and fixes: MCP errors.

Can Cursor use the CLI instead? ​

Yes. Cursor can run socifyr post ... in a terminal. See CLI reference.

Next steps ​