Public tranche contract — Analytics Legends — SAP Analytics Intelligence MCP Resource

Public tranche contract is one of 3 resources on the Analytics Legends — SAP Analytics Intelligence MCP server. Connect the server and your client can attach it as context.

by client

How to attach Public tranche contract from your client

• Claude Code Analytics Legends — SAP Analytics Intelligence Resource/Public tranche contract run in your project directory
• Claude Desktop Analytics Legends — SAP Analytics Intelligence Resource/Public tranche contract ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor Analytics Legends — SAP Analytics Intelligence Resource/Public tranche contract ~/.cursor/mcp.json
• VS Code Analytics Legends — SAP Analytics Intelligence Resource/Public tranche contract .vscode/mcp.json
• Zed Analytics Legends — SAP Analytics Intelligence Resource/Public tranche contract ~/.config/zed/settings.json
• Windsurf Analytics Legends — SAP Analytics Intelligence Resource/Public tranche contract ~/.codeium/windsurf/mcp_config.json
• Cline Analytics Legends — SAP Analytics Intelligence Resource/Public tranche contract ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI Analytics Legends — SAP Analytics Intelligence Resource/Public tranche contract ~/.gemini/settings.json
• Grok Analytics Legends — SAP Analytics Intelligence Resource/Public tranche contract .mcp.json (in your project root)
• ChatGPT Analytics Legends — SAP Analytics Intelligence Resource/Public tranche contract Settings → Connectors → Advanced → Developer mode
• Claude.ai Analytics Legends — SAP Analytics Intelligence Resource/Public tranche contract Settings → Connectors → Add custom connector
• LangChain Analytics Legends — SAP Analytics Intelligence Resource/Public tranche contract pip install langchain-mcp-adapters

Other resources on this server

• AI access policy
• Platform manifest

Analytics Legends — SAP Analytics Intelligence also offers 4 prompts — things you invoke, where a resource is context you attach.

Read from the server itself, by connecting to it and calling resources/list on 24 September 2026. A listing does not declare its resources, so asking is the only way to know them, and this is what the server actually offers rather than what its listing claims. Names only are stored; connect the server for each resource's type and contents.