CLDGeminiPDF MCP Server

Created By
tfll37a year ago
MCP server for Claude Desktop allowing sharing files to Google's Gemini AI models via API for analysis and then response retrieval to Claude Desktop for further processing
Overview

What is CLDGeminiPDF?

CLDGeminiPDF is a Model Context Protocol (MCP) server that allows Claude Desktop to analyze PDF documents using Google's Gemini AI models, providing intelligent analysis and insights.

How to use CLDGeminiPDF?

To use CLDGeminiPDF, download the pre-built JAR file, obtain a free Gemini API key from Google AI Studio, configure the server in Claude Desktop, and start analyzing PDFs.

Key features of CLDGeminiPDF?

  • PDF content extraction and analysis using Gemini AI models
  • Support for multiple Gemini models (2.5, 2.0, 1.5 series, and Gemma models)
  • Dual processing methods: direct PDF upload or text extraction
  • Seamless integration with Claude Desktop via MCP
  • Flexible configuration for easy deployment

Use cases of CLDGeminiPDF?

  1. Analyzing research papers for methodology and conclusions.
  2. Extracting key terms and risks from contracts.
  3. Generating insights from various PDF documents.

FAQ from CLDGeminiPDF?

  • What are the prerequisites for using CLDGeminiPDF?

    You need Java 11 or higher, Maven, a Google AI Studio API key, and the Claude Desktop application.

  • Can I build CLDGeminiPDF from source?

    Yes, you can clone the repository and build it using Maven.

  • What should I do if I encounter a "PDF file not found" error?

    Ensure the file path is correct and that the PDF file is accessible and readable.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
tfll37
Star
0
Language
Java
License
MIT 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
Crevio

2 days ago