Skip to main content
Glama
laodev1

Perplexity MCP Server

by laodev1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Perplexity MCP Server

No user-submitted related servers found.

    Related Servers

    • Perplexity MCP Server

      Family-IT-Guy
      A
      license
      Not graded
      quality
      F
      maintenance
      A custom Model Context Protocol implementation that integrates Perplexity AI with Claude Desktop, allowing users to access Perplexity's AI models for both single questions and multi-turn conversations.
      26 npm
      15
      ISC

    • Kagi MCP

      yuki-yano
      A
      license
      B
      quality
      D
      maintenance
      A Node.js implementation of the Kagi Model Context Protocol server that enables Claude AI to search the web and summarize documents, videos, and audio using Kagi's APIs.
      2
      18 npm
      MIT

    • Perplexity MCP Server

      shaunmacfullstack
      A
      license
      Not graded
      quality
      D
      maintenance
      Exposes Perplexity AI's search capabilities to Claude, enabling real-time web search and information retrieval within the assistant. The project is currently in active development with plans to support Perplexity Spaces and multi-source data synthesis.
      Apache 2.0

    • Example MCP Server

      Ranjith63812
      A
      license
      Not graded
      quality
      D
      maintenance
      A Node.js and TypeScript implementation that provides system information and health check tools for Claude Desktop. It serves as a boilerplate for building and integrating custom tools using the Model Context Protocol.
      6 npm
      ISC
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    C2.9/5.0

    Scored across 2 tools

    Disambiguation2/5

    Both tools involve querying Perplexity AI, with only subtle differences in description ('simple query' vs 'chat completion'). An agent would likely struggle to decide which to use, as the boundaries are unclear.

    Naming Consistency4/5

    Both tools follow a consistent 'perplexity_<verb>' pattern. The verbs 'ask' and 'chat' are different but semantically related, and no mixing of naming conventions is present.

    Tool Count3/5

    With only 2 tools, the server feels minimal for a service like Perplexity AI, which typically offers more nuanced capabilities (e.g., different models, streaming). However, it covers basic query and chat needs.

    Completeness3/5

    The tool surface covers basic query and chat interactions but lacks operations such as specifying model parameters, context handling, or result streaming. This may limit agent flexibility.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources