The Searchcraft MCP Server exposes a suite of administrative tools that let you manage a Searchcraft cluster from MCP Clients. It provides capabilities to create and manage indexes, ingest and delete documents, manage federations and authentication keys, and perform search and analytics operations. Tools are organized into engine API tools (for direct cluster actions such as creating indexes, adding documents, and managing keys), federation management, stopwords and synonyms management, and import tools for generating schemas from JSON data. With this MCP server, tools like create_index, add_documents, create_key, get_search_results, and generate_searchcraft_schema enable programmatic control of your cluster from natural-language prompts or automated workflows. The included sample prompts show how to chain actions (e.g., create an index, ingest documents, create a read API key) to bootstrap an application quickly. To use it, connect your MCP client (for example Claude Desktop) to the server and issue requests using the available tool names and parameters described in the Engine API Tools sections of the documentation.

Prerequisites:

• Node.js (14+ or as required by the package, the README badges suggest Node.js 22+)
• npm or yarn

Installation steps:

1. Clone or download the repository containing the MCP server code.
2. Install dependencies: npm install

   or if using yarn:

   yarn install
3. Build the TypeScript sources (if the project uses a build step): npm run build

   or the project may auto-build on start; consult package.json for the exact script names

4. Run the server: npm run start

   or

   npm run dev

If you prefer to run via npx without local installation:

1. Ensure you have npm available, then run: npx -y searchcraft-mcp-server

Environment configuration can be provided via env vars described in the mcp_config section.

Configuration tips:

• The MCP server works with a Node.js/Express stack per the README indicators; ensure your Node version matches the package requirements.
• Common environment variables include those for authenticating with your Searchcraft cluster (e.g., SEARCHCRAFT_HOST, SEARCHCRAFT_API_KEY) and networking (PORT).
• If you run behind a reverse proxy or need TLS, configure your proxy and update the server’s port and host accordingly.
• When upgrading the MCP server, verify compatibility of the tool names and payload schemas, as API changes can affect prompts and tool invocations.

Troubleshooting:

• If tools fail to load, check that dependencies are installed and that the MCP server has network access to the Searchcraft cluster.
• For authentication errors, re-check your API key and permissions assigned to the key used by the MCP client.