Perplexity MCP Server

Created By
wysh3a year ago
MCP web search using perplexity without any API KEYS
Overview

What is Perplexity MCP Server?

Perplexity MCP Server is a research-level Model Context Protocol (MCP) server that provides AI-powered research capabilities through Perplexity's infrastructure without the need for API keys.

How to use Perplexity MCP Server?

To use the Perplexity MCP Server, clone the repository, install the dependencies, build the server, and start it using npm commands. Configuration is required to integrate it with your MCP setup.

Key features of Perplexity MCP Server?

  • Web search integration via Perplexity
  • Use without any API Key
  • TypeScript-first implementation
  • Modular tool architecture

Use cases of Perplexity MCP Server?

  1. Conducting comprehensive web searches with adjustable detail levels.
  2. Retrieving up-to-date documentation and code examples.
  3. Discovering and evaluating APIs based on technical requirements.
  4. Analyzing code for deprecated patterns and providing migration guidance.
  5. Engaging in ongoing conversations with Perplexity AI.

FAQ from Perplexity MCP Server?

  • Is an API key required to use the Perplexity MCP Server?

No, the server can be used without any API key.

  • What programming language is used for the implementation?

The server is implemented in TypeScript.

  • What is the purpose of this project?

This project is intended for educational and research purposes only.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
wysh3
Star
4
Language
JavaScript
License
MIT license

Recommend Servers

View All
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.

25 minutes ago