Over time, what has stood out more is StackOne's focus on being the connectivity layer for AI applications rather than just another integration platform. Its MCP server support makes it much easier to connect AI agents with enterprise systems in a secure and standardized way, reducing the complexity of building agentic workflows across multiple SaaS tools.

I also appreciate the breadth of supported connectors, the developer experience, and the speed at which new integrations can be deployed. As AI-driven automation becomes more important, StackOne provides the infrastructure needed to help agents interact reliably with business systems without requiring teams to build and maintain custom connectivity from scratch. Review collected by and hosted on G2.com.

As the platform evolves around AI and MCP, I'd like to see more reference architectures, production-ready examples, and best practices for building agentic workflows. Additional tooling for monitoring MCP connections, debugging AI interactions, and tracking integration health would make operating AI-powered applications even easier.

Expanding provider coverage and offering more advanced documentation for complex enterprise scenarios would also help teams adopt the platform more quickly. These are refinements rather than major issues, and addressing them would further strengthen an already solid developer platform. Review collected by and hosted on G2.com.

StackOne is the integration layer that makes our whole business development setup actually hang together. I've built a BD operator in Claude that scans for ICPs, researches them and drafts personalised outreach, and StackOne is what logs every single touchpoint straight into our CRM (Vincere). Contact creation, company lookups, record creation, sent emails, it's all captured automatically so the team always sees where an account is up to. One integration layer instead of wiring up each tool myself. Review collected by and hosted on G2.com.

Honestly very little. The platform gives you so much that the real work is on your side, deciding which connectors and workflows to build out first. A few of the things I want next, like timesheet and project logging, I'm still building into my own setup rather than them being switched on out of the box, so there's some design effort up front. That's more about my roadmap than a fault with the product, but worth flagging for anyone expecting it all to be plug-and-play on day one. Review collected by and hosted on G2.com.

We had nine systems connected within two weeks, including Okta, Jamf, Intune, Procurify, Expensify, and NetSuite. The org needs every agent limited to what the person asking is allowed to do, and StackOne’s per-connector, per-account permissions plus a full audit trail of every action gave us the confidence to connect everything. What’s stood out most has been how easy the team is to work with. Turnaround on getting things up and running has been exceptional where Claude had no native connector, StackOne built one quickly. They’ve been responsive, open to feedback, and willing to iterate on what we need. It’s been great working with them. Review collected by and hosted on G2.com.

I wish Claude could update permissions without needing to disconnect and reconnect all the time Review collected by and hosted on G2.com.

What I like best about StackOne is that it solves a real problem I was facing: connecting AI agents to all the systems they need to actually take action. The platform is easy to use and friendly, even for use cases involving multiple systems, and setup felt straightforward from day one. On top of that, the support and sales teams know the product in depth and are very responsive, which made it easy to apply it to my specific use cases quickly. Review collected by and hosted on G2.com.

So far, I haven't identified anything that would take away my confidence in the product. My experience has been limited to the initial use cases I am testing, so there may be more nuanced points to explore as we scale usage, but nothing so far has raised concerns. Review collected by and hosted on G2.com.

I view this from the perspective of a privacy and cybersecurity professional, so I start with the risk model. They made the right choice to move away from the "unified API" approach (which quickly hits its limits with LLMs) and instead expose each application's native semantics as controllable actions. Permissions remain the system's actual ones, and all actions are logged; execution remains deterministic alongside MCP, and by default, no data is retained. These are precisely the safeguards needed to meet the requirements of GDPR (Articles 5, 25, 32), ISO 27001, and ISO 42001. I also really liked the fact that prompt injection protection is built into the infrastructure rather than being an add-on component, and that relying on open standards like MCP and A2A minimizes vendor lock-in. In my experience, the support team is responsive and knowledgeable. Review collected by and hosted on G2.com.

It is still a young product. Certain aspects (particularly regarding testing and specific formalities that would be useful in highly regulated environments) are still maturing. Nothing has been a deal-breaker for me, and the team is moving in the right direction. Review collected by and hosted on G2.com.

I find StackOne to be easy to use and intuitive. It was very easy for me to connect an MCP server to my Claude desktop, which has significantly increased our efficiency. The product enables the 'company brain' to communicate with all different parts of the business, making our operations seamless. I appreciate its incredibly intuitive interface, which works well without requiring extensive training. Review collected by and hosted on G2.com.

Nothing Review collected by and hosted on G2.com.

Using Stackone to support our agents and keep our internal operations running smoothly is super easy and efficient. Review collected by and hosted on G2.com.

It’s super easy to use I don’t actually have negative feedback Review collected by and hosted on G2.com.

* The unified API saves us from building and maintaining dozens of brittle integrations

* Excellent coverage and fast connector delivery—new vendors get added quickly.

* Support is responsive and knowledgeable; they don’t hand-wave.

* Great observability—logs, retries, and error surfaces make debugging painless. Review collected by and hosted on G2.com.

* Great API, but the SDK isn’t there yet: inconsistent naming, limited helpers, and outdated examples increase dev time

* Would love field-level selection and a clear ‘field matrix’ across ATSs so we know exactly what comes back. Review collected by and hosted on G2.com.

It's hard to think of any upside if I'm honest. Review collected by and hosted on G2.com.

You cannot market this feature because none of the integrations are ready to be used. As the customer, you are expected to QA every integration yourself.

Also: Their marketing website lists integrations that are not available.

Also: Many of their integrations do not contain data (such as Pay) which was flagged by us during the sales process as important.

Also: They only fix integrations once you ask them to - which there is no SLA for.

Also: You get very little or no testing credentials to any HRIS providers unless you're paying them upwards of £70,000 a year.

This renders the integration worthless, as it cannot be relied on to provide our clients with a good experience.

I have quotes from StackOne to evidence every point that is raised above. Review collected by and hosted on G2.com.

The stack's configuration and straightforward navigation have really impressed me. Review collected by and hosted on G2.com.

So far, I have nothing to complain about or dislike. Review collected by and hosted on G2.com.