Server data from the Official MCP Registry
Perplexity answers: ask, search, reason, and deep research through the Sonar API.
About
Perplexity answers: ask, search, reason, and deep research through the Sonar API.
Security Report
The server sends the Perplexity API key only to api.perplexity.ai over HTTPS, reads it solely from the PERPLEXITY_API_KEY environment variable, and has no shell execution, file access, or dynamic code evaluation. The only findings are informational: upstream error bodies are echoed into tool results and message roles are not restricted to a fixed set. Supply chain analysis found 4 known vulnerabilities in dependencies (0 critical, 2 high severity). Package verification found 1 issue.
8 files analyzed · 7 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
Permissions Required
This plugin requests these system permissions. Most are normal for its category.
What You'll Need
Set these up before or after installing:
How to Install
Add this to your MCP configuration file:
{
"mcpServers": {
"io-github-cloudcorprecords-answersearch": {
"env": {
"PERPLEXITY_API_KEY": "your-perplexity-api-key-here"
},
"args": [
"-y",
"@reneturcios/answersearch"
],
"command": "npx"
}
}
}Documentation
View on GitHubFrom the project's GitHub README.
answersearch
answersearch puts Perplexity's models within reach of a terminal or an agent. You can put a question to a search-grounded model and get an answer with its sources, pull ranked web results on their own, hand a hard problem to the reasoning model, or commission a slower, deeper research pass that reads widely before it writes. It runs as a small CLI or as an MCP server, and it needs a Perplexity API key.
Setup
Get a key from the Perplexity API portal and export it:
export PERPLEXITY_API_KEY=<redacted>
Without the variable set, every command and tool call fails with an
error that names PERPLEXITY_API_KEY — nothing is sent anywhere.
Install
npx @reneturcios/answersearch ask "what changed in the latest Node LTS?"
Or run the container image:
docker run -i -e PERPLEXITY_API_KEY ghcr.io/cloudcorprecords/answersearch
The container defaults to the MCP server (see below). Pass CLI arguments to use it as a CLI instead.
CLI
# Conversational answer grounded in live web search (sonar-pro)
answersearch ask "who won the marathon last weekend?"
# Ranked search results only, with optional budgets
answersearch search "composting basics" --max-results 5 --max-tokens 4000 --max-tokens-per-page 512
# Step-by-step reasoning (sonar-reasoning-pro)
answersearch reason "prove that the square root of two is irrational"
# Deep, multi-source research (sonar-deep-research) — this one takes a while
answersearch research "compare the failure modes of lithium and sodium batteries"
answersearch --version
Successful calls print the API's JSON response. Exit codes: 0 on
success, 1 when the API call fails (including a missing key), 2
for usage errors.
MCP server
One bin serves both faces. The mcp subcommand starts a stdio MCP
server:
npx -y @reneturcios/answersearch mcp
MCP client configuration:
{
"mcpServers": {
"answersearch": {
"command": "npx",
"args": ["-y", "@reneturcios/answersearch", "mcp"],
"env": { "PERPLEXITY_API_KEY": "your-key-here" }
}
}
}
Tools
| Tool | Input | What it does |
|---|---|---|
perplexity_ask | messages (array of {role, content}, required) | Conversational answer with live web search, via the sonar-pro model on the chat-completions endpoint. |
perplexity_search | query (string, required), max_results, max_tokens, max_tokens_per_page (integers, optional) | Direct call to the Search API; returns its ranked results and metadata as returned upstream. |
perplexity_reason | messages (required, same shape) | Analytical reasoning via sonar-reasoning-pro. |
perplexity_research | messages (required, same shape) | Deep research via sonar-deep-research; expect a longer wait than the other tools. |
Tool results are the upstream JSON, pretty-printed as text. Upstream failures (bad key, quota, HTTP errors) come back as tool errors carrying the status and the API's own message.
Development
npm install
npm run build # tsc -> dist/
npm test # node test runner over test/*.test.ts, no network (fake fetch fixtures)
npm run dev # run the CLI from source via tsx
License
MIT — see LICENSE.
Reviews
No reviews yet
Be the first to review this server!
More Developer Tools MCP Servers
Rea
Freeby Morluto · Developer Tools
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
Paperclip
Freeby Paperclipai · Developer Tools
Trending hip-hop artist momentum scores across four cultural dimensions.
Fetch
Freeby Modelcontextprotocol · Developer Tools
Web content fetching and conversion for efficient LLM usage
Git
Freeby Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
Toleno
Freeby Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
MCP Marketplace
Freeby mcp-marketplace · Developer Tools
Search and install MCP servers from inside your AI client.
