Pocha MCP Server

What is Pocha MCP Server?

A Model Context Protocol (MCP) server that generates TypeScript API functions for the Pocha project. It provides a tool to automatically generate type-safe API function templates following a consistent pattern.

How to use Pocha MCP Server?

Clone the repository, install dependencies with pnpm install, build with pnpm build, then configure the server in Cursor IDE’s mcp.json using the compiled dist/index.js script. The server exposes a generate-api-function tool that accepts parameters like functionName, route, method, optional params, and returnType.

Key features of Pocha MCP Server

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

Use cases of Pocha MCP Server

• Automatically creating API functions for the Pocha project.
• Ensuring consistent API function patterns across a codebase.
• Reducing boilerplate when adding new endpoints to a Pocha backend.

FAQ from Pocha MCP Server

What does the generated API function include?

The generated function includes proper TypeScript types, token-based authentication via Authorization header, error handling with try/catch, and a descriptive JSDoc comment with route and method.

What are the dependencies required to build or run the server?

The server uses the MCP TypeScript SDK and Zod for schema validation. Node.js and pnpm are required to install and build.

How do I set up this server with Cursor IDE?

Edit the Cursor MCP configuration file (e.g., ~/.cursor/mcp.json) and add an entry under mcpServers with the command to run dist/index.js via npx and Node. Restart Cursor for the changes to take effect.

Can I generate functions for custom routes and methods?

Yes, the generate-api-function tool accepts a route (string), method (one of "GET", "POST", "PUT", "DELETE"), and optional params array with names and types.

Where does the generated code live?

The server outputs the generated TypeScript code as a response; it does not automatically write files. The user must copy or integrate the output into their project.