Connect Your AI Assistant to Your GEO Platform
Visiblie MCP Server brings Generative Engine Optimization directly into Claude, Cursor, and any MCP-compatible AI assistant. Monitor brand visibility, run audits, and optimize content—all from your coding environment.
Built on the open standard
“Model Context Protocol (MCP) is the open standard for AI-tool integrations”
What is the Visiblie MCP Server?
A secure, OAuth-enabled bridge between your AI coding assistant and the Visiblie GEO platform. Ask questions, run audits, check visibility—all without leaving your IDE.
For Developers
Add Visiblie tools directly to Claude Code, Cursor, or any MCP-compatible environment. No context switching. No copy-paste. Natural language commands for your entire GEO workflow.
- Works in Claude Desktop, Claude.ai, Cursor, and more
- OAuth 2.0 authentication—no raw API keys in config files
- 18+ tools for visibility tracking, audits, and optimization
For Teams
Every team member gets the same Visiblie capabilities in their preferred AI assistant. Standardize GEO workflows, share configurations, and maintain consistent brand optimization across your org.
- Team-wide OAuth credentials from Agency Settings
- Unified access to brand data, audits, and recommendations
- Track API usage per key from the Visiblie dashboard
Setup in 3 Minutes
Connect once, use everywhere. OAuth keeps your credentials secure.
Generate OAuth Credentials
Go to your Agency Settings, select an API key, and generate OAuth credentials for MCP.
Add to Your AI Assistant
For Claude Desktop: Settings → Connectors → Add custom connector
For Claude CLI: Run claude mcp add --transport http visiblie https://mcp.visiblie.com/mcp --header "Authorization: Bearer YOUR_API_KEY"
Start Using Visiblie
Ask Claude to run visibility checks, audits, and optimizations using natural language.
18+ Tools at Your Command
Everything you need to monitor, analyze, and optimize your AI presence
Brand Visibility
Track mentions across AI platforms
Visibility Score
Real-time GEO metrics dashboard
Website Audit
Technical SEO + GEO analysis
AI Citations
Track source citations in AI responses
Competitor Analysis
Compare your visibility vs competitors
Recommendations
Actionable GEO optimization steps
Integrations
Manage platform connections
Brand Registration
Register brands programmatically
Secure Auth
OAuth 2.0 with token refresh
Security First
Enterprise-grade authentication and data protection
OAuth 2.0 Authorization
- Authorization Code Flow with PKCE—industry standard for secure OAuth
- No API keys in config files—credentials stored in system keychain
- Token expiry and refresh—automatic token rotation every hour
- Scoped access—tokens limited to MCP scope only
Enterprise Security
- HTTPS only—all communication encrypted in transit
- Encrypted API keys—secrets stored with AES-256 encryption at rest
- Audit logs—track every API request by key and timestamp
- Instant revocation—delete compromised keys with immediate effect
SOC 2 Type II Compliant
Visiblie's infrastructure meets SOC 2 Type II security standards. Regular penetration testing, encrypted backups, and access controls ensure your brand data stays protected.
What You Can Do
Real-world workflows teams use every day
Monitor Brand Mentions During Standup
"Check my brand visibility across ChatGPT, Claude, and Perplexity"
Instant report showing current visibility score, platform breakdown, and week-over-week changes
Run Pre-Launch SEO Audit
"Run a full GEO audit for staging.example.com and show me the top 5 issues"
Technical audit covering crawlability, schema markup, AI citability, and actionable fixes
Compare Against Competitors
"How does our AI visibility compare to competitor.com?"
Side-by-side analysis of visibility scores, citation frequency, and recommendation rates
Track Citation Sources
"Where is ChatGPT citing us this week?"
List of source URLs, citation frequency, and context in which your brand appears
Get Optimization Recommendations
"What are our top 3 GEO improvements for Q2?"
Prioritized action items based on visibility gaps, competitor analysis, and platform trends
Register New Brand Automatically
"Register example.com as a new brand in Visiblie"
Brand created, initial audit queued, and confirmation with brand ID
Technical Details
Protocol Compliance
- MCP Specification: Full Model Context Protocol v2024-11-05 support
- Transport: Streamable HTTP (SSE deprecated per Anthropic guidance)
- OAuth: RFC 6749 (Authorization Code), RFC 8414 (Metadata), RFC 9728 (Protected Resource)
- PKCE: S256 and plain code challenge methods supported
Performance & Limits
- Response time: <500ms average for most tool calls
- Token limit: 25,000 tokens per tool response (per Connector Directory requirements)
- Timeout: 5 minute maximum per tool call
- Rate limits: Follows your Visiblie plan tier (500-5000 req/hr)
Supported AI Assistants
Developer-Friendly Integration
Choose your setup method
Claude CLI Setup
Recommended for developers# Add Visiblie MCP server with Bearer token
claude mcp add --transport http visiblie https://mcp.visiblie.com/mcp \
--header "Authorization: Bearer YOUR_API_KEY"
# Verify connection
claude mcp list
# Start using
claude
> "Check my brand visibility score"Claude Desktop Setup (OAuth)
Recommended for teams# 1. Generate OAuth credentials
curl -X POST https://mcp.visiblie.com/oauth/register \
-H "Content-Type: application/json" \
-d '{"visibleApiKey":"YOUR_VISIBLIE_API_KEY"}'
# Response:
# {
# "client_id": "client_abc123...",
# "client_secret": "xxxxxxxxxxxxxx"
# }
# 2. Add to Claude Desktop:
# Settings → Connectors → Add custom connector
# - Name: Visiblie
# - URL: https://mcp.visiblie.com/mcp
# - Paste Client ID and Secret
# - Click "Connect"
# 3. Authorize when prompted (redirects to OAuth flow)Or Generate via Agency Settings UI
- 1. Go to Agency Settings → Developer API
- 2. Scroll to "OAuth Credentials for Claude Desktop"
- 3. Select your API key and click "Generate OAuth Credentials"
- 4. Copy the Client ID and Secret from the dialog
- 5. Add to Claude Desktop as shown above
Frequently Asked Questions
What AI assistants are supported?
Visiblie MCP Server works with any MCP-compatible assistant: Claude Desktop, Claude.ai (via Custom Connectors), Claude CLI, Cursor IDE, Windsurf, and more. The same server works across all clients.
Is my API key secure with MCP?
Yes. With OAuth authentication, your API key never leaves the Visiblie server. The OAuth flow generates short-lived access tokens (1 hour expiry) that are automatically refreshed. Keys are stored encrypted in your system keychain, not in config files.
Do I need a paid Claude account?
For Claude Desktop and Claude.ai Custom Connectors, yes—Pro, Max, Team, or Enterprise. For Claude CLI and Cursor, no paid account needed. The MCP server itself works with any plan.
Can I use this for my agency clients?
Yes. Generate separate OAuth credentials for each client using their respective Visiblie API keys. Each credential set is isolated and can be revoked independently from Agency Settings.
What data does the MCP server access?
The MCP server accesses the same data as the Visiblie web app: brand visibility scores, audit results, competitor analysis, citations, and recommendations. It respects your plan limits and brand permissions.
How do I revoke access?
Delete the API key from Agency Settings → Developer API. This immediately revokes all OAuth tokens derived from that key. Or remove the connector from your AI assistant settings.
Does this work with the Visiblie API?
The MCP server wraps the Visiblie REST API. If you prefer direct API access (for custom integrations, webhooks, etc.), use the same API keys with our REST endpoints. MCP is for AI assistant integration specifically.
Is there a rate limit?
MCP requests count against your plan's API rate limit (500-5000 requests/hour depending on tier). Check current usage in the Visiblie dashboard under Agency Settings → Developer API.
Ready to Connect?
Get Visiblie tools in your AI assistant in under 3 minutes.