Gus IT
Comparison · checked September 15, updated September 16, 2026

Claude, Luca Express and Dell Automation Platform: not one or the other.

A prospect asked us a fair question: what is the difference between Luca Express and just running Claude with an MCP (Model Context Protocol) server? The short version is that they do different jobs, and so does Dell's automation platform. The infrastructure practice we run puts each in its own lane, with engineers who can specify and test what gets built. Below: the roles, what is real today, what it costs, and four situations, including the ones where you need only one piece.

Short answer
Claude + MCP is the intelligence and the open way to connect it. Luca Express is the operations workspace that puts that intelligence to work on phones, email, tasks and follow-ups. Dell Automation Platform is the execution layer for infrastructure on Dell hardware. Gus IT is the engineering that specifies, builds and validates across the three. Buy the pieces your situation needs; two of the four scenarios below are answered by Claude alone.
Claude + MCP
A very capable AI plus an open standard for plugging it into systems you already have. Anything those systems don't do, you (or someone you hire) build, host and secure.
Luca Express
A business platform that ships the rest already assembled: CRM, email, calendar and tasks, phone and voice agents, and a gateway to several AI models, running as one system. Claude is one of the models inside it.
Dell Automation Platform
Dell's operations platform, aimed at Dell hardware (Automation Studio plug-ins can also reach non-Dell systems and public clouds): a catalog of validated blueprints, an orchestrator, and Automation Studio for blueprints you write yourself. It runs infrastructure; it does not run your front office.

Disclosure: Gus IT builds Luca Express, deploys Claude for clients and designs infrastructure on Dell hardware. We are not affiliated with Anthropic or Dell Technologies. Every answer below works for us, including the ones that don't involve our product.

Our answer, in full and signed

A prospective customer asked. This is our answer, written for this page and dated September 16, 2026, with the parts that do not favor us left in.

You asked what the difference is between Luca Express and just an MCP server (Model Context Protocol, the open standard for connecting an AI to your systems) with Claude. We build Luca Express, so read our answer knowing that.

Claude with an MCP server gives you the intelligence and an open, standard way to connect it to the systems you already run. If you have a CRM, a phone system and someone to write, host and maintain the connectors, that is a complete answer, and it is the cheaper one. We deploy Claude this way for clients, and two of the four situations on this page are answered by Claude alone.

Luca Express is the rest of the system, already assembled and run by us: one web workspace; a CRM with email, calendar, tasks and contacts; phones on real numbers with an AI that answers incoming calls; sales workflows that start when something happens in the CRM, such as a completed call; and one connection to Claude and to other AI models. We checked each of those against the running code and its tests on September 15 and 16, 2026. They are real. Our own tasks, email and phones run on them every day.

Not everything is ready, and you should not buy on the strength of these today. Time-delayed follow-ups: Luca Express can queue a callback for later, but nothing runs that queue on a schedule yet, so a follow-up starts when an event triggers it, not by the clock. Outbound AI calling: built, and switched off in every configuration we ship. Governance: controls over who may do what, spend limits and a person approving sensitive actions are early access; Claude Enterprise is ahead of us there, and if audit trail and access control decide your purchase, choose it. Our own MCP side: the gateway that lets your Claude use Luca's tools is early access, and a central hub for other MCP servers, such as GitHub, Jira or Slack, is designed, not built.

Where that leaves you. If your team is technical, or you like the tools you already have, take Claude and MCP and skip us. If you want AI working the phones, the inbox and the pipeline without hiring an engineer to build and keep the connectors, Luca Express is that. The way in is a paid pilot on one workflow with a measurable target, and the format of your data export agreed before we start.

Everything above describes the code as it runs, not a roadmap. The table further down this page carries the same labels, and we will change them when the code changes.

Gus IT LLC gus@gusit.degusitllc.com/#contact

What we checked

  • Workspace, September 16: one web workspace and one live list of apps. Of 262 app folders on disk, about 221 are reachable from the workspace. The rest sit in seven groups switched off on purpose, or are not registered.
  • CRM, email, calendar, tasks, contacts, September 16: adding, viewing, changing and deleting records works in each, and each has its own automated tests.
  • Sales follow-ups, September 16: a completed call creates its follow-up end to end. Nothing runs queued callbacks on a schedule, and no next-run time is ever set.
  • Voice, September 16: telephony on the account's real numbers. Incoming calls are checked to be genuinely from the carrier and rejected otherwise. AI answering of incoming calls is on in every configuration we ship; AI-placed outgoing calls are off in every configuration.
  • Governance and the model gateway, September 15: the labels in the table below are unchanged from that review.

Four roles, one practice

Most of the confusion comes from comparing four different kinds of thing as if they were one.

The model and the open connector

Claude + MCP

Anthropic's Claude: chat, Claude Cowork for people who don't code, Claude Code for engineers, and the API. MCP (Model Context Protocol) is an open standard that lets Claude, and other AI clients that support it, call tools and read data in your systems. A server can expose tools, data and even interactive panels (MCP Apps).

What MCP is not: a CRM, a phone system, or the place your records live. Someone still builds and runs those behind it.

A protocol, not a product.

The operations workspace

Luca Express

Business applications, data, phone numbers and AI agents, with the plumbing between them, operated by Gus IT. Staff work in one web workspace; agents work the same records.

Claude does the agent work. OpenAI, Gemini, Mistral and local models route through the same gateway for tasks that suit them.

Where the work actually happens.

The execution layer

Dell Automation Platform

In Dell's words, "an AI-driven operations platform for creating, managing and continuously optimizing your IT environment": a portal with a catalog of validated blueprints, an orchestrator that runs online or on-premises, and Automation Studio for your own blueprints (declarative YAML) and plug-ins, including Redfish for Dell and non-Dell systems.

Dell acquired Cloudify, an open-source orchestration company, in January 2023; Dell did not disclose terms, and TechCrunch and SiliconANGLE reported about $100M. Dell Automation Platform is where Dell sells orchestration and blueprints today; Dell's pages don't spell out the lineage, so we claim no more than that.

Blueprints as governed artifacts, not scripts.

The engineers

Gus IT

Specification, architecture decisions, validation and handoff. Our Azure Local deployer builds clusters from bare metal on Dell PowerEdge. Our Claude practice puts Claude Code, connectors and governance into engineering teams. Luca Express is our own platform, so we run what we sell.

Specify it, build it, prove it, hand it over.

How the pieces join

One loop, five stages. Each stage has an owner, and the output of the last feeds the first.

  1. Customer + Gus IT

    Outcome

    State what should change and how you will know. A target that cannot be measured is not a requirement yet.

  2. Claude Code + MCP

    Specification

    Scenarios written so they can fail: Given, When, Then, So that, As measured by. One test per scenario. Claude drafts against your systems through MCP; engineers review.

  3. Dell Automation Platform

    Blueprint

    A validated blueprint from Dell's catalog where one fits, or an Automation Studio blueprint you own. The choice of execution layer is written down as a decision, not left to the first script.

  4. Dell Automation Platform

    Execution

    The orchestrator runs the blueprint on Dell compute, storage and networking or the private cloud. Dell calls this deterministic automation from version-controlled blueprints; approvals and an audit trail are yours to confirm with Dell and design into the run.

  5. Luca Express

    Operation

    Engineers record each run's result, evidence and follow-ups in the workspace; there is no connector between Luca Express and Dell Automation Platform. What the run shows becomes the next specification.

This is the practice we run, with engineers in the loop at every stage. The two Dell stages show where Dell Automation Platform slots in on infrastructure that licenses it, described from Dell's pages; elsewhere the execution layer is our Azure Local deployer or your existing infrastructure-as-code. Nothing here is wired together: Luca Express and Dell Automation Platform do not talk to each other, and Claude's drafts reach execution only through an engineer's review. The Luca Express parts that could automate stages of this carry their real status in the next section.

Who supplies which layer

A working system needs all six layers. Hatched cells are the ones you supply yourself. Every Luca Express item carries its real status today; Dell's items are Dell's products, described from Dell's public pages.

Layer
Claude + MCP
Luca Express
Dell Automation Platform
Screens for your staffWhere people work every day
Included

Claude's chat, Claude Cowork (a workspace for non-engineers with connectors, files and scheduled tasks) and Claude Code. Pipeline views, inboxes, call logs and dashboards still come from your existing tools or get built.

  • One web workspace across all appsAvailable

A portal and catalog for infrastructure operators. Not a business workspace.

Business data and workflowsRecords, follow-ups, schedules, phone numbers
You build or bring

MCP connects Claude to your CRM, phone system and helpdesk; it doesn't provide them. Unattended jobs run as scheduled tasks in Claude Cowork or Claude Code routines in the cloud, on Managed Agents (beta), or on your own scheduler.

  • CRM, email, calendar, tasks, contactsAvailable
  • Phone and voice agents on real numbersAvailableAI answers incoming calls today. AI-placed outgoing calls are built but switched off in every configuration we ship.
  • Sales workflows triggered by CRM events (new deal, stage change, completed call)Available
  • Time-delayed follow-ups and scheduled callbacksEarly accessCallbacks are queued today; the scheduled run of that queue is not wired yet, so delayed follow-ups do not fire on their own.
  • Infrastructure operations apps (Azure, Hyper-V, VMware, Microsoft 365)Early access

Not its job.

Connectors and toolsHow the AI reaches your systems
Included

The MCP standard and many prebuilt servers. A read-only server for an in-house system is often a few hours with the official SDK; one with proper auth, logging, error handling and a deployment story is days to weeks. Those are our rough figures, not published benchmarks.

  • Agents use the platform's own apps and dataAvailable
  • MCP gateway so your own Claude can use Luca toolsEarly access
  • Central hub for third-party MCP servers (GitHub, Jira, Slack)Roadmap
Dell product

Plug-ins for Dell and non-Dell systems over open standards such as Redfish; reuse of existing infrastructure-as-code and CI/CD pipelines.

GovernanceWho may do what, audit trail, spend limits
Included on business plans

Team: SSO and admin controls for connectors. Enterprise adds role-based access, SCIM, audit logs, a compliance API, spend limits and custom data retention.

  • Role-based access checks and an audit log on agent tool callsEarly accessEnforced and logged on the platform's own tool surfaces; coverage varies by surface, and we review it with you.
  • Per-user AI spend caps and usage ledgerEarly access
  • Human approval before sensitive agent actionsEarly accessConfirmation gates run in the platform's app surfaces; not yet on the MCP surface.
Dell product

Blueprints are version-controlled artifacts rather than loose scripts. Dell supports its validated blueprints; its FAQ says it "does not provide support for user-generated blueprints" and points you to Dell Services for help building them.

Infrastructure executionBuilding and changing servers, storage, clusters
You script it

Claude Code with the tools your team already uses: Azure CLI, PowerShell, Ansible, Terraform. Approvals, audit and rollback are yours to design.

  • Azure Local cluster deployer, bare metal to cluster on Dell PowerEdgeAvailableDelivered by Gus IT engineers as a service, not self-serve.
  • Day-2 operations apps for those platformsEarly access
Dell product

Validated blueprints and an orchestrator for private cloud, AI and edge software on Dell compute, storage and networking; Dell Private Cloud, Dell AI Solutions and Dell Distributed Private Cloud as targets.

The modelThe AI itself
Included

Claude: Haiku, Sonnet, Opus and Fable. One vendor, by design.

  • Claude plus OpenAI, Gemini, Mistral and local models through one gatewayAvailableEach provider activates with its key. Ask which Claude versions the gateway routes today; the catalog is updated on request.
Dell product

Dell's pages describe a Blueprint AI Assistant in Automation Studio and an "agentic AI layer" on the platform.

AvailableIn daily use on the platform today.
Early accessBuilt and running, not yet covered end to end by automated tests or a support commitment. Scoped and enabled with you in a pilot.
RoadmapDesigned, not built. Don't buy for it.
Dell productDell's own product; availability, support and pricing come from Dell.

On governance, Claude Enterprise is ahead of Luca Express today. If audit and access control are your deciding factors, that is the honest answer.

What changes day to day

Claude + MCPLuca ExpressDell Automation Platform
Getting startedClaude is ready in minutes. Custom MCP servers take from hours to weeks each, depending on auth, logging and hosting.Engineer-led onboarding. Our team stands up your environment and first workflows with you.Through Dell sales. The portal and orchestrator run online or on your premises.
Who maintains itYou: servers, credentials, updates, and fixes when a connected system changes its API.We maintain the platform. You own your data and your settings.Dell maintains the platform and its validated blueprints. Blueprints you write are yours to maintain.
Lock-inLow. MCP is an open standard and your systems stay yours.Higher. Your workflows live in our apps. Ask how you'd export before you start.Blueprints are YAML infrastructure-as-code; the orchestrator and the catalog are Dell's, on Dell hardware.
MaturityGenerally available products, widely deployed.A younger platform. Some parts are early access, as labeled above.A shipping Dell product line. Confirm availability for your region and hardware with Dell.
How it's deliveredSelf-serve.A managed service. No self-serve signup and no supported self-install package.Sold by Dell; terms from Dell.
Security surfaceEvery MCP server acts with whatever access you grant it, by credential or OAuth scope. Scoping, logging and prompt-injection defense are yours to design.Handled by the platform, with the maturity caveats in the governance row above.Dell's platform controls; the plug-ins and blueprints you write carry the credentials you give them.

What it costs

Claude's prices are Anthropic's published list prices in US dollars, checked September 15, 2026. Luca Express has no public price list and Dell prices its platform through its own channels, so we won't invent numbers for either.

Claude + MCP

  • Claude Team, standard seatIncludes Claude Code and Claude Cowork. 2 to 150 people.$25 / seat / mo$20 billed annually
  • Claude Team, premium seatAbout 5x the usage of a standard seat$125 / seat / mo$100 billed annually
  • Claude EnterpriseAnnual. Seat price plus usage at API rates. Adds SCIM, audit logs, compliance API.$20 / seatplus usage
  • Claude Pro / MaxIndividuals$20 / mo$17 billed annually; Max from $100 / mo
  • Managed Agents (beta)Anthropic-hosted agent runtime$0.08 / session-hrplus tokens
Claude API prices per million tokens
API, per million tokensInputOutput
Haiku 4.5$1$5
Sonnet 5$2$10
Opus 5$5$25
Fable 5.1$10$50
  • MCP itself is free and many servers are open source. The real cost is the engineering time to build, host, secure and maintain custom ones.
  • Phone numbers, voice, CRM and helpdesk licenses are billed separately by those vendors.

Luca Express

Quoted per engagement. Ask us for a quote that separates three lines, so you can compare each against the Claude figures plus the engineering time you'd otherwise spend:

  • Platform and apps: the workspace, CRM, communications and voice.
  • Onboarding: environment setup and your first workflows.
  • AI model usage: the tokens your agents and calls consume.

What a pilot is: one workflow with a measurable target, a fixed scope, and the format of your data export agreed before we start. Length and fee depend on the workflow; you get both in writing first.

Where it can come out cheaper: when you'd otherwise pay for a CRM, a voice-agent product, an automation tool, and an engineer to glue them together.

Where it comes out more expensive: when you already run those systems and only want AI on top. Then you'd be paying for apps you won't use.

Dell Automation Platform

Priced and sold by Dell; ask your Dell account team. Two things to budget alongside it:

  • Custom blueprints: Dell's FAQ says it "does not provide support for user-generated blueprints" and offers Dell Services instead, so budget engineering time, Dell Services, or an integrator for the ones you write.
  • The specification work: a blueprint is only as good as the scenarios and tests behind it. That is the part Claude Code and engineers supply, and it is a real line item.

Where it earns its place: repeatable, audited changes across many Dell systems, where a validated blueprint replaces a hand-run procedure.

Where it doesn't: a single cluster you will build once, or an environment with no Dell hardware in it.

For scale: Anthropic's pricing page works an example of 10,000 support conversations at about 3,700 tokens each on Haiku 4.5 and lands at about $37. That figure is the input-token arithmetic (37 million tokens at $1 per million); output tokens come on top. The model is rarely the biggest line item. The people who build and run the system around it usually are.

Four situations, four answers

Where we would point each one, including the cases where the answer isn't us.

Software team · 8 engineers

Faster coding, reviews, tickets and docs

Claude + MCP only
Why
Claude Code with Team seats, plus MCP servers for GitHub, Jira and your database, is built for exactly this. Luca's business apps and phone agents add nothing this team needs, and Dell's platform is for infrastructure, not source code.
Rough cost
8 standard seats: $200/mo billed monthly, or $160/mo billed annually ($1,920/yr). If all eight move to premium seats: $1,000/mo, or $800/mo billed annually ($9,600/yr).
Where the others fit
Only if the same company also wants the front-office pieces, or runs Dell infrastructure its engineers have to change safely.
Services business · 15 people, no engineer

Answer calls after hours, log leads, follow up, book appointments

Luca Express, pilot first
Why
Claude + MCP supplies the intelligence and the connectors, but not the phone numbers, the CRM, the scheduler, or anyone to wire them together. Luca Express ships those as one system. It runs Gus IT's own tasks, email and phones every day; we are a consultancy with engineers on staff, so treat that as a working reference rather than a like-for-like one.
Watch for
Onboarding is engineer-led. Start with a paid pilot on one workflow, such as one after-hours call that becomes a lead and then a follow-up, and measure it. If you already love your CRM, try Claude Team plus that CRM's connector first.
Regulated organization · healthcare, finance, public sector

AI with SSO, audit trail, retention control and approvals

Claude Enterprise first
Why
Anthropic's Enterprise plan offers SSO, SCIM, audit logs, a compliance API, custom data retention and what Anthropic calls a HIPAA-ready configuration, directly from the model vendor. Luca's access controls and approval gates are early access, so don't choose it for governance yet.
Where the others fit
Luca Express for a specific, non-sensitive workflow after your security team has reviewed it. On Dell infrastructure, Dell Automation Platform is worth evaluating with Dell as a version-controlled, repeatable way to execute infrastructure change.
Infrastructure team · Dell hardware, Azure Local or private cloud

Build and run clusters safely, and stop hand-running procedures

All four, each in its lane
Execution
Dell Automation Platform runs validated blueprints on PowerEdge and the private cloud, and Automation Studio holds the blueprints you own.
Specification
Claude Code with MCP into your inventory, ticketing and repositories drafts the scenarios, tests and blueprint changes; your engineers review every one.
Design and validation
Gus IT designs the target, runs the Azure Local deployer from bare metal to cluster, and validates the result against the scenarios.
Operation
Luca Express carries the tasks, follow-ups and evidence engineers record after each run, if you don't already have a workspace for that. If you run ServiceNow or Jira, keep them; Claude reaches them over MCP and Luca adds nothing there. There is no integration between Luca Express and Dell Automation Platform; Luca's day-2 operations apps for these platforms are early access and are scoped with you.
Either way
Give agents read-only access first. Write access to production needs approvals and a rollback plan, whichever tools you pick.

Which pieces you need

Skip Luca Express when

  • Your team is technical and mostly wants help writing and reviewing code.
  • You already run a CRM, phone system and helpdesk you like, and just want AI on top of them.
  • You need mature, audited governance on day one: SSO, SCIM, audit export and approvals. Go with Claude Enterprise.
  • You want self-serve signup or to self-host tomorrow. Luca Express is delivered as a managed service today.
  • Minimal lock-in is a hard requirement. MCP is an open standard; a platform's apps are stickier by nature.

Add Luca Express when

  • You want AI working the phones, inbox and pipeline, not only a chat window.
  • You don't have, or don't want, an engineer to build and babysit connectors.
  • You'd otherwise buy a CRM, a voice-agent product and an automation tool separately, and pay someone to join them.
  • You want more than one AI model without re-plumbing each app.
  • You're comfortable starting with a pilot on one measurable workflow.

Add Dell Automation Platform when

  • You run Dell servers, storage or a Dell private cloud and change them more than once.
  • Hand-run procedures are your risk: you want changes version-controlled and repeatable instead of hand-run.
  • A validated blueprint exists for your stack, or you have engineers to write and maintain your own.
  • You can specify and test what a blueprint must do. If not yet, start with validated blueprints and build that discipline alongside.
  • Skip it for a one-off build, or for an environment with no Dell hardware in it.

Questions to ask any vendor, including us

Want a straight answer for your case?

Tell us the workflow or the environment you have in mind. We'll tell you which pieces it needs, even when the answer is one you can buy without us.

Email Gus IT Book a consultation