list_brandsLABSCO SUMMARY
AI-search visibility, and the page fix, in one place
Superlines hands an agent the numbers behind how your brand shows up in AI answers — visibility, citations, share of voice, competitor sentiment — and the same session can audit a live page and propose the markup change. It suits the team that wants the analysis and the next action in one conversation.
What it is
Superlines tracks how a brand appears in AI-powered search — ChatGPT, Perplexity, Gemini, Claude. This server connects an MCP client to that analytics data so visibility, citations and competitor standing can be asked for in natural language.
What you get
- Visibility and trend reads:
analyze_metrics,get_weekly_performance,get_period_comparison,get_analytics_summary. - Citation tracking:
get_citation_datafor domain and URL analysis,get_top_cited_url_per_promptfor per-query winners. - Competitor work:
analyze_brand_mentionswith sentiment scores,get_competitive_gap,get_competitor_insights,analyze_competitor_url. - Content direction:
get_query_data,find_content_opportunities,get_fanout_query_insights,analyze_sentiment. - Page auditing on any URL:
webpage_crawl,webpage_audit,webpage_analyze_technical,webpage_analyze_content. - Markup generation with
schema_optimizer. - Brand setup lookups through
list_brandsandget_brand_details.
Requirements
Node.js 18+ and a Superlines account on the Enterprise plan — MCP access is Enterprise-only. Create an API key in the dashboard under Organization Settings, then pass it as SUPERLINES_API_KEY in the client config.
Setup effort
One command plus a key — npm install -g @superlines/mcp-server, then supply credentials
USE CASES
Month-over-month visibility check
Read the current visibility numbers and compare them against the previous period.
Find who gets cited instead of you
See which domains and URLs AI answers cite for the queries you care about.
Size up a competitor
Pull their mentions with sentiment, then find the gap you could take.
Audit a page for AI search
Run the full LLM-friendliness audit on a URL and get the schema markup to fix it.
Decide what to write next
Surface topics with improvement potential and the queries feeding them.
22 tools
Listed in project docs. Your client may show a different list.
get_brand_detailsanalyze_metricsget_weekly_performanceget_period_comparisonget_analytics_summaryget_citation_dataget_top_cited_url_per_promptanalyze_brand_mentionsget_competitive_gapget_competitor_insightsget_best_performing_promptget_query_datafind_content_opportunitiesget_fanout_query_insightsanalyze_sentimentwebpage_crawlwebpage_auditwebpage_analyze_technicalwebpage_analyze_contentschema_optimizeranalyze_competitor_urlBEFORE YOU INSTALL
What to know first
Tools you get
22 tools named in the project's documentation.
Requires
- npx on PATH
- Node.js 18+
- SUPERLINES_API_KEY in your environment
INSTALLATION
Connect your client
Server setup
npm install -g @superlines/mcp-serverMCP Clients
Claude Desktop
{
"mcpServers": {
"superlines": {
"command": "npx",
"args": [
"-y",
"@superlines/mcp-server"
],
"env": {
"SUPERLINES_API_KEY": "<YOUR_SUPERLINES_API_KEY>"
}
}
}
}macOS: ~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json
Claude Desktop — macOS / Linux proxy
If you prefer not to use npx, you can download and run the proxy script locally.
mkdir -p ~/superlines-mcp
curl -o ~/superlines-mcp/mcp-proxy.js https://raw.githubusercontent.com/Superlines/mcp-server/main/mcp-proxy.js
chmod +x ~/superlines-mcp/mcp-proxy.js{
"mcpServers": {
"superlines": {
"command": "node",
"args": [
"/Users/<YOUR_USERNAME>/superlines-mcp/mcp-proxy.js"
],
"env": {
"SUPERLINES_API_KEY": "<YOUR_SUPERLINES_API_KEY>"
}
}
}
}Claude Desktop — Windows proxy
If you prefer not to use npx, you can download and run the proxy script locally.
mkdir $env:USERPROFILE\superlines-mcp
Invoke-WebRequest -Uri "https://raw.githubusercontent.com/Superlines/mcp-server/main/mcp-proxy.js" -OutFile "$env:USERPROFILE\superlines-mcp\mcp-proxy.js"{
"mcpServers": {
"superlines": {
"command": "node",
"args": [
"C:\\Users\\<YOUR_USERNAME>\\superlines-mcp\\mcp-proxy.js"
],
"env": {
"SUPERLINES_API_KEY": "<YOUR_SUPERLINES_API_KEY>"
}
}
}
}Cursor
{
"mcpServers": {
"superlines": {
"command": "npx",
"args": [
"-y",
"@superlines/mcp-server"
],
"env": {
"SUPERLINES_API_KEY": "<YOUR_SUPERLINES_API_KEY>"
}
}
}
}.cursor/mcp.json (project or global)
Continue
{
"mcpServers": [
{
"name": "superlines",
"command": "npx",
"args": [
"-y",
"@superlines/mcp-server"
],
"env": {
"SUPERLINES_API_KEY": "<YOUR_SUPERLINES_API_KEY>"
}
}
]
}Any MCP client — Global install
{
"mcpServers": {
"superlines": {
"command": "superlines-mcp",
"env": {
"SUPERLINES_API_KEY": "<YOUR_SUPERLINES_API_KEY>"
}
}
}
}