Onyx MCP Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

What is Onyx MCP Server?

Onyx MCP Server is a Model Context Protocol (MCP) server designed for seamless integration with Onyx AI knowledge bases, enabling users to search and retrieve relevant context from their documents.

How to use Onyx MCP Server?

To use the Onyx MCP Server, install it via Smithery or clone the repository, install dependencies, configure your Onyx API token, and start the server. You can then connect it to any MCP-compatible client.

Key features of Onyx MCP Server?

  • Enhanced semantic search capabilities across document sets.
  • Context window retrieval for better context understanding.
  • Full document retrieval option.
  • Integration with Onyx's chat API for comprehensive answers.
  • Configurable document set filtering for targeted results.

Use cases of Onyx MCP Server?

  1. Knowledge management for organizations.
  2. Customer support to quickly find relevant information.
  3. Research across extensive document collections.
  4. Training access to materials and documentation.
  5. Ensuring policy compliance by providing access to the latest procedures.

FAQ from Onyx MCP Server?

  • What are the prerequisites for installation?

    Node.js (v16 or higher) and an Onyx instance with API access are required.

  • Can I retrieve full documents?

    Yes, the server allows for full document retrieval in addition to chunk retrieval.

  • Is there a way to maintain conversation context in chat?

    Yes, the chat tool supports maintaining context across multiple interactions using a session ID.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
0
Language
TypeScript
License
MIT license

Recommend Servers

View All
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)

2 days ago