Developer Tools

litefuse.ai

Provides access to Litefuse documentation via semantic search and page fetching for developers.

1 endpoint3 known toolsFirst detected September 9, 2026Last detected September 9, 2026

ENDPOINT 1

https://litefuse.ai/api/mcp

No auth detected

Capabilities

tools.listChanged

Semantic search (RAG) over the Litefuse documentation.

Inferred read-only

Fetch the raw Markdown for a single Litefuse docs page.

Inferred read-only

Get a high-level, machine-readable index by downloading https://litefuse.ai/llms.txt.

Inferred read-only

CONNECT WITH APPROVAL

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

Codex

~/.codex/config.toml

[mcp_servers.mcp-typescript-server-on-vercel]
url = "https://litefuse.ai/api/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "mcp-typescript-server-on-vercel": {
      "type": "http",
      "url": "https://litefuse.ai/api/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: mcp-typescript-server-on-vercel
Remote MCP URL: https://litefuse.ai/api/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": {
    "mcp-typescript-server-on-vercel": {
      "url": "https://litefuse.ai/api/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "mcp-typescript-server-on-vercel": {
      "type": "http",
      "url": "https://litefuse.ai/api/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "mcp-typescript-server-on-vercel",
  "transport": "streamable-http",
  "url": "https://litefuse.ai/api/mcp"
}

MCP Inspector

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

TRUST AND VERIFICATION EVIDENCE

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.