Pocha MCP Server

Created By
retz8a year ago
Testing Internal MCP Server for KISA Dev team's pocha project
Overview

What is Pocha MCP Server?

Pocha MCP Server is a Model Context Protocol (MCP) server designed to generate TypeScript API functions for the Pocha project, providing a tool to automatically create type-safe API function templates.

How to use Pocha MCP Server?

To use the Pocha MCP Server, clone the repository, install the dependencies, and build the project. You can then use the generate-api-function tool to create API functions by providing the necessary parameters.

Key features of Pocha MCP Server?

  • Generates TypeScript API functions with proper typing
  • Supports various HTTP methods (GET, POST, PUT, DELETE)
  • Includes authentication token handling
  • Provides error handling and response typing
  • Supports optional parameters and return types

Use cases of Pocha MCP Server?

  1. Automatically generating API functions for the Pocha project.
  2. Simplifying the process of creating type-safe API endpoints.
  3. Enhancing development efficiency by reducing boilerplate code.

FAQ from Pocha MCP Server?

  • What programming language is used?

The server is built using TypeScript.

  • How do I set up the server in my development environment?

Follow the installation instructions in the README to clone the repository and configure your Cursor IDE.

  • Is there any support for error handling?

Yes, the generated API functions include proper error handling.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
retz8
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)

8 hours ago
Alloy

2 days ago