clix

Clix MCP Server exposes two main capabilities within the Model Context Protocol (MCP) ecosystem: semantic documentation search and SDK search. Once the server is configured in your MCP client, you can invoke search_docs to retrieve relevant sections from Clix documentation (user guides, API references, troubleshooting, and best practices) with semantic ranking, and search_sdk to explore Clix SDKs for various platforms (iOS, Android, Flutter, React Native) along with production-ready code snippets. These tools enable agents to surface up-to-date references and ready-to-use samples during conversations. To use the server, configure it in your MCP client (VS Code extension settings, Copilot MCP settings, Claude/Codex configurations, etc.) so that the client can forward your requests to the server and display results in the assistant UI or tool palette. Note that network access is required for fetching documentation pages and SDK source files, and you can fine-tune result counts via environment variables.

Prerequisites:

• Node.js >= 18
• npm (comes with Node.js) or pnpm/yarn if preferred

Installation steps:

1. Install the MCP server globally from npm: npm i -g @clix-so/clix-mcp-server@latest

2. Verify installation by running the server's CLI help or version: clix-mcp-server --help clix-mcp-server --version

3. (Optional) For local development and testing, clone the repo, install dependencies, build, and run tests: git clone https://github.com/clix-so/clix-mcp-server.git cd clix-mcp-server npm install npm run build npm test npm run dev

4. Add the MCP configuration to your client using the shared config example, or use npx to always run the latest version: json { "mcpServers": { "clix-mcp-server": { "command": "npx", "args": ["-y", "@clix-so/clix-mcp-server@latest"] } } }

Environment variables:

• DOCS_SEARCH_MAX_RESULTS: controls how many documentation results are returned per query (default is 3).
• SDK_SEARCH_MAX_RESULTS: controls how many SDK results are returned per query (default is 3). Adjust these values to balance thoroughness vs. latency. If you host behind a proxy or require authentication for fetching docs/SDKs, ensure network access is configured accordingly. The server is designed to be used with MCP clients via standard MCP configurations; for local development, you can point the client to a local build as shown in the README. The npm package name is @clix-so/clix-mcp-server, and the server can be driven using npx for always-up-to-date usage or installed globally for persistent access.