Newsletter Commerce Intelligence MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| extract_newsletter_products | Extract affiliate links, product recommendations, and sponsored mentions from newsletter content. Pass the newsletter body directly as HTML or plain text — does not fetch content from URLs. Supports Substack, Ghost, and Beehiiv HTML plus plain text. Returns product name, category, affiliate link URL, recommendation strength, and sponsor flag. Call this before analyze_newsletter_sponsors or track_product_trends — both tools reuse its cache. Use for monetization analysis, affiliate auditing, and cross-issue tracking. Example: newsletter_id='morning-brew-2026-03-12', category_filter=['saas','physical_goods']. |
| analyze_newsletter_sponsors | Identify sponsored sections in a newsletter and estimate advertising value: CPM, read-through rate, and sponsor-reader fit score. Returns each sponsor's name, placement type (dedicated section, inline, footer), estimated CPM based on industry benchmarks, and audience fit score. Revenue estimates are benchmark averages — not live ad-platform data. Use for advertising intelligence, sponsor acquisition research, and ad placement optimization. Use this tool for sponsor metrics only; for the full affiliate product and link list use extract_newsletter_products instead. Reuses cached extraction when newsletter_id matches a prior extract_newsletter_products call. Example: newsletter_id='tldr-2026-03-12' → returns [{sponsor:'Warp', placement:'dedicated_section', estimated_cpm:40, fit_score:0.85}]. |
| track_product_trends | Compare affiliate product mentions and brand frequency across multiple newsletter issues to detect rising, stable, and declining trends. Returns trend velocity, mention count per issue, and category breakdown. No AI call — computed from cached extraction data only. Use for affiliate marketing optimization, editorial product tracking, and sponsor category analysis. Requires prior extract_newsletter_products call for each newsletter_id — returns an error listing missing IDs if any are not in cache. Example: newsletter_ids=['issue-101','issue-102']. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/teamsincetoday/newsletter-commerce-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server