Skip to content

MCP Server Landscape

Status: Active (growing) Project: Operations · General

What this is

The collection of Model Context Protocol (MCP) servers Sam has installed in Claude Desktop and other Claude clients. MCP servers expose tools (filesystem, databases, APIs) to Claude agents, which is how the firm wires Claude into Salesforce, Notion, GitHub, Google Ads, and other systems.

Known installed servers

  • Salesforce / Litify MCP bridge — exposes Clientell + sf CLI capabilities to Claude Desktop (see Salesforce / Litify AI Toolkit)
  • Notion MCP (https://mcp.notion.com/mcp) — reads/writes the SAIL Knowledge Base database; used by the notion-session-export skill in Cowork
  • Google Ads MCP write tools — custom-built write capabilities on top of a Google Ads MCP (negatives, ad copy, bid strategy)
  • Filesystem MCP servers for local project access

Recent setup activity

  • MCP server installs for Claude Desktop (Apr 13, 2026) — batch install of several MCP servers, plus environment configuration
  • Google Ads MCP Write Tools: Build, Auth Fix, Repo Reorganization (April 12) — built custom write tools on top of an existing MCP, fixed auth, reorganized the repo

Pipedream as a universal MCP

In April 2026 Sam set up a Pipedream OAuth client to act as a universal "connect everything" layer. Pipedream Connect lets one OAuth client proxy authenticated calls to 2,000+ services (Notion, Google, Slack, etc.). See docs/integrations/pipedream-connect-api.md for the full API reference.

Sources

See also