perplexity -zerver

Perplexity MCP Zerver provides a set of research-oriented capabilities that run locally via Bun. It exposes tools for intelligent web research, documentation extraction, API discovery, code analysis, and persistent conversations stored in SQLite. The available tools include: search for web research with configurable depth, get_documentation to retrieve technical documentation in structured form, find_apis to surface relevant APIs with descriptions, check_deprecated_code to analyze code snippets for outdated patterns, extract_url_content to parse and structure content from URLs (including GitHub), and chat_perplexity to maintain context across sessions. You can interact with these tools through your MCP client by issuing commands that call the corresponding tool names, for example: “Use perplexity to research quantum computing advancements” or “Ask perplexity-server for React 18 documentation.” The chat_perplexity tool maintains a persistent conversation history, leveraging local SQLite storage to preserve context between sessions. Use these capabilities to assemble research, verify facts, extract code examples, and maintain a coherent line of inquiry over time.

Prerequisites:

• Bun runtime (https://bun.sh/)
• Node.js 18+ (for TypeScript compilation during build, if needed)

Installation steps:

1. Clone the repository:

git clone https://github.com/wysh3/perplexity-mcp-zerver.git
cd perplexity-mcp-zerver

2. Install dependencies:

bun install

3. Build the TypeScript project:

bun run build

4. Run or configure the MCP server using your MCP config file (see mcp_config section for example). Ensure the built entry exists at the path specified in args (e.g., /absolute/path/to/build/main.js).

Tips and common considerations:

• Ensure the build step outputs the server entry at the path referenced in the MCP configuration (/main.js).
• If you move the build output, update the MCP config accordingly.
• The MCP config uses Bun as the runtime; you can adjust the timeout (default 300 seconds) based on your network conditions and expected research tasks.
• Browser automation for Pro account features may require additional environment variables or login steps as described in the Pro Account section of the README.
• For troubleshooting server connection issues, verify the absolute path in the configuration, confirm Bun/Node.js availability, and ensure the build completed successfully.
• If you plan to customize storage or environment-specific settings, consider adding env variables in the mcp_config under an env block (not required for basic operation).