Liftaven

io.github.liftavenPublished by GitHub account liftavenv1.1.1Updated Oct 24, 2026

MCP connector for Liftaven SEO research, connected search reports and reviewed website proposals.

VerifiedStreamable HTTPWeb executableProductivity & Workflow Web Search & Scraping Data & Analytics

Server details

Identifier: io.github.liftaven/mcp-server
Transport: Streamable HTTP
Runtime: Web executable
Trust: Verified
Published: Sep 22, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account liftaven for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.liftaven%2Fmcp-server.svg)](https://sourceweft.com/mcp/io.github.liftaven%2Fmcp-server?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Liftaven connects an assistant to SEO research: search performance reports, connected Search Console and Analytics data, and website change proposals for…

What you can do: Check connection status and which providers and accounts are ready before requesting reports
Inspect the live tool catalogue and run operations from connected providers such as Search Console and Analytics
Compare search performance periods and rank pages or opportunities by evidence
Prepare supported website changes as proposals that a person reviews and approves in Liftaven
Submit supported sitemap actions when explicitly requested
When to use it: Useful for founders, small teams and website owners who want an assistant to read their search and analytics data, explain what it shows, and draft concrete on-page improvements that still go through human review in Liftaven.
Requirements: A Liftaven account and a client that supports Streamable HTTP MCP with OAuth, or Node.js 22 or newer for the local stdio bridge via npx. Sign-in happens in the browser with a consent screen; the connector uses a fixed hosted endpoint and needs network access.

Before you install

OAuth tokens stored locally are credentials, and the consent screen grants access to connected provider data. Website proposals and sitemap submissions change site content or settings, so review them in Liftaven before applying; the assistant cannot approve its own proposal. Recommendations do not guarantee rankings or traffic.

Installation

In SourceWeft

Open Liftaven in the dashboard and add it to a workspace.
Connect the required credentials. They are stored privately and never shown on public pages.
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.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.liftaven%2Fmcp-server/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "liftaven": {
      "type": "http",
      "url": "https://mcp.liftaven.com/mcp"
    }
  }
}

README

Liftaven MCP

SEO research that leads to reviewed website improvements.

Liftaven helps founders, small teams and website owners turn search data into a practical next step. Start with a public website check, add Search Console and Analytics for context, and keep research, conversations and content drafts together. When an improvement is ready, review it in the workspace before applying it through a connected editor.

Website · MCP repository · Agent skill · npm package

What this connector does

This package connects a local stdio MCP client to the hosted Liftaven MCP server. Hosted tools run on Cloudflare; the local package bridges the connection and opens browser-based OAuth. You do not need to deploy a Worker or paste a product password into your assistant.

Tool	What it does
`connection_status`	Check connected providers and account readiness before requesting reports.
Discovered provider tools	Inspect the current MCP catalogue, then select the appropriate Search Console, Analytics or other connected-provider operation.
Website proposal workflow	Prepare supported changes for review in Liftaven. The assistant cannot approve its own proposal.

Tool availability depends on connected providers and account permissions. Inspect the live catalogue instead of assuming every provider is connected. Supported sitemap submissions are actions and should happen only when requested. Website proposals retain human review; recommendations do not guarantee rankings or traffic.

Example workflow

Check the connected website, provider accounts and available tools.
Compare the latest complete 28 days with the previous 28 using the same property, filters and dimensions.
Rank a few opportunities by evidence, inspect the current page, and propose a concrete improvement for review.

Things to ask your assistant

Review my last 28 complete days of search performance. Which three pages deserve attention first, and why?

Compare search clicks with landing-page engagement. Separate what the data shows from your explanation.

Prepare a title improvement for this page, with supporting evidence, for me to review in Liftaven.

Connect a remote MCP client

Open the client’s custom MCP or connector settings.
Enter https://mcp.liftaven.com/mcp as the remote server URL.
Complete Liftaven sign-in in your browser and review the permissions on the consent screen.
Return to the client and load the available tools.

Use a client that supports Streamable HTTP MCP and OAuth. Custom-connector availability depends on the client and your account. A public repository or npm release does not mean the integration has been approved for a client’s marketplace.

Claude Desktop and other stdio clients

Requires Node.js 22 or newer and an existing Liftaven account. Add this entry to your client’s MCP configuration:

json

{  "mcpServers": {    "liftaven": {      "command": "npx",      "args": [        "-y",        "liftaven-mcp"      ]    }  }}

{  "mcpServers": {    "liftaven": {      "command": "npx",      "args": [        "-y",        "liftaven-mcp"      ]    }  }}

You can also run npx -y liftaven-mcp from a terminal to start the bridge. It speaks MCP over stdio; it is not an interactive chat interface. For desktop clients that support MCPB extensions, download the .mcpb file from Liftaven releases.

Permissions and account access

The live catalogue reflects the providers connected to your Liftaven workspace. Check connection_status first and review the consent screen before approving access.

Only approve a connection you intended to start. If sign-in opens a new tab, finish it, return to the consent screen and refresh. Manage providers and agent access in Liftaven.

The package uses pinned mcp-remote for OAuth, PKCE and local token storage. Tokens on your computer are credentials. The connector uses the fixed endpoint above and rejects command-line endpoint overrides. Product passwords and underlying provider credentials are not requested by this package.

Troubleshooting

No tools or insufficient permissions: reconnect through browser consent and check the selected account.
An empty list: confirm that the account owns the expected items. Empty results are different from a failed request.
A link asks you to sign in: open it with the owning product account; a private product link is not a public share link.
The browser blocks authorization: inspect the browser’s displayed error and restart an expired request from the client. Never send cookies or tokens in an issue.

Add the companion skill

The Liftaven agent skill explains how to select the right records, interpret results and respect the workflow’s limits:

Learn more about Liftaven

Development and support

Report a connector issue with your client, Node.js version and a redacted error. Keep package.json, manifest.json, server/config.json, server.json and the lockfile version aligned for releases. GitHub Actions publishes versioned npm packages and MCPB assets. See LICENSE for the MIT license.

Source: README.md at commit 92f255c

Tools

This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

v1.1.1LatestSep 22, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts