INDIVIDUAL MCP TOOL

search_tools

Search the Kbaise directory of tools that work with Lovable projects.

kbaise.comnone authenticationAvailability not checked

LIVE ENDPOINT

https://kbaise.com/api/public/mcp

No auth detected

Connect to this endpoint to inspect the live schema for search_tools and invoke it with your own arguments.

{}

Inferred read-only · medium confidence · heuristic, not a guarantee.

No write-capable action terms were found; this is not proof that invocation has no side effects.

CONNECT WITH APPROVAL

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.kbaise]
url = "https://kbaise.com/api/public/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "kbaise": {
      "type": "http",
      "url": "https://kbaise.com/api/public/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: kbaise
Remote MCP URL: https://kbaise.com/api/public/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": {
    "kbaise": {
      "url": "https://kbaise.com/api/public/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "kbaise": {
      "type": "http",
      "url": "https://kbaise.com/api/public/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "kbaise",
  "transport": "streamable-http",
  "url": "https://kbaise.com/api/public/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

get_tool — Full dossier for one tool by slug: what it is, why it is picked, the trap to avoid, install notes, pricing and link health.
recommend_stack — Describe what you are building and get a recommended stack by role, with the traps to avoid and a paste-ready brief.
latest_model_updates — Recent official posts from OpenAI, Anthropic and Google.
compare_tools — Put 2-4 tools head to head: cost, why builders pick each, the trap, and how to wire it up.
decision_history — What Lovable builders actually shipped after comparing these tools, with the one-line reasons they gave.
audit_stack — Audit an existing stack: paste a package.json, dependency list, or prose.
community_stacks — Tool line-ups published by Lovable builders, most endorsed first.
trending_tools — Anonymous aggregate demand signal: which tools Lovable builders looked up in the last 7 days and which head-to-head comparisons they ran in the last 30.