Perplexity Answer Reader MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APIFY_TOKEN | Yes | Your Apify API token from console.apify.com/account/integrations. The server lists its tool without a token, but a call needs one. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ask_perplexity_with_sourcesA | Give questions and your own Perplexity API key. Returns one row per answer with the answer text, every search result with which ones the answer cites, the cited domains, the searches Perplexity ran, and, if you name a brand, whether the answer names and cites it and at what position. With no key it writes up to 3 free check rows and asks nothing. Pay per event on Apify: 0.01 USD per completed answer, plus your Perplexity bill. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool there is no risk of misselecting between alternatives, so the surface is trivially unambiguous. However, the single tool multiplexes several distinct modes (paid answer, free check rows with no key, optional brand-mention analysis), which blurs what the tool actually does in any given call.
The name ask_perplexity_with_sources is clear snake_case verb_noun form and, being the only tool, cannot conflict with anything. The 'with_sources' suffix describes the return shape rather than the action, which makes the name slightly less action-oriented than ideal.
A single tool is defensible for a narrow Perplexity-wrapper service, and it is not padded with redundant endpoints. Still, one tool carrying answer generation, source/citation extraction, search-query reporting, and brand-position checking feels thin and overloaded for the scope implied by the description.
The core operation — ask a question, get answer plus sources and citations — is fully covered, including a no-key trial path. Gaps remain: no way to continue a conversation or ask follow-ups, no batch/multi-question call, and no retrieval of earlier answers, which agents doing iterative research would need.