Foglift
Integration · Model Context Protocol
Hosted Foglift MCP Server
Connect Foglift to an MCP client through a hosted remote URL and OAuth. Run Technical Audits, AI Visibility checks, recommendations, content briefs, setup guidance, and recipes from the agent without copying API keys into a config file.
Recommended: hosted remote MCP + OAuth
The hosted endpoint is the easiest path for clients that support remote MCP servers and OAuth. Add this server URL:
https://mcp.foglift.io/api/mcp
- 1. Add the remote MCP URL in your client's connector or MCP server settings.
- 2. Authorize Foglift through the browser OAuth flow. The live issuer is
https://mcp.foglift.io. - 3. Verify the session by asking the client to call
whoamiorget_usage.
OAuth authorization requires a Foglift account. Create a free account first if you have not connected Foglift before.
Verified June 11, 2026: https://mcp.foglift.io/.well-known/oauth-authorization-server returns OAuth authorization, token, and dynamic-client-registration endpoints. https://mcp.foglift.io/.well-known/oauth-protected-resource advertisesresource: https://mcp.foglift.io/api/mcp.
Local stdio setup for Cursor, Windsurf, and power users
Some clients still expect MCP servers to run as local commands. For those clients, keep using the npm package with an API key. This is the right path for Cursor and Windsurf today, and it remains useful when you want all traffic to originate from your own machine.
1. Generate an API key
Sign up at foglift.io, then go to Dashboard > Settings > API Keys. Free accounts can create keys.
2. Add the stdio server
{
"mcpServers": {
"foglift": {
"command": "npx",
"args": ["-y", "foglift-mcp"],
"env": { "FOGLIFT_API_KEY": "sk_fog_..." }
}
}
}3. Restart and verify
Restart the client and ask it to call get_usage or scan_website. You should see structured account or scan data in the agent response.
Current hosted tool inventory
A live tools/list call against https://mcp.foglift.io/api/mcp returned 24 tools on June 11, 2026. The hosted endpoint includes Actions Engine and setup tools that are newer than the original npm-only page described.
scan_websiteScan one URL for SEO, AI Readiness, performance, security, and accessibility signals. Public scans do not require a key.
batch_scanScan up to 10 URLs in one request for competitor sweeps or release checks.
run_ai_visibilityQuery ChatGPT, Claude, Perplexity, Gemini, and Google AI Overview for brand mentions and citations.
get_ai_resultsPull historical AI Visibility results with filters for date range, model, prompt, and pagination.
get_promptsList saved monitoring prompts for the connected brand.
add_promptAdd a new prompt to the AI Visibility monitoring set.
delete_promptRemove a saved prompt by ID.
get_modelsRead enabled AI engines and monitoring cadence for the account.
set_modelsUpdate enabled engines and monitoring cadence.
get_sentimentShow sentiment trends for AI mentions across a chosen window.
get_usageRead plan, quota, scan usage, and token balance.
get_scan_historyShow score history for a specific URL.
get_geo_monitorRead legacy monitoring history for AI search optimization scores.
get_referrer_analyticsReport AI-engine referral visits by engine, landing path, and day.
estimate_costEstimate token and dollar cost before running a scan or AI Visibility check.
get_recommendationsFetch source-tagged Actions Engine recommendations for the connected brand.
submit_recommendationSubmit a recommendation or action item back into the workflow.
apply_recommendationApply supported setup or content recommendations through the agent.
generate_content_briefGenerate a content brief from the monitored brand, prompt, and competitive context.
report_issueSend structured product feedback or a support issue from the MCP client.
whoamiConfirm which Foglift account and brand the MCP session is connected to.
recommend_setupAsk Foglift for setup improvements for the current account or brand.
apply_setup_recommendationApply supported setup fixes after reviewing them.
recipe_runRun a named Foglift recipe such as a weekly brand health report. Uses the underscore tool name.
Three workflows worth automating
Audit a release candidate
“Use scan_website on the preview URL, then summarize the lowest AI Readiness, SEO, and accessibility signals in a table.”The agent gets the same structured scan data the dashboard uses, then turns it into a release checklist inside the same session.
Find the next content fix
“Callget_recommendationsandget_ai_results. Which prompt has competitor mentions and no Foglift mention, and what page should we improve first?”
This pairs the Actions Engine with live AI Visibility history, which is the same dogfooding loop Foglift uses on its own site.
Run a repeatable recipe
“Use recipe_run for the weekly brand health report, then turn the result into a short changelog entry.”Recipes make recurring AI search checks repeatable. The current tool name is recipe_run, with an underscore, so it works in clients that reject dotted tool names.
The closed-loop pattern: edit, scan, verify in one session
AI search optimization works best as a tight loop. The agent scans a page, identifies the missing citation or readiness gap, edits the page, re-scans after deploy, then pins the prompt that the page should win.
1. Baseline scan
Call
scan_websiteon the target URL and note the lowest score dimensions.2. Diagnose against visibility data
Call
get_ai_resultsandget_recommendationsto find the prompt and page with the clearest gap.3. Apply the page fix
Add FAQ schema, improve heading clarity, add a comparison table, cite primary sources, or strengthen internal links.
4. Re-scan after deploy
Run
scan_websiteagain and compare the new score against the baseline.5. Pin a tracking prompt
Use
add_promptso future monitoring tracks whether the page starts earning citations.
Foglift uses this loop internally. In a June 12, 2026 AI Visibility baseline, broad discovery prompts returned 0 Foglift mentions across 25 model checks. That is why developer-surface pages like this one matter: broad AI answers already cite tool roundups and developer workflows, so Foglift needs public pages that make its API, CLI, and MCP surfaces easy to extract.
Foglift MCP vs. other AI search optimization tools
MCP support across the AI search optimization category from the May 2026 parity review:
| Tool | Hosted OAuth MCP | Local MCP | Notes |
|---|---|---|---|
| Foglift | Yes, https://mcp.foglift.io/api/mcp | Yes, foglift-mcp on npm | Hosted endpoint returned 24 tools in the live check |
| Profound | No first-party hosted MCP found | No first-party local MCP found | REST API exists for enterprise workflows |
| Peec.ai | No first-party hosted MCP found | No first-party local MCP found | API surface can be wrapped by custom adapters |
| Otterly.ai | No first-party hosted MCP found | No first-party local MCP found | Dashboard and CSV workflows remain primary |
| Semrush AI Toolkit / Ahrefs Brand Radar | No AI-search-specific MCP found | No AI-search-specific MCP found | Large APIs, with MCP left to customer or community adapters |
See the supporting category review in Best AI Search Tools with MCP Integration 2026.
Frequently asked questions
How do I connect the hosted Foglift MCP server?
Add https://mcp.foglift.io/api/mcp as a remote MCP server in a client that supports hosted MCP and OAuth. The live server advertises OAuth discovery at https://mcp.foglift.io/.well-known/oauth-authorization-server. Complete the browser authorization flow, then call whoami or get_usage to verify the account.
Do I still need to install foglift-mcp from npm?
Use the hosted OAuth endpoint when your client supports remote MCP. Use the npm package when your client requires a local stdio command, or when you prefer to run the server locally with FOGLIFT_API_KEY in your environment.
Which clients work with the hosted OAuth endpoint?
The live allowlist includes Claude web callback origins and localhost OAuth callbacks used by local MCP clients and inspectors. Other remote MCP clients can work once their OAuth callback origin is allowlisted. Cursor and Windsurf remain best documented through the local npm stdio setup today.
What tools does the hosted Foglift MCP server expose?
The hosted endpoint returned 24 tools in a live tools/list check on June 11, 2026: scan_website, batch_scan, run_ai_visibility, get_ai_results, get_prompts, add_prompt, delete_prompt, get_models, set_models, get_sentiment, get_usage, get_scan_history, get_geo_monitor, get_referrer_analytics, estimate_cost, get_recommendations, submit_recommendation, apply_recommendation, generate_content_brief, report_issue, whoami, recommend_setup, apply_setup_recommendation, recipe_run. The canonical recipe tool is recipe_run with an underscore.
Is Foglift MCP free?
Connecting the MCP server is free. Tool calls consume Foglift account quota. Public scan_website calls can run without an API key, while account, brand, recommendation, recipe, and monitoring tools require an authorized Foglift account.
How is Foglift MCP different from the Foglift CLI?
The CLI is built for humans and scripts in a terminal. MCP is built for AI agents. MCP exposes typed tools over the Model Context Protocol so the agent can choose when to scan, retrieve results, create prompts, generate briefs, or run recipes inside the same work session.
What is the closed-loop AI Readiness pattern?
The closed-loop pattern means the agent scans a page, diagnoses the missing citation or readiness gap, edits the page, re-scans after deploy, and pins a tracking prompt. Foglift MCP keeps those steps in one agent session instead of splitting them across a dashboard, terminal, and spreadsheet.
Sources
- Foglift live MCP endpoint.
https://mcp.foglift.io/api/mcp,https://mcp.foglift.io/.well-known/oauth-authorization-server, andhttps://mcp.foglift.io/.well-known/oauth-protected-resource. Re-verified June 11, 2026. - Anthropic. Introducing the Model Context Protocol (November 2024).
- Anthropic. modelcontextprotocol/servers. Reference servers and client list.
- Foglift. foglift-mcp on npm. Local stdio package and version history.
Related
- All Foglift integrations REST API, CLI, Slack, Discord, webhooks, Zapier, n8n, and MCP.
- Developer documentation REST API reference, CLI guide, and developer workflows.
- API-first AI monitoring Why AI Visibility data should be callable from code and agents.
- Best AI Search Tools with MCP Integration 2026 How the category stacks up on agent readiness.
Connect the hosted MCP server
Use the remote URL for OAuth-capable clients, or install the npm stdio server for local clients.