MCP Perplexity Server
by sibbl
The MCP Perplexity Server provides an API to ask questions to a model behind the Perplexity API using the Model Context Protocol (MCP). It can be quickly set up using Docker or Node.js.
Last updated: N/A
What is MCP Perplexity Server?
The MCP Perplexity Server is a server that acts as an interface to the Perplexity API, allowing users to send questions and receive responses from a model. It utilizes the Model Context Protocol (MCP) for communication and supports different transport methods like SSE and stdio.
How to use MCP Perplexity Server?
The server can be deployed using Docker Compose or Node.js. Configuration is done through environment variables, including the Perplexity API key and transport method. After deployment, you can send requests to the server's endpoint to query the Perplexity API.
Key features of MCP Perplexity Server
API access to Perplexity models
Docker and Node.js deployment options
Support for SSE and stdio transport
Configurable model selection
Authentication support via header
Uses Model Context Protocol (MCP)
Use cases of MCP Perplexity Server
Integrating Perplexity models into applications
Building chatbots powered by Perplexity
Creating custom question-answering systems
Experimenting with different Perplexity models
Providing a standardized interface to Perplexity's capabilities
FAQ from MCP Perplexity Server
What is MCP?
What is MCP?
MCP stands for Model Context Protocol. It's used for communication with the Perplexity API.
How do I get a Perplexity API key?
How do I get a Perplexity API key?
You need to sign up for a Perplexity API account and obtain an API key from their platform.
What is the default transport method?
What is the default transport method?
The default transport method is stdio.
How do I enable SSE transport?
How do I enable SSE transport?
Set the MCP_TRANSPORT environment variable to sse.
How do I secure the SSE endpoint?
How do I secure the SSE endpoint?
Set the MCP_SSE_AUTH_HEADER_VALUE environment variable to a secret token. Clients must then include this token in the Authorization header of their requests.