Ask your AI assistant about your brand’s AI search visibility and get answers from your actual Peec AI data. This works with Claude, Cursor, VS Code, Windsurf and others.Documentation Index
Fetch the complete documentation index at: https://docs.peec.ai/llms.txt
Use this file to discover all available pages before exploring further.
What you can do
- Check brand visibility across ChatGPT, Perplexity, Gemini, Google AI Overviews, Google AI Mode, Claude, Microsoft Copilot, and Grok
- Compare against competitors on the main metrics such as visibility, sentiment, share of voice, and position
- Analyze sources to see which domains and URLs AI models retrieve and cite most often, and how that shapes your content strategy
- Inspect source content by pulling the scraped markdown of any cited URL to see exactly what an AI engine read
- Spot trends by date, AI model, topic, or country to surface patterns and gaps to act on
- Get ranked next steps from Peec Actions: opportunity-scored recommendations grouped by owned pages, editorial coverage, reference sites, and UGC communities
- Run ready-made workflows with built-in prompts like the weekly pulse, engine scorecard, topic heatmap, and campaign tracker. One slash command, full report.
- Manage your project setup by asking the assistant to create, edit, or delete prompts, topics, tags, tracked brands, and custom domain/URL classifications. Works one at a time or in batches of up to 50. It always confirms before applying a change.
- Refine your brand profile so AI-generated prompt suggestions match how you actually describe your business.
How it works
Connect
Add the server URL to your AI tool. See our setup guide for your platform.
Ask questions or run a prompt
Free-form questions:
- “How has our brand visibility changed over the last 30 days?”
- “Which competitors have the highest share of voice in ChatGPT?”
- “What are our most cited URLs across AI search engines?”
Connection details
Your tool may ask for these details:| Property | Value |
|---|---|
| Server URL | https://api.peec.ai/mcp |
| Transport | Streamable HTTP |
| Authentication | OAuth 2.0 or Personal Access Token |
Authentication
Two options, depending on what your client supports:- OAuth 2.0. Your AI assistant opens a Peec AI consent page in your browser. Sign in and click Agree & Allow Access. The session persists across conversations.
- Personal Access Token. Create a token under API Keys → Personal Access Tokens in app.peec.ai, then attach it as an
Authorization: Bearer <token>header on your client’s MCP connection. Best for headless setups, CI, or clients without OAuth support.
The consent page shows which application is requesting access. You can switch accounts if needed.
Read and write access
Most tools are read-only. Reports, chat inspection, source content, and actions all pull existing data. A smaller set of tools edits your project configuration. The assistant uses them when you ask to add a prompt, rename a topic, or update a tracked brand. Every write tool is flaggedreadOnlyHint: false, and delete tools are flagged destructiveHint: true, so your client prompts for confirmation before the call runs. Write tools require organization-owner access on the project.
See tools for the full list.
Supported platforms
The MCP works with any tool that supports MCP (Model Context Protocol). Setup guides:- Claude (Desktop, Web, Code)
- Cursor
- VS Code (GitHub Copilot)
- Windsurf
Requirements
- A Peec AI account with at least one project
- A supported AI tool
