Productivity
lufer.ai
MCP server for accessing pricing, case studies, booking calls, and submitting sales leads.
ENDPOINT 1
https://lufer.ai/mcp
MCP server metadata
- Name
- Lufer AI MCP Server
- Version
- 0.1.0
Sales + discovery surface for Lufer AI. Tool inventory and maturity at https://lufer.ai/.well-known/mcp.json. Full agent skill at https://lufer.ai/.well-known/skills/lufer-ai/SKILL.md.
Known tools 4
getPricingReturns current plan pricing + billing cadence (Starter / Pro / Enterprise).
Inferred read-onlylistCasesLists recent shipped case studies with metrics (client, vertical, headline, body, 3 metrics each).
Inferred read-onlyrequestQuotePersists a lead to Cloudflare D1 and dispatches a notification email to the sales inbox.
Potential side effectsCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.lufer-ai-mcp-server]
url = "https://lufer.ai/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"lufer-ai-mcp-server": {
"type": "http",
"url": "https://lufer.ai/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: lufer-ai-mcp-server
Remote MCP URL: https://lufer.ai/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"lufer-ai-mcp-server": {
"url": "https://lufer.ai/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"lufer-ai-mcp-server": {
"type": "http",
"url": "https://lufer.ai/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "lufer-ai-mcp-server",
"transport": "streamable-http",
"url": "https://lufer.ai/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Trust Data Available
BuiltWith Trust API v2 evidence for lufer.ai was fetched 2026-07-31T07:50:36.973Z and is being refreshed.
lufer.ai is assessed as Neutral: No suspicious signals found, but no strong positive signal either
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.