Nx (local)
BetaNx's monorepo server gives the agent the workspace's project graph, file ownership, tasks, code generators and Nx documentation.
- Developer Tools
- Local
- Runs
- On the developer's Mac
- Launched with
- npx
- Platform
- macOS
- Publisher
- Nx
How it works
Every agent request passes through Ferentin policy before it reaches Nx (local).
It runs on the developer's Mac and talks to the AI client over stdio, so no network gateway sees it. Developers launch it with npx -y nx-mcp.
Ferentin's endpoint agent finds Nx (local) in the MCP configuration of AI clients on managed Macs. An administrator adds it once from the local MCP catalog for every managed Mac that launches it this way. Each of its tools starts unvetted until it is approved. Ferentin records every tool call.
- AI agentAsks for something
- Ferentin policies
- Nx (local) MCP serverRuns on the developer's Mac
- Governed resultChecked, logged, returned
About Nx (local)
Nx's monorepo server gives the agent the workspace's project graph, file ownership, tasks, code generators and Nx documentation.
Frequently asked about Nx (local)
- How do I connect Nx (local) to Ferentin?
- Enroll your Macs with the Ferentin endpoint agent, then add Nx (local) from the local MCP catalog in the Ferentin admin console. Every managed Mac that launches it the way the catalog names it is covered, and each of its tools starts unvetted until you approve it.
- Is the Nx (local) integration generally available?
- The Nx (local) integration is currently beta on Ferentin.
Related integrations
3
Playwright (local)
Microsoft's browser automation server drives a real browser for the agent. It navigates, fills forms, clicks and reads pages.
PostgreSQL (local)
The reference PostgreSQL server runs read queries against the database named on its command line. The package is archived but still widely run.
Redis (local)
Read and write access to a Redis database, run as a container.