Companies that use MCP

Source: Analysis of Linkedin bios of 1,014 companies that use MCP

I analyzed these 100 companies and found that MCP users are predominantly software and technology companies building developer tools, SaaS platforms, and AI-powered products. Many are creating infrastructure for other businesses: analytics platforms, workflow automation tools, testing frameworks, and data management systems. There's a strong representation of companies serving specific verticals like healthcare, e-commerce, real estate, and financial services with specialized software solutions.

These are primarily growth-stage companies. The employee counts cluster heavily in the 11-50 and 51-200 ranges, suggesting companies past the initial startup phase but still scaling. Many have raised seed or Series A funding, typically in the $2M to $20M range. Even the larger enterprises like Meta or SumUp represent the innovative, tech-forward end of their sectors. The smaller companies without funding data often describe ambitious missions that suggest they're building for scale.

A salesperson should understand that MCP's typical customer is a technical company in growth mode, likely with 10-200 employees, building products for other businesses. They value developer experience, speed of implementation, and reducing complexity. They're probably already using modern development practices and are looking for tools that integrate cleanly into existing workflows without adding friction.

Source: Analysis of 100 job postings that mention MCP

My analysis shows that MCP purchasing decisions are driven by technical leadership, with Directors of Software Engineering (12%) and Directors of Product Management (10%) leading the charge. These leaders are focused on building what one posting calls "AI-first experiences" and creating platforms that deliver "on-demand, least privileged access to infrastructure." They're investing in teams that can bridge traditional software development with emerging AI capabilities, particularly around agentic systems and generative AI integration.

The day-to-day users are predominantly Machine Learning Engineers (13%), Backend Engineers (11%), and AI Engineers (9%) who are tasked with connecting AI agents to enterprise systems. These practitioners are building what multiple postings describe as "autonomous orchestration tools" and "AI-powered tools used by game, art, marketing, and live ops teams." They're creating MCP servers, managing authentication systems, and integrating AI capabilities into existing workflows to boost developer productivity across their organizations.

The common thread across these roles is the challenge of making AI adoption safe and scalable. Companies repeatedly mention needing "security, observability, and control" for AI systems and the ability to "safely connect agents to their systems." One posting captures this perfectly: "enterprises can't adopt it safely without security, observability, and control." Another emphasizes building solutions with "consent-driven AI at the center" while ensuring systems remain "resilient, scalable, and compliant." These organizations are racing to operationalize AI while managing risk.

Source: Analysis of tech stacks from 1,014 companies that use MCP

I noticed that companies using MCP tend to be B2B SaaS businesses with a strong emphasis on both partner-driven growth and operational transparency. The presence of Partnerstack and HubSpot App Marketplace signals that these companies are building ecosystem plays, likely offering integrations or partner programs as a core distribution strategy. Meanwhile, tools like StatusPage and Incident.io reveal an obsession with reliability and trust, which makes sense for companies whose reputation depends on uptime and clear communication during outages.

The pairing of Golinks with StatusPage and Incident.io is particularly telling. Golinks suggests these are fast-growing companies where internal knowledge sharing and quick access to resources matter. When you combine that with incident management tools, you see teams that need to move quickly during critical moments and have built internal systems to support that speed. The ZipHQ correlation adds another layer, it's a procurement tool that appears in companies managing complex vendor relationships, which aligns with businesses that have reached a scale where tooling sprawl becomes a real problem.

My analysis shows these are likely growth-stage B2B companies, probably Series A through C, that have moved beyond pure product-led growth into a hybrid motion. They're building partner channels while maintaining strong direct sales efforts, hence the HubSpot App Marketplace presence. The incident management stack suggests they serve other businesses who depend on their reliability, possibly infrastructure or developer tools companies. They're operationally mature enough to invest in internal efficiency tools like Golinks but still growing fast enough that partnership leverage matters significantly.

A salesperson approaching MCP's typical customer should understand they're talking to operationally sophisticated teams who value reliability, transparency, and efficiency. These buyers likely have experience with developer tools, care deeply about their own customer experience during incidents, and are actively thinking about ecosystem growth strategies rather than just direct sales.