How perplexityai/modelcontextprotocol works
This is Perplexity’s MCP server, exposing live web search and Agent API capabilities to MCP clients over local stdio or self-hosted Streamable HTTP. The server registers four tools: direct search, quick answers, deep research, and reasoning. Agent-backed tools call the Agent API; search calls the Search API. Shared server code handles upstream requests and responses, while validation defines response schemas. The excerpts show the main wiring; HTTP configuration and logging are visible in source, while some upstream details are not.
Main entry points: server.ts MCP Server · http.ts HTTP Entry · index.ts Stdio Entry · validation.ts Response Schemas
Components 13
MCP Entry Points
- Stdio Entry
src/index.ts - HTTP Entry
src/http.ts
Research Tools
- MCP Server
src/server.ts - Web Search
src/server.ts - Quick Answers
src/server.ts - Deep Research
src/server.ts - Advanced Reasoning
src/server.ts
Perplexity APIs
- Agent API
- Search API
Shared Runtime
- Response Handling
src/server.ts - Response Schemas
src/validation.ts - Structured Logger
src/logger.ts
Other components
- MCP Client
Connections 17
- MCP Client → Stdio Entry: connects locally
README.md - MCP Client → HTTP Entry: connects remotely
README.md - Stdio Entry → MCP Server: starts
src/index.ts - HTTP Entry → MCP Server: creates per request
src/http.ts - MCP Server → Web Search: registers
src/server.ts - MCP Server → Quick Answers: registers
src/server.ts - MCP Server → Deep Research: registers
src/server.ts - MCP Server → Advanced Reasoning: registers
src/server.ts - Web Search → Search API: requests search
src/server.ts - Quick Answers → Agent API: requests answer
src/server.ts - Deep Research → Agent API: requests research
src/server.ts - Advanced Reasoning → Agent API: requests reasoning
src/server.ts - Quick Answers → Response Handling: formats result
src/server.ts - Deep Research → Response Handling: formats result
src/server.ts - Advanced Reasoning → Response Handling: formats result
src/server.ts - Response Handling → Response Schemas: validates against
src/server.ts - HTTP Entry → Structured Logger: logs events
src/http.ts