Nucleus · the governed MCP gateway

One doorway to every system your agents touch.

Nucleus sits between AI clients and the company's systems. Claude, a Dispatch box, or a Slack bot connects to one MCP endpoint and sees only the tools that person is allowed to use. Every call is authorized before it leaves, runs as a named person, is metered, rate-limited and written to an audit trail. Nucleus also runs workflows against those tools in the cloud, with nothing to install.

How it works with Dispatch → See it in production

ProtocolMCP AccessDefault-deny Every callMetered + audited TenancyMulti-tenant WorkflowsIn the cloud

What it is

Clients ask. Nucleus decides. Systems answer.

An agent with a credential can do anything the credential can do. Nucleus is there so no client ever holds one. The client presents its own key, and Nucleus decides whether this person may call this tool, now, at this rate, within this budget. It holds the system credentials itself and makes the call on the person's behalf.

Clients

Claudedesktop · code · web

Dispatch boxworkflows · agents · schedules

Slackslash commands · bots

Any MCP clientone endpoint

Every tool call

Nucleus

Who · a named person, from their own key
Allowed? · default-deny, per install and tool
Rate · tenant, person and key buckets
Budget · reserve, call, settle
Record · ledger, audit, traces

Systems

Translation platformprojects · usage · health

Flatten cacheprerender · sitemaps · requeue

CRM & billingcontacts · deals · subscriptions

Tickets, chat, searchand whatever comes next

The gateway

Built on the assumption that tools are powerful.

Whatever connects, it gets the same controls. Nothing here depends on the client behaving well.

Discovery

Each person sees only their tools

The tool list is built per person from access rules. A tool someone may not call is not on their list, so an agent cannot reason its way toward it.

Authorization

Default-deny, every call

Access is checked again on each call, not only when the list is built. Revoking access takes effect on the next call, not the next session.

Credentials

Secrets stay in the vault

System credentials are stored encrypted with each server install. Clients present their own key. No system password ever reaches a laptop, a prompt or a model.

Metering

Priced per tool, on a ledger

Each tool carries a credit cost. Calls reserve against a budget before they run and settle afterwards, and every event is recorded on an append-only ledger.

Runaway protection

Rate limits at three levels

Token buckets per organization, per person and per API key. A runaway loop hits its own limit first and stops there, before it can affect the shared system or the budget.

Operations

Observable in production

Metrics, logs and traces for every call, plus an audit log of security events. When something goes wrong, you can see who called what, and when.

Orchestration

Workflows that run in the cloud, with nothing to install.

Nucleus goes beyond granting access to tools. It also chains them into workflows that run unattended, in the same way Dispatch does, but hosted, so a team can automate the moment it signs in.

Build

In the browser

Lay out the steps in the workflow builder: which tools to call, in what order, and what each step passes to the next. There's no server to stand up and no runtime to maintain.

Run

In the cloud, under the same rules

Every step is a governed tool call, run as the workflow's owner, rate-limited, priced and recorded like any other call. Automation gets no back door.

Grow

Onto your own box

When a job needs local models, your own MCP servers or systems only your network can reach, run it on Dispatch instead. It still uses the same tools, rules and record. Cloud or box ›

Nucleus Apps

Start as tools. Grow into an app, without leaving Nucleus.

A new product can begin as a database and a set of MCP tools that Claude drives. When the team needs screens, Nucleus hosts a web app in front of the same tools, with sign-in, permissions and live updates already in place.

Day 1

Tools and a database

Install it like any MCP server. Claude is the interface while the business rules take shape against real data.

When people need screens

Register an app

Add two fields on the server's catalog entry, and the app appears at /apps/<name>/ behind Nucleus sign-in, with every request permission-checked.

From then on

People and agents, live

The app and the tools share one implementation, so a draft Claude rewrites shows up on a person's screen within about a second. See Protolyth ›

Accountability

Every action has a name on it.

Any meaningful action can be traced to the same five things, which is what makes it billable, auditable and safe to let agents act on.

Org tenant› Person user› Key client identity› Install server instance› Tool the call

When an agent acts for someone, the action is recorded as that person. A rep's assistant writing to the CRM writes as the rep, and a scheduled workflow writes as whoever owns it. An agent never gets a shared superuser key. Its permissions are the person's, and so is its record.

Who connects

The same tools from wherever the work starts.

A tool is installed once, in Nucleus, and every client gets it. The person asking at a desk, an automation running overnight on a box, and a teammate typing a command in Slack all reach the same tool, with the same rules and the same record.

Ad hoc

Claude

Ask a question about a customer or a project, and Claude answers from live systems through Nucleus, within your own access. Nothing to export, and no credentials to paste in.

Recurring

Dispatch

When a workflow needs a local model, a local MCP server or a system on your own network, it runs on a Dispatch box instead of in the cloud. It still calls the same Nucleus tools under the same rules. How the two fit ›

In the channel

Slack

A slash command can start a workflow, and the result is posted back to the channel the team already reads. Nobody has to learn a new screen.

Keep reading

From gateway to running work.

Apps