Searchcraft MCP Server

Most developer tooling work still happens through a UI a human drives. Searchcraft MCP server moves it into the conversation instead. Searchcraft's MCP Server.

The short version

An MCP Server powered by Searchcraft – the developer-first vertical search engine.

Getting it running

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

The tools it exposes

The server publishes 8 tools. What each one is for:

• One — Step** → Use create_index_from_json to analyze, generate schema, create the index, and import all documents in one command
• analyze_json_from_file — Read JSON data from a local file and analyze its structure to understand field types and patterns for Searchcraft index schema generation
• analyze_json_from_url — Fetch JSON data from a URL and analyze its structure to understand field types and patterns for Searchcraft index schema generation
• generate_searchcraft_schema — Generate a complete Searchcraft index schema from analyzed JSON structure, with customizable options for search fields, weights, and other index
• create_index_from_json — Complete workflow to create a Searchcraft index from JSON data. Fetches JSON from URL or file, analyzes structure, generates schema, creates the
• create_vite_app — Creates a complete Vite + React search application from JSON data. Analyzes your data structure, generates optimized search templates, and creates a
• Parameters — The Parameters tool exposed by this server
• Prerequisites — The Prerequisites tool exposed by this server

What it needs from you

Configuration is passed through the environment: VITE_ENDPOINT_URL, VITE_INDEX_NAME, VITE_READ_KEY, ENDPOINT_URL, CORE_API_KEY, YOUR_API_KEY, MCP_SERVER_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

• Existing Searchcraft Index → The index specified in VITE_INDEX_NAME should already exist - Valid Read Key → The VITE_READ_KEY must have read permissions for the index - Git Available → The tool uses git to clone the template repository - Node.js & Yarn → Required for dependency installation

Things to watch

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

How it compares

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Searchcraft's toolset — One, analyze_json_from_file, analyze_json_from_url and 5 more — is a fair guide to whether it matches your workflow. It is maintained by searchcraft-inc; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.