Claude MCP Integration

Connect Trigify to Claude using the Model Context Protocol

What is MCP?

The Model Context Protocol (MCP) is an open standard that enables AI assistants like Claude to interact with external tools and data sources. With Trigify’s MCP server, you can query and manage your social listening searches directly through Claude.

Use Cases

Sales Teams

“Show me all LinkedIn posts mentioning our competitors this week and summarize the key themes”

Product Managers

“Create a search for feature requests mentioning ‘dark mode’ and analyze the sentiment”

Marketing

“Get the latest results from my brand monitoring search and draft response ideas”

Developers

“List all my active searches and show me the API response format”

Setup Options

Trigify MCP works with Claude Desktop, Claude Web, and the Claude API.

Claude Desktop

Prerequisites

Claude Desktop uses OAuth authentication - just log in with your Trigify account. No API key needed!

Step 1: Configure Claude Desktop

Open your Claude Desktop configuration file.

macOS:

open ~/Library/Application\ Support/Claude/claude_desktop_config.json

Windows:

%APPDATA%\Claude\claude_desktop_config.json

If the file doesn’t exist, create it.

Add the Trigify MCP server configuration:

Example
{
  "mcpServers": {
    "trigify": {
      "url": "https://api.trigify.io/mcp"
    }
  }
}

No API key needed! OAuth uses the same login as the Trigify dashboard.

Step 2: Restart Claude Desktop

Quit Claude Desktop completely and reopen it.

Step 3: Authorize Access

When you first use a Trigify tool in Claude:

  1. You’ll be redirected to the Trigify login page

  2. Log in with your Trigify credentials (same as the dashboard)

  3. Authorize Claude to access your Trigify account

  4. You’ll be returned to Claude automatically

The Trigify tools are now available in your conversations!

Claude Web

Requires: Claude Pro, Max, Team, or Enterprise plan

Claude Web uses OAuth authentication - just log in with your Trigify account. No API key needed!

Step 1: Add Connector in Claude

  1. Go to Claude and open Settings

  2. Navigate to Connectors

  3. Click Add connector

  4. Enter the MCP server URL:

https://api.trigify.io/mcp

  1. Save the connector

Step 2: Authorize Access

When you first use a Trigify tool in Claude:

  1. You’ll be redirected to the Trigify login page

  2. Log in with your Trigify credentials (same as the dashboard)

  3. Authorize Claude to access your Trigify account

  4. You’ll be returned to Claude automatically

No API key needed! OAuth uses the same login as the Trigify dashboard.

Step 3: Start Using

The Trigify tools are now available in your Claude conversations. Try asking “List my Trigify searches”.

Claude API

Developers building with the Claude API can connect to Trigify’s MCP server programmatically.

API Request

Example
{
  "model": "claude-sonnet-4-5",
  "max_tokens": 1024,
  "messages": [
    {
      "role": "user",
      "content": "List my Trigify searches"
    }
  ],
  "mcp_servers": [
    {
      "type": "url",
      "url": "https://api.trigify.io/mcp",
      "name": "trigify",
      "authorization_token": "your-trigify-api-key"
    }
  ],
  "tools": [
    {
      "type": "mcp_toolset",
      "mcp_server_name": "trigify"
    }
  ]
}

Requires the beta header: anthropic-beta: mcp-client-2025-11-20

TypeScript Example

Example
import Anthropic from "@anthropic-ai/sdk";

const anthropic = new Anthropic();

const response = await anthropic.beta.messages.create({
  model: "claude-sonnet-4-5",
  max_tokens: 1024,
  messages: [{ role: "user", content: "List my Trigify searches" }],
  mcp_servers: [{
    type: "url",
    url: "https://api.trigify.io/mcp",
    name: "trigify",
    authorization_token: "your-trigify-api-key"
  }],
  tools: [{
    type: "mcp_toolset",
    mcp_server_name: "trigify"
  }],
  betas: ["mcp-client-2025-11-20"]
});

Available Tools

Once configured, Claude can use these tools:

Tool

Description

Credits

create_search

Create a keyword search, profile monitor, or podcast monitor

Yes

search_podcasts

Search for podcasts by name (use before creating podcast-episodes monitor)

No

list_searches

List all your searches and monitors

No

get_search

Get details of a specific search

No

get_search_results

Fetch results from a search

No

update_search

Update search configuration

No

delete_search

Delete a search

No

Supported Monitoring Types

Keyword-based (requires keywords):

  • linkedin-posts — LinkedIn posts matching keywords

  • reddit-posts — Reddit posts matching keywords

  • youtube-videos — YouTube videos matching keywords

  • podcast-keywords — Podcast episodes matching keywords

  • twitter-posts — Twitter/X posts matching keywords

Profile monitoring (requires profile_url):

  • linkedin-profile — Monitor a LinkedIn profile or company page

  • twitter-profile — Monitor a Twitter/X profile

  • youtube-channel — Monitor a YouTube channel

Podcast monitoring (requires podcast_id from search_podcasts):

  • podcast-episodes — Monitor a specific podcast for new episodes

​Example Prompts

Try asking Claude:

​Troubleshooting

Security

  • Claude Desktop & Web: Uses secure OAuth 2.1 flow with JWT tokens (24h expiry) - no API keys needed

  • Claude API: Your API key is transmitted securely over HTTPS

  • All modes: Requests go directly to Trigify’s API over HTTPS

  • Trigify never sees or stores your Claude conversations

  • You can revoke access at any time from the Trigify dashboard