OData MCP Bridge (Go)

Download the appropriate binary for your platform from thereleases page.

git clone https://github.com/oisee/odata_mcp_go.git cd odata_mcp_go go build -o odata-mcp cmd/odata-mcp/main.go

# Build for current platform make build # Build for all platforms make build-all # Build for all platforms with WSL integration (copies to /mnt/c/bin) make build-all-wsl # Build and test make dev # Check current version make version # See all options make help

# Build for current platform ./build.sh # Build for all platforms ./build.sh all # See all options ./build.sh help

# Using Make make build-linux # Linux (amd64) make build-windows # Windows (amd64) make build-macos # macOS (Intel + Apple Silicon) # WSL-specific builds (copies Windows binary to /mnt/c/bin) make build-windows-wsl # Build Windows + WSL integration make build-all-wsl # Build all platforms + WSL integration # Using build script ./build.sh linux # Linux (amd64) ./build.sh windows # Windows (amd64) ./build.sh macos # macOS (Intel + Apple Silicon) # Manual Go build GOOS=linux GOARCH=amd64 go build -o odata-mcp-linux cmd/odata-mcp/main.go GOOS=windows GOARCH=amd64 go build -o odata-mcp.exe cmd/odata-mcp/main.go

# Build Docker image make docker # Or manually docker build -t odata-mcp . # Run in container docker run --rm -it odata-mcp --help

# Build all platforms and copy Windows binary to C:\bin make build-all-wsl # Build only Windows and copy to C:\bin make build-windows-wsl

{ "mcpServers": { "northwind-v2": { "command": "C:/bin/odata-mcp.exe", "args": [ "--service", "https://services.odata.org/V2/Northwind/Northwind.svc/", "--tool-shrink" ] }, "northwind-v4": { "command": "C:/bin/odata-mcp.exe", "args": [ "--service", "https://services.odata.org/V4/Northwind/Northwind.svc/", "--tool-shrink" ] } } }

{ "mcpServers": { "my-sap-service": { "command": "/usr/local/bin/odata-mcp", "args": [ "--service", "https://my-sap-system.com/sap/opu/odata/sap/MY_SERVICE/", "--user", "myusername", "--password", "mypassword", "--tool-shrink", "--entities", "Products,Orders,Customers" ] } } }

Using Environment Variables (More Secure)

{ "mcpServers": { "my-secure-service": { "command": "/usr/local/bin/odata-mcp", "args": [ "--service", "https://my-service.com/odata/", "--tool-shrink" ], "env": { "ODATA_USERNAME": "myusername", "ODATA_PASSWORD": "mypassword" } } } }

Note:Claude Desktop currently doesn't support reading environment variables from your system. Theenvfield in the configuration sets environment variables specifically for that MCP server process.

Security Best Practices for Claude Desktop

Note:Claude Desktop does not currently support API key authentication for MCP servers. All MCP servers run locally with the same permissions as Claude Desktop itself.

{ "mcpServers": { "production-readonly": { "command": "/usr/local/bin/odata-mcp", "args": [ "--service", "https://production.company.com/odata/", "--read-only", "--tool-shrink" ], "env": { "ODATA_USERNAME": "readonly_user", "ODATA_PASSWORD": "readonly_pass" } }, "dev-with-functions": { "command": "/usr/local/bin/odata-mcp", "args": [ "--service", "https://dev.company.com/odata/", "--read-only-but-functions", "--trace-mcp" // Enable debugging ] } } }

The Claude Code CLI has stricter property name validation than other Claude tools. If you encounter errors like:

API Error: 400 {"type":"error","error":{"type":"invalid_request_error","message":"tools.17.custom.input_schema.properties: Property keys should match pattern ^[a-zA-Z0-9_.-]{1,64}$"}}

Use the--claude-code-friendlyflag to remove the$prefix from OData parameter names:

{ "mcpServers": { "northwind-claude-code": { "command": "/usr/local/bin/odata-mcp", "args": [ "--service", "https://services.odata.org/V2/Northwind/Northwind.svc/", "--claude-code-friendly", // Removes $ from parameter names "--tool-shrink" ] } } }

- $filter→filter
- $select→select
- $expand→expand
- $orderby→orderby
- $top→top
- $skip→skip
- $count→count

The server internally maps these friendly names back to their OData equivalents when making requests.

Operation Filtering Configuration Examples

{ "mcpServers": { "large-service-readonly": { "command": "/usr/local/bin/odata-mcp", "args": [ "--service", "https://large-erp.company.com/odata/", "--disable", "cud", // Disable create, update, delete "--tool-shrink", "--entities", "Orders,Products,Customers" ], "env": { "ODATA_USERNAME": "readonly_user", "ODATA_PASSWORD": "readonly_pass" } }, "minimal-tools": { "command": "/usr/local/bin/odata-mcp", "args": [ "--service", "https://api.company.com/odata/", "--enable", "gf", // Only get and filter operations "--tool-shrink" ] }, "no-actions": { "command": "/usr/local/bin/odata-mcp", "args": [ "--service", "https://api.company.com/odata/", "--disable", "a", // Disable all function imports/actions "--verbose" ] } } } ### AI Foundry Configuration For AI Foundry integration, use the --protocol-version flag to specify the 2025-06-18 protocol: 

See theAI Foundry Compatibility Guidefor detailed setup instructions.
The OData MCP bridge supports two transport mechanisms:

- STDIO (default)- Standard input/output communication, used by Claude Desktop

- HTTP/SSE- HTTP server with Server-Sent Events for web-based clients
🔒SECURITY MODEL: HTTP transport uses a strict security model.
- Localhost: Token required (--mcp-token)

- Non-localhost: Token + TLS required, no exceptions

- All interfaces (0.0.0.0/::): Requires--allow-all-interfaces+ token + TLS
Token can be any string - for dev,--mcp-token devworks fine.
Using Streamable HTTP Transport (Modern MCP Protocol)
New in v1.5.0: Support for Streamable HTTP transport (protocol version 2024-11-05)

- POST /mcp- Main MCP endpoint (supports automatic SSE upgrade)

- GET /health- Health check endpoint

- POST /sse- Legacy SSE endpoint (for backward compatibility)

- GET /health- Health check endpoint

- GET /sse- Server-Sent Events endpoint for real-time communication

- POST /rpc- JSON-RPC endpoint for request/response communication