Bun-based MCP Server

Created By
moikas-codea year ago
Overview

what is MCP Server?

MCP Server is a minimal Model Context Protocol (MCP) server built using Bun and TypeScript, designed to handle MCP requests and demonstrate dynamic tool loading from a PostgreSQL database.

how to use MCP Server?

To use MCP Server, install Bun, set up the project dependencies, and start the server using the provided commands. The server listens for MCP requests via standard input/output.

key features of MCP Server?

  • Implements StdioServerTransport for local testing.
  • Includes a basic example tool (add) that adds two numbers.
  • Supports dynamic tool loading from a PostgreSQL database.
  • Enforces strict TypeScript and ESLint configurations.

use cases of MCP Server?

  1. Developing and testing MCP-based applications.
  2. Creating custom tools that can be loaded dynamically.
  3. Learning and experimenting with Bun and TypeScript in server environments.

FAQ from MCP Server?

  • What is the purpose of the add tool?

The add tool is a simple example that demonstrates how to create and use tools within the MCP Server.

  • How do I install Bun?

You can install Bun by following the instructions on the official Bun website: https://bun.sh/.

  • Can I use a different database instead of PostgreSQL?

Yes, you can modify the load_tools_from_db function to integrate with other databases as needed.

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

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
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