sap-bdc-mcp
by rahulsethi
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BDC_MODE | No | Runtime mode label (local/dev/prod) | local |
| BDC_USER | No | User label (redacted) | |
| BDC_REGION | No | Region label | |
| BDC_PLUGINS | No | Comma-separated plugin module paths to load (v0.2 also accepts npx:/uvx:/cmd: upstream MCP servers) | |
| BDC_BASE_URL | No | Base URL label (redacted where appropriate) | |
| BDC_MOCK_MODE | No | Use fixtures/local inputs instead of calling external endpoints | 1 |
| BDC_TENANT_ID | No | Tenant identifier (redacted in outputs) | |
| BDC_MAX_DOC_KB | No | Max size for fetched ORD docs (prevents 'LLM ate my RAM' moments) | 512 |
| BDC_VERIFY_TLS | No | Verify TLS certificates for HTTPS fetches | 1 |
| BDC_ORD_SOURCES | No | Comma-separated list of ORD sources (URLs or file paths) | |
| BDC_PLUGIN_TRUST | No | Operator-asserted trust for plugin aliases (v0.2) | |
| BDC_AUDIT_ENABLED | No | Every tool call writes a JSONL audit event (v0.2) | 1 |
| BDC_APPROVAL_TOKEN | No | Secret approval token for write operations (v0.2) | |
| BDC_REQUIRE_DRY_RUN | No | High-risk tools must dry-run first (v0.2) | 1 |
| BDC_SERVICE_ACCOUNT | No | Service account label (redacted) | |
| BDC_API_POLICY_STRICT | No | WRITE/ADMIN tools with api_surface=UNKNOWN are refused (v0.2) | 1 |
| BDC_ENABLE_ADMIN_TOOLS | No | Enable admin tools (v0.2) | 0 |
| BDC_ENABLE_WRITE_TOOLS | No | Enables write tools (keep OFF in v0.1) | 0 |
| BDC_PLUGIN_ENV_PASSTHROUGH | No | Secrets to forward to plugin subprocesses (v0.2) | |
| BDC_REQUIRE_APPROVAL_TOKEN | No | Require approval token for real execution (v0.2) | 1 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/rahulsethi/SAPBDCMCP'
If you have feedback or need assistance with the MCP directory API, please join our Discord server