LopeBase
com.lopebasev0.4.3Updated Oct 6, 2026
Your products' traffic, revenue, uptime, and content, from your LopeBase workspace.
Overview
AI-generated overview
Lets an assistant read traffic, revenue, uptime, and content data from a LopeBase workspace.
- What it does
- LopeBase exposes a workspace's product data to an assistant, covering traffic, revenue, uptime, and content. It runs either as a remote endpoint at a workspace-specific LopeBase host or as a local npm package over stdio. The manifest lists no tools, so the exact operations are not documented here.
- When to use it
- Consider it when you want an assistant to answer questions about a LopeBase workspace's site traffic, revenue, uptime, or content without switching to the dashboard. It is only useful if you already use LopeBase.
- Requirements
- A LopeBase workspace, since the remote endpoint is addressed per workspace. Either network access to that endpoint or Node.js to run the npm package locally. The manifest declares no authentication and no environment variables or headers.
Before you install
The manifest declares no authentication, so confirm how access to your workspace data is actually controlled before connecting. The data covers traffic, revenue, and uptime, which is business-sensitive; check what is sent to the assistant and where it is processed.
Installation
In SourceWeft
- Open LopeBase in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"lopebase": {
"type": "http",
"url": "https://{workspace}.lopebase.com/api/mcp"
}
}
}Tools
0Tool metadata has not been indexed yet.
Version history
1- v0.4.3LatestOct 6, 2026


