LiftMCP
LiftMCP is a MCP server that exposes each configured website property as its own hosted MCP endpoint so AI agents can work with that site in a structured way.
About
LiftMCP (com.liftmcp/platform) is a hosted Model Context Protocol server that makes individual websites AI-agent-ready. Each LiftMCP property gets its own remote endpoint on streamable HTTP, parameterized by your property slug from the dashboard. developers shipping marketing sites, docs, or SaaS surfaces can register properties so coding agents connect without self-hosting MCP infrastructure. The catalog positions it in launch for AI and agent visibility rather than as a generic scraping plugin. You configure the slug variable when adding the remote in Claude Code, Cursor, or other MCP clients. Fit is strongest when you already manage sites in LiftMCP and want agents to interact with that property’s curated tools and content boundary, not when you only need ad-hoc browser automation on arbitrary URLs.
- Per-property hosted MCP server at a slug-based streamable-http URL
- No local install—remote MCP only; property_slug comes from LiftMCP property settings
- MCP schema 2025-12-11; server version 1.0.0
- Open-source repo: github.com/billmacuk/LiftMCP
- MCP integration for exposing live web properties to agents, not a codegen skill
LiftMCP by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
claude mcp add --transport http platform https://{property_slug}.mcp-dev.liftmcp.com/Add your badge
Show developers this MCP server is listed on Skillselion. Paste this into your README.
| Transport | HTTP |
|---|---|
| Auth | None |
What it does
Give each site or product property its own hosted MCP endpoint so Claude or Cursor can read and act on that site like a first-class tool.
Who is it for?
Best when you run one or more sites on LiftMCP and want Claude Code or Cursor to integrate with a dedicated remote per property.
Skip if: Skip if you need a self-hosted MCP for arbitrary internal APIs with no LiftMCP property, or developers and only need casual web fetch without a managed agent-ready layer.
What you get
After you add your property slug remote in your MCP client, agents can call your LiftMCP-hosted server for that site without running local MCP code.
- Agent-callable MCP remote URL for one LiftMCP property
- Structured agent access to that property without local MCP hosting
By the numbers
- Server version 1.0.0 per server.json
- Single streamable-http remote with required property_slug variable
- Repository: github.com/billmacuk/LiftMCP
Recommended MCP Servers
0Latency MemoryPersistent memory layer for AI agents.
0nMCP — Universal AI API OrchestratorUniversal AI API Orchestrator — 1,554 tools, 96 services.
0xHumans Protocol MCPMCP for AI agents: financing, skills, lending on Base1k Patient Mcp1k patient MCP server
1trippulse1trip PULSE: 21-tool AI travel planner.
3D AI Agent Avatar3D AI Agent Avatar — render any GLB, give it a Solana wallet, a voice, and pump.fun powers.89How it compares
Hosted per-site MCP exposure, not a local filesystem or repo-only developer skill.
FAQ
Who is LiftMCP for?
Developers and small teams who use LiftMCP properties and want AI coding agents to connect via MCP to each site’s hosted server.
When should I use LiftMCP?
Use it at launch when you are making a site agent-accessible and already have a property slug from LiftMCP settings.
How do I add LiftMCP to my agent?
Register the streamable-http remote https://{property_slug}.mcp-dev.liftmcp.com/ in your MCP client and set property_slug to the value from your Property settings.