Connects AI coding clients to analytics, search, health-check, and digest data across one LopeBase workspace.
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent โ or use 1-click editor setup below.
We haven't yet run this listing's install command through our automated sandbox check. This isn't a red flag โ we're steadily working through the catalog.
๐ก Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
Inspect callable tools, capabilities, and parameters exposed to AI agents by LopeBase.
The LopeBase MCP server gives an AI agent access to data from multiple products in a LopeBase workspace. Supported sources are Google Search Console, Bing, Google Analytics 4, PostHog, Plausible, and Cloudflare Web Analytics. Rather than connecting each product separately, the server provides one MCP connection for the workspace.
The service also includes workspace-level health checks and a weekly digest across the connected products. This makes it suitable for agents that need to review search visibility, website analytics, product analytics, or the general state of several data sources together.
LopeBase runs as an MCP server started with npx lopebase. The command is intended to run from a project folder, where it can be used to connect an MCP-compatible client. The supplied client list includes Claude Code, Codex, Gemini CLI, opencode, and Cursor Agent.
Once connected, the agent can use the server to work with the products available in the relevant LopeBase workspace. The workspace is the organizing scope for the supported product data, health checks, and weekly digest. The available material does not describe a separate server for each product or provide product-specific connection commands.
Start the LopeBase MCP server by running the following command in a project folder:
The command is documented for use with Claude Code, Codex, Gemini CLI, opencode, and Cursor Agent. The provided information does not specify environment variables, authentication flags, configuration files, required account permissions, or separate setup steps for individual data sources. Those details should be confirmed in the product documentation before automating deployment or onboarding additional workspace products.
The LopeBase MCP server covers these capability areas:
The description does not enumerate individual MCP tool names or state which queries, filters, mutations, or reporting dimensions each product supports. It should therefore be evaluated as a unified access point for the listed product data and workspace summaries, rather than assumed to provide any particular undocumented operation.
The LopeBase MCP server is most relevant when an agent needs to compare or review multiple analytics and search systems from one workspace connection. It can also support recurring review workflows that use health checks or the weekly digest, provided those features are available for the workspace being connected.
Factual signals from GitHub, npm, and our automated checks โ not a rating.
No reviews yet โ be the first to share how this listing worked for you.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/lopebase)<a href="https://allmcps.com/mcp/lopebase"><img src="https://allmcps.com/api/badge/lopebase?style=directory" alt="LopeBase on AllMCPs" /></a>