Social Listening MCP Server

What is Social Listening MCP Server?

A Model Context Protocol (MCP) server that provides social listening capabilities through Syften's API. It enables AI-powered analysis of social mentions, with support for real-time notifications via webhooks.

How to use Social Listening MCP Server?

Install Node.js v16+, clone the repo, run npm install and npm run build. Configure your Syften API key as an environment variable, then add the server to your Claude Desktop or VSCode Claude extension configuration. Use the provided tools (e.g., configure_ai_filter, setup_webhook, analyze_trends) via natural language prompts in Claude.

Key features of Social Listening MCP Server

• Real-time social mention monitoring
• AI-powered content categorization
• Webhook notifications for important mentions
• Historical data backfilling
• Trend analysis and reporting
• Natural language query support

Use cases of Social Listening MCP Server

• Configure AI filtering to detect specific mention categories (e.g., bug reports, feature requests)
• Set up webhook notifications for important social mentions
• Analyze trends of mentions over a date range
• Retrieve high-confidence filtered mentions for review
• Query social listening data using natural language prompts

FAQ from Social Listening MCP Server

What prerequisites are needed?

Node.js v16 or later, a Syften account with API access, and either the Claude Desktop app or VSCode with the Claude extension.

How do I configure the API key?

Generate an API key from your Syften account (Settings > API Access) and set it as the SYFTEN_API_KEY environment variable in the MCP server configuration JSON.

What data does the server backfill or sync?

It can backfill mentions for a specific month (backfill_month) and sync new mentions since the last update (sync_latest). Historical data is stored locally.

How does webhook integration work?

You can configure a webhook endpoint via setup_webhook. The server sends JSON notifications with mention URL, AI score, categories, and a timestamp. Requests include a X-Webhook-Secret header.

What transports or authentication does the server use?

The server uses the MCP stdio transport (run as a subprocess). Authentication is handled via a Syften API key set in the environment; no other transports or auth methods are documented.