Test Mcp

Created By
ComPDFKita year ago
hahahh ![asd](https://avatars.githubusercontent.com/u/108785628?s=64&v=4) <img src="https://avatars.githubusercontent.com/u/108785628?s=64&v=4" alt="2.4" width="50%" height="50%"/>
Overview

What is ComIDP MCP Server?

ComIDP MCP Server is a lightweight Model Context Protocol (MCP) server designed for seamless integration with AI chatbots, providing unstructured document processing functionalities, such as extracting data from PDF files.

How to use ComIDP MCP Server?

To use the ComIDP MCP Server, set up the server by installing the required dependencies, configuring the integration with Claude Desktop, and using the provided API for data extraction from PDF files.

Key features of ComIDP MCP Server?

  • Intelligent Document Extraction: Extracts textual content from PDF documents.
  • Batch processing: Supports multiple file uploads for extraction.
  • Future enhancements: Plans to support more document formats and integration with other ComIDP tools.

Use cases of ComIDP MCP Server?

  1. Extracting data from invoices and receipts for accounting purposes.
  2. Processing academic papers to extract relevant information.
  3. Archiving and organizing large volumes of documents efficiently.

FAQ from ComIDP MCP Server?

  • What document formats does ComIDP MCP Server support?

Currently, it supports PDF files, with plans to include JPG and PNG formats in the future.

  • Is there a trial version available?

Yes, you can contact the team for a trial license key.

  • How can I get support?

You can open an issue on GitHub or contact the R&D team for assistance.

Server Config

{
  "mcpServers": {
    "comidp-mcp": {
      "command": "uv",
      "args": [
        "run",
        "PATH/TO/comidp-mcp/src/virtual environment python",
        "PATH/TO/comidp-mcp/src/comidp_tools.py"
      ],
      "env": {
        "IDPKEY": "your_idp_key_here"
      }
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
ComPDFKit
Star
-
Language
-
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