MCP-VizAPI: Visual Data Extraction with VizAPI.ai

Created By
IvanZidova year ago
Overview

What is MCP-VizAPI?

MCP-VizAPI is a server that integrates with VizAPI.ai to extract structured data from images and documents using the Model Context Protocol (MCP).

How to use MCP-VizAPI?

To use MCP-VizAPI, set up the server by installing the necessary dependencies, configuring your environment variables, and running the server either using Python or Docker.

Key features of MCP-VizAPI?

  • List and retrieve extraction templates.
  • Suggest fields for extraction from documents/images.
  • Extract structured data using predefined templates.
  • Health check for the VizAPI service.

Use cases of MCP-VizAPI?

  1. Automating data entry from scanned documents.
  2. Extracting information from invoices and receipts.
  3. Integrating with AI agents for enhanced data processing.

FAQ from MCP-VizAPI?

  • What is required to run MCP-VizAPI?

You need Python 3.12+, a VizAPI.ai account, and Docker if running as a container.

  • Can I use MCP-VizAPI without Docker?

Yes, you can run it using Python directly.

  • How do I check if the VizAPI service is running?

Use the health check feature provided by the server.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
IvanZidov
Star
0
Language
Python
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