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
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago