Get top stories: ranked story clusters with coverage links, discussion URLs, and optional filtering by tier or publisher
Get full story detail: all coverage links, social discussion posts, and TechSnif article text when available
Track the news cycle: story timelines, change feeds since a timestamp, and trending stories ranked by velocity
Search and read articles: TechSnif editorial articles by list, search, slug, or trending
Rank the sources: leaderboards of the publications and journalists driving coverage
Get tech events: upcoming tech industry conferences and events

Setup

Claude Desktop

Add this to your Claude Desktop config file:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "techsnif": {
      "command": "npx",
      "args": ["-y", "@techsnif/mcp-server"]
    }
  }
}

Cursor

Add this to .cursor/mcp.json in your project (or globally):

{
  "mcpServers": {
    "techsnif": {
      "command": "npx",
      "args": ["-y", "@techsnif/mcp-server"]
    }
  }
}

Other MCP clients

Run the server directly:

npx @techsnif/mcp-server

The server uses stdio transport, compatible with any MCP client.

Available tools

Tool	Description
`get_top_stories`	Top-ranked story clusters with coverage and discussion links. Filter by tier (1-3), publisher, discussion platform, topic, or since-date; sort by rank or newest. Default limit 20.
`get_story`	Full story cluster by slug: all coverage links, exact social post URLs, and TechSnif article text when available. Supports `platform`, `publisher`, and `brief`.
`search_stories`	Full-text search over story cluster headlines and excerpts, with optional publisher and platform filters. Default limit 10.
`get_story_timeline`	Ranking history of a story cluster: rank, tier, commentary count, and coverage count at each snapshot.
`get_changes`	New and updated story clusters since a timestamp (default: last 24 hours). Poll it to stay in sync with the feed. Default limit 50.
`get_trending_stories`	Story clusters gaining momentum, ranked by velocity with commentary and coverage deltas. Default window 24 hours, limit 20.
`get_tech_events`	Upcoming tech industry events with dates, locations, and URLs. Default limit 10.
`get_articles`	TechSnif editorial articles, filterable by category (AI, Startups, Venture, Robotics) or tag. Default limit 10.
`get_article`	Full TechSnif editorial article by slug, including the complete body text. Supports `brief`.
`search_articles`	Full-text search over TechSnif article titles and excerpts, ranked by relevance. Default limit 20.
`get_trending_articles`	Trending TechSnif articles from the last 48 hours. Default limit 5.
`get_leaderboard`	Source and author leaderboards: which publications and journalists drive the most coverage. Default window 30d, limit 50.

Tool names, descriptions, and defaults are generated from the shared agent contract, so the CLI, this server, and the hosted MCP at https://mcp.techsnif.com all expose the same surface.

Available resources

Resource	Description
`techsnif://categories`	List of all categories with descriptions
`techsnif://tags`	List of all tags with descriptions
`techsnif://platforms`	Active social discussion platforms with story counts

Example prompts

Once connected, try asking your AI assistant:

"What are the top tech stories right now on TechSnif?"
"Search TechSnif for stories about OpenAI"
"Show me the top story cluster with all its coverage links"
"How did that story trend over the last day? Show its timeline."
"What changed on TechSnif in the last 6 hours?"
"Which stories are gaining momentum right now?"
"Which outlets drove the most coverage this month?"
"What tech events are coming up?"

Configuration

Set TECHSNIF_API_URL to override the default API base URL (defaults to https://api.techsnif.com).

Set TECHSNIF_SITE_URL if you also want category links to point somewhere other than the main site (defaults to https://techsnif.com):

Requests include a non-identifying User-Agent header such as TechSnif-MCP/3.3.0 so TechSnif can distinguish MCP traffic from CLI and generic API traffic in aggregate Cloudflare analytics. The server does not send cookies, device IDs, or user identifiers.

{
  "mcpServers": {
    "techsnif": {
      "command": "npx",
      "args": ["-y", "@techsnif/mcp-server"],
      "env": {
        "TECHSNIF_API_URL": "http://localhost:4321",
        "TECHSNIF_SITE_URL": "http://localhost:4321"
      }
    }
  }
}