Perplex MCP Server
jcmrs/perplex
Orquestra Claude, Gemini e Perplexity para pesquisa colaborativa em IA
Ver no GitHubUm servidor MCP que integra Claude, Gemini CLI e Perplexity AI para colaboração centrada em IA. Funciona como orquestrador de pesquisa e análise, permitindo que múltiplos modelos trabalhem em conjunto através de automações GitHub Actions.
Instalação
npx convez-ai jcmrs/perplex1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Automação de validação de PRs com múltiplos modelos de IA
- Pesquisa integrada com capacidades de diferentes plataformas de IA
- Pipelines de desenvolvimento que requerem análise multi-modelo
Veredito

Projeto experimental que busca federar três plataformas de IA distintas. Atualmente focado em automações GitHub Actions; ainda em estágio exploratório quanto à integração prática das capacidades de pesquisa do Perplexity com Claude e Gemini.
README
A tradução para o português deste README ainda está na fila.
GitHub Integration Files
This directory contains GitHub-specific configuration and automation.
Structure
.github/
├── workflows/ # GitHub Actions workflows
│ └── foundation-validation.yml # PR validation
├── ISSUE_TEMPLATE/ # Issue templates
├── pull_request_template.md # PR template
├── CODEOWNERS # Code ownership rules
└── README.md # This file
GitHub Actions Workflows
foundation-validation.yml
Triggers: Pull requests to main, pushes to main Purpose: Validates foundation alignment on every PR Checks:
- Runs
tools/validate-foundation.sh - Ensures no uncommitted changes
- Blocks PR merge if validation fails
Why: Replicates local pre-commit hooks on GitHub's side. Local hooks only run on individual machines - GitHub Actions ensures validation happens on all PRs regardless of local setup.
Templates
Pull Request Template
Provides structured format for PR descriptions including:
- Summary of changes
- Links to ADRs
- Traceability to requirements/vision
- Validation performed
Issue Templates
Structured formats for:
- Bug reports
- Feature requests
- Questions
- Other issue types
Code Ownership
CODEOWNERS file defines who reviews changes to specific files/directories.
For AI Agents
GitHub Actions workflows run automatically - you don't trigger them manually. When you create a PR, GitHub runs these checks.
If validation fails:
- Review the GitHub Actions log
- Fix the issues locally
- Commit fixes
- Push to PR branch
- GitHub re-runs validation automatically
For Humans
GitHub Actions provide automated quality gates. PRs can't merge until checks pass, ensuring foundation standards are maintained automatically.
Note: GitHub Actions workflows are configured here but execute on GitHub's infrastructure, not locally.