Pipedream MCP is a hosted or self-hosted server that centralizes discovery and calls to thousands of APIs and prebuilt tools through a single interface. It manages OAuth and credentials so LLM-driven apps can perform actions on user accounts without exposing raw credentials to the model. Key scale and setup: MCP provides access to thousands of APIs and tools (Pipedream's developers pages and docs mention ~3,000+ apps and 10,000+ prebuilt tools; product announcements reference ~2,500+ MCP servers). You can use a hosted endpoint (remote.mcp.pipedream.net) or self-host your own MCP server. Developer workflow includes signing up for Pipedream, creating a project, obtaining OAuth credentials, and configuring environment variables (PIPEDREAM_CLIENT_ID, PIPEDREAM_CLIENT_SECRET, PIPEDREAM_PROJECT_ID, PIPEDREAM_ENVIRONMENT set to development). The Connect API + frontend SDK show a Connect Link for end users; tool discovery is registry-based with per-app discovery pages. Security emphasizes encrypted, isolated credentials that are revocable and not exposed to models, with enterprise security features documented separately. Pricing includes a free tier plus subscription plans with credits consumed by actions and tool calls; exact rates are in docs and the account dashboard. Next steps include evaluating on the Free plan, planning production by mapping usage to credits, and considering self-hosting for compliance or isolated infrastructure.