Database · MODEL CONTEXT PROTOCOL

lupuletic onyx mcp server

lupuletic onyx mcp server is a community-listed Model Context Protocol server. Review the source repository before installation.

WHAT IT CONNECTS

What lupuletic onyx mcp server gives an AI Agent

  • **Enhanced Search**: Semantic search across your Onyx document sets with LLM relevance filtering
  • **Context Window Retrieval**: Retrieve chunks above and below the matching chunk for better context
  • **Full Document Retrieval**: Option to retrieve entire documents instead of just chunks
  • **Chat Integration**: Use Onyx's powerful chat API with LLM + RAG for comprehensive answers
  • **Configurable Document Set Filtering**: Target specific document sets for more relevant results
  • Node.js (v16 or higher)
  • An Onyx instance with API access
  • An Onyx API token
  • Clone the repository:
  • Install dependencies:
  • Build the server:
  • Configure your Onyx API Token:
  • Start the server:
  • The command to run the server (`node`)
  • The path to the built server file (`/path/to/onyx-mcp-server/build/index.js`)
  • Environment variables for `ONYX_API_TOKEN` and `ONYX_API_URL`
  • `query` (required): The topic to search for
  • `documentSets` (optional): List of document set names to search within (empty for all)
  • `maxResults` (optional): Maximum number of results to return (default: 5, max: 10)
  • `chunksAbove` (optional): Number of chunks to include above the matching chunk (default: 1)
  • `chunksBelow` (optional): Number of chunks to include below the matching chunk (default: 1)
  • `retrieveFullDocuments` (optional): Whether to retrieve full documents instead of just chunks (default: false)
  • `query` (required): The question to ask Onyx
  • `personaId` (optional): The ID of the persona to use (default: 15)
  • `documentSets` (optional): List of document set names to search within (empty for all)
  • `chatSessionId` (optional): Existing chat session ID to continue a conversation
  • **Use Search When**: You need specific, targeted information from documents and want to control exactly how much context is retrieved.
  • **Use Chat When**: You need comprehensive answers that combine information from multiple sources, or when you want the LLM to synthesize information for you.
  • **Knowledge Management**: Access your organization's knowledge base through any MCP-compatible interface
  • **Customer Support**: Help support agents quickly find relevant information
  • **Research**: Conduct deep research across your organization's documents
  • **Training**: Provide access to training materials and documentation
  • **Policy Compliance**: Ensure teams have access to the latest policies and procedures
  • Linting
  • Building
  • Testing
  • Code coverage reporting
  • **PR Title Validation**: All PR titles are validated against the [Conventional Commits](https://www.conventionalcommits.org/) specification:
  • PR titles must start with a type (e.g., `feat:`, `fix:`, `docs:`)
  • This validation happens automatically when a PR is created or updated
  • PRs with invalid titles will fail the validation check
  • **Commit Message Validation**: All commit messages are also validated against the conventional commits format:
  • Commit messages must start with a type (e.g., `feat:`, `fix:`, `docs:`)
  • This is enforced by git hooks that run when you commit
  • Commits with invalid messages will be rejected
  • Use `npm run commit` for an interactive commit message creation tool
  • **Version Bump Determination**: The system analyzes both the PR title and commit messages to determine the appropriate version bump:
  • PR titles starting with `feat` or containing new features → minor version bump
  • PR titles starting with `fix` or containing bug fixes → patch version bump
  • PR titles containing `BREAKING CHANGE` or with an exclamation mark → major version bump
  • If the PR title doesn't indicate a specific bump type, the system analyzes commit messages
  • The highest priority bump type found in any commit message is used (major > minor > patch)
  • If no conventional commit prefixes are found, the system automatically defaults to a patch version bump without failing
  • **Version Update and Publishing**:
  • Bumps the version in package.json according to semantic versioning
  • Commits and pushes the version change
  • Publishes the new version to npm

SECURITY

An MCP listing is not a security review

An MCP server may receive model context, credentials, local files, or permission to call external systems. Review its code, requested environment variables, network behavior, package provenance, and maintenance status before connecting it to an agent.