parquet_mcp_server

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is parquet_mcp_server?

parquet_mcp_server is a powerful Model Control Protocol (MCP) server designed for manipulating and analyzing Parquet files, providing essential tools for data scientists and developers.

how to use parquet_mcp_server?

To use parquet_mcp_server, install it via Smithery or clone the repository, set up a virtual environment, and configure the necessary environment variables. Then, integrate it with Claude Desktop for seamless operation.

key features of parquet_mcp_server?

  • Text embedding generation from Parquet file columns.
  • Detailed analysis of Parquet file schemas, row counts, and sizes.
  • Conversion of Parquet files to DuckDB databases for efficient querying.
  • Conversion of Parquet files to PostgreSQL tables with pgvector support.
  • Markdown file processing into structured chunks with metadata.

use cases of parquet_mcp_server?

  1. Data scientists analyzing large datasets in Parquet format.
  2. Applications requiring vector embeddings for text data.
  3. Projects needing to convert and analyze Parquet files.
  4. Workflows leveraging DuckDB for fast data querying.
  5. Applications utilizing PostgreSQL for vector similarity searches.

FAQ from parquet_mcp_server?

  • Can parquet_mcp_server handle all types of Parquet files?

Yes! It is designed to work with various Parquet file structures.

  • Is parquet_mcp_server free to use?

Yes! It is open-source and free for everyone.

  • How can I troubleshoot common issues?

Check the SSL settings, ensure the Ollama server is running, and verify file permissions.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
0
Language
Python
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago