Skip to content

Blog batch 2026-08-19: Perplexity MCP, AWS vs Terraform MCP, PostHog MCP - #146

Open
gusmar2017 wants to merge 1 commit into
mainfrom
blog/batch-2026-08-19
Open

Blog batch 2026-08-19: Perplexity MCP, AWS vs Terraform MCP, PostHog MCP#146
gusmar2017 wants to merge 1 commit into
mainfrom
blog/batch-2026-08-19

Conversation

@gusmar2017

Copy link
Copy Markdown
Contributor

Summary

  • Perplexity MCP Server (Gus) — the 4-tool breakdown (perplexity_search/ask/research/reason), how each maps to Perplexity's Agent API effort presets, and CTO Denis Yarats's public March 2026 comments about Perplexity moving internal/enterprise systems away from MCP even while its public server remains "the recommended" path. focusKeyword: perplexity mcp server. topic_source: new_topic.
  • AWS MCP Server vs Terraform MCP Server (Adam) — clarifies the AWS-servers-do-live-resources vs Terraform-server-does-plan/apply split, anchored on the verified fact that AWS deprecated its own awslabs/terraform-mcp-server in favor of HashiCorp's official server. focusKeyword: aws mcp server vs terraform mcp server. topic_source: new_topic.
  • PostHog MCP Server (Adam) — covers the 3 tool surfaces (feature flags, session recordings, natural-language-to-SQL warehouse queries) and the repo's consolidation from a standalone posthog/mcp repo (archived) into the posthog/posthog monorepo. focusKeyword: posthog mcp server. topic_source: new_topic.

All 3 came from the existing queue (Topics 114 and 127, both previously held on cannibalization/overlap caution) plus new replenishment research — see the editorial calendar commit in mac-mini-agent for full topic selection and keyword research notes.

Sentinel validation log (Two-Agent Validation Loop)

Post Round 1 Round 2 Round 3 (final)
Perplexity MCP Server NEEDS_REVISION (38%, 4 flagged) NEEDS_REVISION (32%, 3 flagged) PASS (27%)
AWS vs Terraform MCP Servers NEEDS_REVISION (58%, 6 flagged) NEEDS_REVISION (38%, 3 flagged) PASS (38%)
PostHog MCP Server NEEDS_REVISION (52%, 4 flagged) PASS (20%) — (shipped Round 2)

All 3 posts reached PASS within the loop (2 at the final Round 3, 1 at Round 2) — none shipped at NEEDS_REVISION this batch.

Validation performed

  • gray-matter frontmatter parses cleanly for all 3 posts
  • Zero em dashes across all 3 posts
  • Banned-word blocklist scan clean
  • Word count 1,200-1,500 for all 3 (1,246 / 1,217 / 1,252)
  • FAQ frontmatter matches body FAQ content exactly for all 3
  • Cornerstone link (/blog/what-is-mcp) present in all 3
  • 2+ directory links (/servers/ or /categories/) present in all 3
  • Cluster sibling links present (search: 1 sibling linked; cloud: 3 siblings linked; analytics: 3 siblings linked)
  • No fabricated server slugs — Perplexity's and PostHog's official servers are not yet indexed in MCPFind's own directory, both posts disclose this explicitly and link to category pages instead

🤖 Generated with Claude Code

@vercel

vercel Bot commented Aug 19, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
mcp-find-web Ready Ready Preview Aug 19, 2026 9:02am

Request Review

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant