#business-intelligence
16 results found
SQLite MCP Server
Mirror of
Sqlite
Database interaction and business intelligence capabilities
Kyomi
AI data intelligence platform that brings your data warehouse, dashboards, monitoring, and accumulated business knowledge into any MCP client. Connects to BigQuery, Snowflake, PostgreSQL, MySQL, ClickHouse, Redshift, Databricks, SQL Server, and Azure Synapse.
TAM-MCP-Server
A comprehensive **Model Context Protocol (MCP)** server for market sizing analysis, TAM/SAM calculations, and industry research. Built with TypeScript, Express.js, and following the MCP 2024-11-05 specification.
Wren Engine
🤖 The Semantic Engine for Model Context Protocol(MCP) Clients and AI Agents 🔥
🔍 Intelligent Anomaly Detection System
Modular server for handling MCP protocol
Fodda Knowledge Graphs
Fodda MCP provides AI agents with access to expert-curated knowledge graphs covering retail, beauty, sports, and other industries. Query structured insights, explore relationships, retrieve evidence, and generate macro overviews powered by PSFK's proprietary research. Features: • Search across knowledge graphs with semantic understanding • Explore node relationships and connections • Access evidence and source attribution • Generate industry overviews and insights • PSFK Retail, Beauty, and Sports graphs available
Bonnard CLI
Ultra-fast to deploy agentic-first mcp-ready semantic layer. Let your data be like water. Bonnard is a CLI for building and deploying semantic layers. Define metrics and dimensions in YAML, deploy a governed MCP server, and serve AI agents and BI tools. Supports Snowflake, BigQuery, Databricks, PostgreSQL, and more. Ships with native integrations for Claude Code, Cursor, and Codex. GitHub: https://github.com/meal-inc/bonnard-cli Docs: https://docs.bonnard.dev/docs/ npm: https://www.npmjs.com/package/@bonnard/cli
Power Bi Analyst Mcp
Connect Claude to your Power BI semantic models. Browse workspaces, tables, and measures, run DAX queries, and get results — with large datasets automatically saved to local CSV files to protect the LLM context window. Includes a query history log for cross-session reuse and auditability.