LiteAPI MCP Server

Created By
liteapi-travela year ago
Overview

what is LiteAPI MCP Server?

LiteAPI MCP Server is a development server designed for building and testing applications using the LiteAPI framework.

how to use LiteAPI MCP Server?

To use the LiteAPI MCP Server, you can run the server for development using the command npm run dev, or you can run the server along with an inspector using npm run inspect.

key features of LiteAPI MCP Server?

  • Easy setup for development environments
  • Ability to run server and inspector simultaneously
  • Configuration options for custom server commands

use cases of LiteAPI MCP Server?

  1. Developing applications using the LiteAPI framework
  2. Testing API endpoints during development
  3. Debugging applications with the inspector tool

FAQ from LiteAPI MCP Server?

  • What is the main purpose of LiteAPI MCP Server?

The main purpose is to provide a simple and efficient server for development and testing of applications.

  • How do I configure the server?

You can configure the server using a JSON configuration file as shown in the documentation.

  • Is there any support for different programming languages?

Currently, LiteAPI MCP Server is built using TypeScript.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
liteapi-travel
Star
0
Language
TypeScript
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago