SAP BusinessObjects BI MCP Server by CData

Created By
CDataSoftwarea year ago
This project builds a read-only MCP server. For full read, write, update, delete, and action capabilities and a simplified setup, check out our free CData MCP Server for SAP BusinessObjects BI (beta): https://www.cdata.com/download/download.aspx?sku=GJZK-V&type=beta
Overview

What is SAP BusinessObjects BI MCP Server by CData?

This project builds a read-only Model Context Protocol (MCP) server for SAP BusinessObjects BI, allowing LLMs to query live data without needing SQL.

How to use the project?

To use the MCP server, clone the repository, build the server, install the CData JDBC Driver, configure your connection, and create a configuration file for your AI client.

Key features of the project?

  • Read-only access to SAP BusinessObjects BI data.
  • Natural language querying capabilities.
  • Integration with AI clients like Claude Desktop.

Use cases of the project?

  1. Querying live data from SAP BusinessObjects BI using natural language.
  2. Integrating with AI tools for data analysis and reporting.
  3. Simplifying data access for non-technical users.

FAQ from the project?

  • Can I write data using this MCP server?

No, this server is read-only. For write capabilities, check the full CData MCP Server.

  • Is there a trial version available?

Yes, a free beta version is available for full read, write, update, and delete capabilities.

Server Config

{
  "mcpServers": {
    "{classname_dash}": {
      "command": "PATH\\TO\\java.exe",
      "args": [
        "-jar",
        "PATH\\TO\\CDataMCP-jar-with-dependencies.jar",
        "PATH\\TO\\sap-businessobjects-bi.prp"
      ]
    }
  }
}
Project Info
Created At
a year ago
Updated At
10 months ago
Author Name
CDataSoftware
Star
-
Language
-
License
-

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago