Provides a hub for routing MCP connections to multiple isolated SAP systems (DEV, QA, PROD) with per-user identity propagation via principal propagation.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@arc-mcp-hub Show me the sales order 12345 details."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Superseded by ARC-1's Multi-System Setup. This project is retired and retained for historical reference. No further features, bug fixes, dependency updates, or security fixes are planned. Use ARC-1 for new SAP multi-system deployments.
The hub originally placed several ARC-1 instances behind one MCP host, with a separate application for routing and token exchange. ARC-1 now handles SAP system/client routing directly through its built-in multi-target mode, removing the need for this hub in that deployment model.
Start with the migration guide, then follow the maintained ARC-1 docs:
BTP deployment overview — choose the topology.
Multi-System Setup — deploy and configure targets.
Multi-Target Administration — operate the service.
ARC-1 repository — maintained code and issue tracker.
Former hub interface | ARC-1 multi-target interface |
|
|
|
|
| Marked BTP subaccount destinations pointing to SAP systems |
Map each old environment name to its actual SAP system/client; these examples are not automatic aliases. Update client URLs and prompts/tool calls, then authenticate against ARC-1.
Check the replacement's scope before migrating: multi-target v1 is experimental, default-off, and mutation-free. It runs on SAP BTP Cloud Foundry with XSUAA and on-premise SAP targets. Principal Propagation is recommended. Shared Basic authentication is a separate opt-in with a one-instance limit. Writes, activation, and transport/Git mutations are unavailable on multi-target routes. Use separate ARC-1 instances and direct MCP connections for writable access or stronger isolation. Other MCP server backends need their own direct connections; ARC-1 is not a general proxy.
Related MCP server: mcphub
The source, tests, and deployment files are retained to explain existing installations. The following documents describe the former hub and are not instructions for new deployments:
Repository archival does not stop a deployed hub or migrate its users. Existing operators should follow the cutover and retirement steps.
MIT
This server cannot be deployed
One MCP endpoint for your company's tools, with per-person sign-in, policy and audit.
One MCP URL for all your connectors — scoped writes, enforced constraints, and a full audit trail.
Every service you connect, one MCP endpoint for all your AI tools. Sign in once.
Governed MCP gateway: one endpoint for your tools, with credential custody and audit log.