pulsemcp scanned Safe content atomic mcp-remote

SAP OData (BTP)

This MCP server provides programmatic access to SAP OData services running on SAP Business Technology Platform (BTP), enabling AI assistants to perform CRUD operations on SAP business data through automatically discovered service endpoints. Built with TypeScript and the SAP Cloud SDK, it features configurable service discovery with pattern-based filtering, automatic metadata parsing to generate type-safe tools for each entity, and support for both OData v2 and v4 protocols with proper SAP authentication handling. The implementation includes comprehensive query capabilities with OData parameters ($filter, $select, $expand, etc.), dynamic tool registration that creates shortened tool names to work within MCP constraints, and flexible deployment options supporting both local development and Cloud Foundry environments. Designed for enterprise scenarios where AI assistants need direct access to SAP business systems for data analysis, reporting, process automation, or integration workflows without requiring manual API configuration or SAP technical expertise.

Cognium trust score

67%

Tier

Scanned

Composite of vulnerability cleanliness, spec conformance, provenance, stability, and usage signals — scanned and weighted by Cognium. Human and agent signals are tracked separately. Last scanned 2026-09-19.

Scan details: Circle-IR · 2026-09-19 · Appeal

View full trust & usage report →

Metadata

Version: 1.0.0
Skill type: atomic
Execution layer: mcp-remote
Category: devops-ci
Source: PulseMCP
Repository: github.com/lemaiwo/btp-sap-odata-to-mcp-server
Author type: human
Last scanned: 2026-09-19
Updated: 2026-09-19

View source Find related skills

MCP

Resolve SAP OData (BTP) from your agent

Streamable HTTP transport at https://api.skillsregistry.net/mcp. No auth for read tools. Discovery: .well-known/mcp.json.

One command in your shell — Claude Code wires it up and verifies the connection. Run /mcp in any session to confirm.

claude mcp add --transport http --scope user skillsregistry https://api.skillsregistry.net/mcp

Swap --scope user for --scope project to commit it to .mcp.json.

Your client Same endpoint everywhere; only the config key differs. The full list is in the descriptor.

Claude Desktop · Settings → Connectors → Add custom connector

https://api.skillsregistry.net/mcp

Paste the URL as the connector endpoint. No authentication.

ChatGPT · Settings → Connectors → Create (developer mode) → MCP server URL

https://api.skillsregistry.net/mcp

Authentication: none. Works in chat and deep research — the server exposes the connector search and fetch tools.

Codex CLI · ~/.codex/config.toml

[mcp_servers.skillsregistry]
url = "https://api.skillsregistry.net/mcp"