MCP serverMCP serverExposes tools to a coding agent over MCP.See every one →What this type is →independently maintainedindependently maintainedPublished by one person or a small company outside SAP. Says nothing about quality; the readings say that.See every one →
@odatano/core-mcp
MCP server exposing ODATANOODATANOmaintains 4 entriesindependent — the Cardano-to-OData bridge built on CAP — to an agent, so the chain is reachable as tools rather than as a REST client.
Facts
Latestv0.6.0ReleasedLicenceApache License 2.0, January 2004
Where it sits
Lives in
Provides
Serve your application over MCPCAPServe your application over MCPExposing selected application data and business operations to an AI agent through the Model Context Protocol. An application may also integrate remote services through [service integration](capability:service-integration), connecting its exposed contract with [agent access to your systems](capability:agent-systems-access). Development assistance belongs to [agent access to your code](capability:agent-code-access).
Flavors
Node.jsfrom its runtime
Requires
@odatano/core@odatano/coreNamed as a dependency in its documentation.
Who is behind it
maxalexweber
Before choosing this
Conditions
PracticalFunctional boundary
The repository the package declares has been deleted — verified against the GitHub API, not just a failed fetch. The package is still on npm, so it installs; the source it was published from is no longer readable, which is a harder thing to discover than a stale version number.
PolicySAP API Policy 4.2026a§ 1.1, 1.2, 2.2.2from Serve your application over MCPAn MCP server exposes an SAP API, or uses SAP APIs to supply tools, resources or data to an agent.
- § 1.1 Published APIs. Published APIs are made available for the documented purposes identified by SAP, including integration, extensions and data exchange.
- § 1.2 Non-Published APIs. Customer and third-party applications must not access non-published APIs except where documentation permits it or SAP otherwise authorizes it.
- § 2.2.2 AI call sequences and data extraction. Outside SAP-endorsed architectures, data services or expressly identified pathways, the policy prohibits specified agentic API use and systematic or large-scale extraction.
MCP does not replace the API's documented-use boundary. Check that every endpoint is published for the intended use and whether the policy's AI-call or extraction provisions apply to the design.
SAP API Policy 4.2026a →LicenceSAP Developer License Agreement 3.2 CAP§ 1, 3from Serve your application over MCPA covered CAP plugin or application exposes SAP product data or covered customer-application functionality through MCP.
- § 1 License. Productive customer applications are limited to SAP BTP or another SAP-licensed platform, and mass extraction to a non-SAP product is restricted except where solely required for SAP interoperability.
- § 3 Artificial Intelligence Training. The agreement prohibits use of the covered materials and customer applications for training artificial-intelligence models or systems.
The CAP developer agreement can apply alongside the API Policy. Ordinary agent inference is not automatically AI training; section 3 becomes relevant when covered materials or applications are used to train, develop or refine a model or system.
SAP Developer License Agreement 3.2 CAP →What it declares
Every artifact
- Type
- MCP server
- Origin
- Independently maintained
- Runtime
- Node.js
As an MCP server
- Guardrails
2 quoted from signing guardrail show all
nothing in this server can sign.
HSM signing (
SignWithHsm*) and every Admin operation (crawler / worker
pause & resume) are deliberately not exposed.
For serve your application over MCP
- Exposure source
- Domain-specific backend
- Exposed operations
- Chain/indexer reads, unsigned builds, human/wallet signing handoff and signed submission; opt-in wallet jobs can ask a backend-managed wallet to sign
- Execution path
- Remote backend calls
- Exposure control
- Target feature discoveryFeature opt-in
Connections
Group by
NodeRelationBasis
Functional
Serve your application over MCPServe your application over MCPExposing application data and operations to agents over MCPSAP and community, narrow by design
provides
stated
provides Serve your application over MCP
Exposes the [@odatano/core](artifact:odatano-core) Cardano CAP/OData backend through domain-specific MCP tools on [Node.js](external:nodejs) 20+. It accepts a hosted gateway or direct [@odatano/core](artifact:odatano-core) host, rather than an arbitrary CAP application-service contract. The MCP process cannot sign; explicitly enabled wallet jobs on a supporting direct target delegate signing to a backend-managed wallet. Domain tools call that OData backend through its gateway or direct host. The registered catalogue follows target-served features; the gateway excludes operator services, HSM signing and wallet jobs, while wallet jobs on a supporting direct target require ODATANO_MCP_ENABLE_WALLET_JOBS=1.
“- Node.js >= 20”“Point `ODATANO_ACCESS_URL` at any ODATANO host app instead of the gateway:”“nothing in this server can sign.”“**Opt-in** (`ODATANO_MCP_ENABLE_WALLET_JOBS=1`): queue a job that a server-managed wallet builds, signs, submits and confirms”“the Cardano OData bridge for SAP CAP”“**unsigned** transactions”“hand them to a human / wallet for signing; verify signatures; submit signed”“MCP server exposing ODATANO (Cardano OData bridge, SAP CAP) to AI agents: reads, unsigned tx builds, signing handoff, submit”“What the gateway does not offer, this server does not register:”“HSM signing (`SignWithHsm*`) and every Admin operation”“**Opt-in** (`ODATANO_MCP_ENABLE_WALLET_JOBS=1`)”“closed on the gateway”
Exposing application data and operations to agents over MCP
Technical
@odatano/core@odatano/coreCAP plugin serving the Cardano blockchain as OData V4independent, cap
needs
authored
needs @odatano/core
CAP plugin serving the Cardano blockchain as OData V4
Download
Install
npm add @odatano/core-mcpDerived from the package name. No recipe recorded; the README has the configuration.
Architecture
Download
@odatano/core-mcpMCP server exposing ODATANO — the Cardano-to-OData bridge built on CAP — to an agent, so the chain is reachable as tools rather than as a REST client.independent, cap
@odatano/coreA CAP plugin that serves the Cardano blockchain as OData V4, giving enterprise-shaped access to a public chain, funded through Cardano Catalyst.independent, cap
Your MCP client → @odatano/core-mcpStated in the document, dataBy its type: an MCP server is called by an MCP client
@odatano/core-mcp → @odatano/coreDocumented only
SAPnot SAP's, or the project's ownstated in the documentdocumented only
History
Others providing
Compare all 9 on the Serve your application over MCP page →Serve your application over MCPServe your application over MCPExposing selected application data and business operations to an AI agent through the Model Context Protocol. An application may also integrate remote services through service integration, connecting its exposed contract with agent access to your systems. Development assistance belongs to agent access to your code.SAP and community, narrow by design
- API ManagementAPI ManagementAPI proxies in front of backend services, with security and traffic management policies attached to them, and Developer Hub where consumers subscribe.sap official, btpAPI proxies with security and traffic policies and Developer Hub
- com.sap.cds:cds-adapter-mcpcom.sap.cds:cds-adapter-mcpThe MCP protocol adapter for CAP Java, serving an @mcp-annotated Application Service as an MCP server with three generated tools, describe, query and call, and data changes only through unbound actions.sap official, capMCP adapter turning a CAP Java service into an MCP server
- @cap-js/mcp@cap-js/mcpA CAP plugin that serves an @mcp-annotated service over MCP with three generated tools, describe, query and call_action, and writes its endpoint into the local agent's configuration in development.sap official, capExposes CAP services as MCP servers for AI agents
- @gavdi/cap-mcp@gavdi/cap-mcpGenerates an MCP server from the CDS model — annotated entities become resources and annotated actions become tools, so an agent reaches the service without a second server being written.independent, capGenerates an MCP server from annotated CDS entities and actions
- @neoimpulse/cap-js-mcp@neoimpulse/cap-js-mcpAn MCP server inside a CAP application, with default tools that read the running model and query entities, plus configurable application tools, prompts and resources.independent, capMCP server inside a CAP application with model and query tools
- @odatano/nightgate-mcp@odatano/nightgate-mcpMCP server exposing NIGHTGATE, the Midnight blockchain attestation layer, as agent tools — the companion to the CAP indexer plugin of the same name.independent, capMCP server exposing the NIGHTGATE Midnight attestation layer
- @shahid.la/cds-db-nlquery-mcp@shahid.la/cds-db-nlquery-mcpMCP server that answers plain-English questions against the entities in db/schema.cds — it discovers the schema, generates CQN-backed SQL with real joins, and returns rows.independent, capMCP server answering plain-English questions against a CDS schema
- cap-mcp-plugincap-mcp-pluginGenerates an MCP server from a CDS model: annotated entities become MCP resources, functions and actions become tools, and services can expose reusable prompt templates. A fork of @gavdi/cap-mcp that adds an OAuth proxy, IAS client registration and draft-lifecycle tools.independent, capMCP server generated from a CDS model, forked from @gavdi/cap-mcp
Details
Sources
Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.
Compatibility and provenance
runtimesnode
latestv0.6.0
first release
releases and cadence7, ~3d median
discovered vianpm registry · keywords:sap-cap
first seen in the atlas
ecosystem and domaincap, ai-and-agents
History in the atlas
- [{"key":"mcp_exposure_source","value":"ODATANO Cardano CAP/OData host or the hosted ACCESS gateway; fixed domain backend"},{"key":"mcp_operations","value":"Chain/indexer reads, unsigned builds, human/wallet signing handoff and signed submission; opt-in wallet jobs can ask a backend-managed wallet to sign"},{"key":"mcp_execution_path","value":"Domain tools call the ODATANO OData backend through its gateway or direct host; the MCP process does not sign transactions"},{"key":"mcp_exposure_control","value":"Domain tool catalogue follows target-served features; gateway omits operator services, HSM signing and wallet jobs; wallet jobs require explicit opt-in elsewhere"}]
- Domain-specific backend
- Remote backend calls
- Target feature discovery; Feature opt-in
- 404 from the GitHub API. Found by the first full run of scripts/check-links.mjs — the citation had a checked date and nobody had re-read it.
- First seen.
For your agent
- Ref
artifact:odatano-core-mcp- JSON
- /artifacts/odatano-core-mcp.json
- MCP
- Connecting an agent