MCP server providing essential day-to-day tools for data analysts and researchers
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"mcp-analyst-toolkit": {
"command": "<see-readme>",
"args": []
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
A Model Context Protocol (MCP) server that provides tools for data analysts and researchers. This server offers access to databases, change logs, and external APIs through the MCP interface.
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Click any tool to inspect its schema.
changelog_periodsList all available time periods in the change log
changelog://periods
changelog_periodGet detailed change logs for a specific period
changelog://{period}
clickhouse_queryClickHouse query templates for common tasks
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in analytics / data
Manage Supabase projects — databases, auth, storage, and edge functions
Query and manage PostgreSQL databases directly from AI assistants
Zero-dependency, token-efficient database MCP server for Postgres, MySQL, SQL Server, MariaDB, SQLite.
A Model Context Protocol (MCP) server that enables secure interaction with MySQL databases
MCP Security Weekly
Get CVE alerts and security updates for Mcp Analyst Toolkit and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
A Model Context Protocol (MCP) server that provides tools for data analysts and researchers. This server offers access to databases, change logs, and external APIs through the MCP interface.
Clone the repository:
git clone <repository-url>
cd mcp-analyst-toolkit
Install dependencies:
uv pip install -e .
Run the MCP server:
uv run mcp dev src/mcp_server/server.py
The server will start and display:
Start the MCP server in development mode:
uv run mcp dev src/mcp_server/server.py
Access the MCP Inspector at http://localhost:6274/ to explore available tools and resources.
Example of config to start using these tools in Claude Code.
{
"mcpServers": {
"analyst_toolkit": {
"command": "uv",
"args": [
"--directory",
"/path/to/repo/mcp-analyst-toolkit/src/mcp_server",
"run",
"server.py"
],
"env": {
"GITHUB_TOKEN": "your_github_token"
}
}
}
execute_query: Execute SQL queries against ClickHouse databasesget_databases: List all available databasesget_table_schema: Get detailed schema information for specific tableschangelog://periods: List all available time periodschangelog://<period>: Get detailed change logs for a specific period (e.g., changelog://2025_q1)Example periods:
2025_q1: Q1 2025 organizational changes2025_q2: Q2 2025 organizational changessrc/
├── mcp_server/
│ ├── __init__.py
│ ├── server.py # Main MCP server implementation
│ ├── prompts/
│ │ ├── __init__.py
│ │ └── clickhouse_query.py # ClickHouse query templates
│ ├── resources/
│ │ ├── __init__.py
│ │ ├── change_log.py # Change log resource handlers
│ │ └── change_log/ # Change log data files
│ │ ├── 2025_q1.json
│ │ ├── 2025_q2.json
│ │ └── ...
│ └── tools/
│ ├── __init__.py
│ ├── clickhouse.py # ClickHouse database tools
│ └── github.py # GitHub integration tools
Change log data is stored in JSON format under src/mcp_server/resources/change_log/. Each file represents a time period and contains structured event data:
[
{
"date": "2025-01-15",
"event": "New Year Collection Launch",
"impact": "Launched exclusive New Year fashion collection..."
}
]
src/mcp_server/tools/src/mcp_server/server.py