Perplexity Ask MCP Server

Created By
ppl-aia year ago
A Model Context Protocol Server connector for Perplexity API, to enable web search without leaving the MCP ecosystem.
Overview

what is Perplexity Ask MCP Server?

Perplexity Ask MCP Server is a Model Context Protocol Server connector for the Perplexity API, enabling web search capabilities within the MCP ecosystem.

how to use Perplexity Ask MCP Server?

To use the server, clone the MCP repository, install dependencies, obtain a Sonar API key, configure the Claude desktop, build the Docker image, and test the integration.

key features of Perplexity Ask MCP Server?

  • Real-time web search integration with the Sonar API.
  • Easy configuration and setup for users.
  • Support for advanced search parameters.

use cases of Perplexity Ask MCP Server?

  1. Conducting live web searches without leaving the MCP environment.
  2. Enhancing research capabilities for users of the Claude desktop.
  3. Integrating web search functionalities into applications using the Perplexity API.

FAQ from Perplexity Ask MCP Server?

  • How do I get a Sonar API key?

Sign up for a Sonar API account and generate your API key from the developer dashboard.

  • Is there a troubleshooting guide available?

Yes, the Claude documentation provides a troubleshooting guide for common issues.

  • What license is the MCP server under?

The MCP server is licensed under the MIT License, allowing free use, modification, and distribution.

Server Config

{
  "mcpServers": {
    "perplexity-ask": {
      "command": "npx",
      "args": [
        "-y",
        "@chatmcp/server-perplexity-ask"
      ],
      "env": {
        "PERPLEXITY_API_KEY": "YOUR_API_KEY_HERE"
      }
    }
  }
}
Project Info
Hosted
Featured
Created At
a year ago
Updated At
a year ago
Author Name
ppl-ai
Star
222
Language
JavaScript
License
MIT license

Recommend Servers

View All
Payai X402 Tools

6 hours ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago