MCP servers that ship as code — a repository or a package you install and run locally (usually over stdio). They have no hosted endpoint, so we cannot probe or grade them: instead each one shows its repository, install command, license, stars and when it was last updated.
Collected from GitHub repositories and npm, PyPI, Cargo, Go, Maven, NuGet and RubyGems packages tagged as MCP servers, the official MCP Registry, Docker's MCP catalog, ModelScope, Baidu MCP World, Cline and other public directories; one entry per repository. A server that also offers a hosted endpoint is listed under Remote instead. These entries are not counted in our reachability, verification or readiness statistics.
-
MCP server that allows simple SAP GUI interaction for LLM models using simulated mouse clicks and keyboard input.
MIT ★ 146 -
MCP server that lets AI assistants work in SAP GUI for Windows: read screens and tables, fill in fields, run transactions. Saves wait for your approval.
pypi MIT ★ 50 -
ktern-sapguimcpgithub.com/kaarproducts/ktern-sapguimcpupdated this year
MCP server for SAP GUI automation (KTern.AI fork)
pypi MIT -
an MCP server that interacts with SAP via the Desktop and/or Web GUI
go MIT ★ 18 -
sapient-mcpgithub.com/yourorg/sapient-mcpupdated this year
Intelligent SAP GUI automation for AI agents — MCP server powered by RoboSAPiens
pypi Apache-2.0 -
MCP server for SAP ABAP development via ADT API. Connect AI assistants to SAP: read, write, test, and deploy ABAP code without SAP GUI.
npm MIT ★ 21 -
SAP ABAP MCPgithub.com/Coaspe/sap-abap-mcpno update data
SAP ABAP MCP is a local-first Model Context Protocol server that enables AI coding agents to develop, test, analyze, and operate SAP ABAP systems through the official ABAP Development Tools HTTP services. It supports repository search and source editing, structured DDIC workflows, enhancement inspection, paged package navigation, source-backed object creation, semantic services, activation, ABAP Unit and ATC, transports, abapGit, RAP generation, debugging, bounded class and executable-program profiling, runtime dumps, traces and feeds, cross-system comparison, dependency analysis, guarded refactoring, and an opt-in same-origin Screen/GUI Status bridge. Curated compact, development, and assurance presets reduce tool-schema token use without removing capabilities from the default surface. The default local stdio mode can be extended with governed self-hosted Streamable HTTP, API-key roles, OIDC/JWT authentication, request-scoped SAP bearer forwarding, per-session isolation, rate limits, structured audit logs, or a side-effect-free embeddable Node.js API. It also includes browser OAuth Authorization Code with PKCE, a read-only transport assurance CLI and GitHub Action, BTP service-key profile import, and live-SAP evidence tooling. SAP profiles and credentials remain on the user's computer, with passwords and OAuth credentials protected by macOS Keychain or Windows DPAPI. SAP-dependent capabilities are validated against the user's own SAP release, configuration, and authorizations.
smithery