Vectorize

Created By
vectorize-mcp-servera year ago
Vectorize MCP server for advanced retrieval, Private Deep Research, Anything-to-Markdown file extraction and text chunking.
Overview

what is Vectorize?

Vectorize is a Model Context Protocol (MCP) server designed for advanced vector retrieval, private deep research, and converting various file formats into Markdown.

how to use Vectorize?

To use Vectorize, set up your environment with your organization ID and API key, then run the MCP server using npx. You can perform document retrieval, text extraction, and deep research through its API.

key features of Vectorize?

  • Advanced vector search capabilities for document retrieval
  • Text extraction and chunking into Markdown format
  • Private deep research generation from specified pipelines

use cases of Vectorize?

  1. Retrieving relevant documents based on specific queries.
  2. Extracting text from various file types and converting them into Markdown.
  3. Conducting in-depth research on topics using private pipelines.

FAQ from Vectorize?

  • What types of documents can Vectorize process?

Vectorize can process various document types, including PDFs and other text formats.

  • Is there a limit to the number of documents I can retrieve?

The limit depends on the configuration of your pipeline and the parameters set during the retrieval process.

  • How secure is the data processed by Vectorize?

Vectorize ensures that all data processed is handled securely, especially during private deep research.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
vectorize-mcp-server
Star
-
Language
-
License
-

Recommend Servers

View All
Alloy

2 days ago
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)

8 hours ago
Crevio

a day ago