pahangkrisdyan-mcp-server

Created By
pahangkrisdyana year ago
Pahangkrisdyan's MCP Server
Overview

what is pahangkrisdyan-mcp-server?

Pahangkrisdyan's MCP Server is a project built using the Quarkus framework, designed to facilitate the development of microservices with a focus on performance and efficiency.

how to use pahangkrisdyan-mcp-server?

To use the MCP Server, you can run the application in development mode using Gradle, create a native executable, or build and run a Docker image of the server.

key features of pahangkrisdyan-mcp-server?

  • Live coding support in development mode with Quarkus Dev UI.
  • Ability to create native executables for optimized performance.
  • Docker support for easy deployment and scalability.

use cases of pahangkrisdyan-mcp-server?

  1. Developing microservices that require high performance and low latency.
  2. Building applications that can be easily containerized and deployed in cloud environments.
  3. Rapid prototyping of Java applications using live coding features.

FAQ from pahangkrisdyan-mcp-server?

  • What is Quarkus?

Quarkus is a supersonic, subatomic Java framework tailored for Kubernetes and cloud environments.

  • How do I run the application in development mode?

You can run the application using the command ./gradlew quarkusDev.

  • Can I create a Docker image from the native executable?

Yes, you can create a Docker image using the provided Dockerfile and run it with Docker.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
pahangkrisdyan
Star
0
Language
Java
License
MIT license

Recommend Servers

View All
Voyei

2 hours 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