MCP: UI5 MCP Server
by SAP
SAP's official MCP server for UI5 development: scaffold apps, lint code, validate manifests and pull API docs into your AI agent.
Nx's official MCP server hands an agent the monorepo's real structure — the project graph, task definitions, generators, owners and Nx docs — so edits land with cross-project impact in view instead of guessed from filenames.
Set up this MCP server in your favorite AI agent — copy a ready-made configuration below.
An agent dropped into an Nx monorepo sees a directory tree and has to infer the rest: which projects exist, what depends on what, which target runs the tests, whether a generator already scaffolds the thing it is about to hand-write. The Nx MCP Server removes the guessing by exposing the workspace's own metadata over the Model Context Protocol.
The server reads the same project graph Nx uses to schedule tasks, so the agent gets project relationships and file-to-project mapping, runnable targets, code ownership, the tech stack per project, the list of installed Nx plugins and their generators (with each generator's schema), and Nx's documentation. On an Nx Cloud workspace it also surfaces CI information, task output, and the self-healing fix flow.
The practical effect is that a change stops being local. Ask for a rename or an API change and the agent can see which projects consume the code and follow the change through them; ask for a new library and it can call the generator the workspace already has rather than inventing a folder layout.
It ships as the nx-mcp npm package and needs no install:
{
"servers": {
"nx-mcp": { "type": "stdio", "command": "npx", "args": ["nx-mcp@latest"] }
}
}By default it runs in a minimal mode that registers only nx_docs, nx_current_running_tasks_details, nx_current_running_task_output and nx_visualize_graph, keeping the client's tool list short; --no-minimal turns on the rest (nx_workspace, nx_project_details, nx_generators, nx_generator_schema, nx_available_plugins, nx_workspace_path). A .nx/nx-mcp-config.json file pins the choice per repository, with an allow/deny list ("tools": ["nx_docs", "!cloud_*"]), telemetry opt-out and debug logging; CLI flags override it. --sse with --port runs it over HTTP for concurrent clients instead of stdio.
If you already use the Nx Console extension in VS Code or Cursor, it manages the server for you and no manual config is needed.
Teams on Nx who have handed real refactoring work to an agent and are tired of it touching one project and breaking three. It is maintained by Nrwl inside the Nx Console repository, alongside the editor extension.
by SAP
SAP's official MCP server for UI5 development: scaffold apps, lint code, validate manifests and pull API docs into your AI agent.
by ESLint
The official ESLint MCP server, shipped inside the ESLint CLI - lets an editor agent lint files, read rule violations and apply fixes using your project's own configuration.
by SAP
SAP's official MCP server for SAP Fiori tools — generates Fiori elements apps from OData services or CAP projects and applies guided modifications to existing ones.
by PTC (Onshape)
PTC's MCP server for Onshape: describe a custom CAD feature in plain language and have an AI write, insert, run and debug the FeatureScript until it works.