What dependencies are required?
Node.js and npm (or yarn) are required. An OpenAI API key must be provided in the `src/env/keys.ts` file or inline in the Cursor MCP interface.
@kleneway
Basic information
Example of an MCP server with custom tools that can be called directly from cursor
No standard config provided
This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.
RepositoryTool list not available yet
This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.
We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.
An AI-powered development toolkit implemented as a Model Context Protocol (MCP) server for Cursor. It provides intelligent coding assistance through custom AI tools, but is primarily a tutorial demo and not a production-ready tool.
Install dependencies with npm install or yarn install, build the server with npm run build, then add it to Cursor Settings > Features > MCP as a new stdio server with the command node /path/to/dist/index.js. Once added, tools appear in Composer and can be triggered by asking the AI explicitly (e.g., “Review this code for best practices”).
src/env/keys.tsNode.js and npm (or yarn) are required. An OpenAI API key must be provided in the `src/env/keys.ts` file or inline in the Cursor MCP interface.
API keys are stored locally in the `keys.ts` file (or set inline) and sent to OpenAI when tools are used. The server runs locally and does not store user data externally.
No. The project is explicitly described as a tutorial demo, not a production-ready tool. The author notes they likely won’t fix issues, but encourages forking.
It uses the stdio transport type, configured in Cursor as a command that runs the built `dist/index.js` file.
The AI agent in Cursor’s Composer automatically suggests using relevant tools, or you can explicitly request them by name or description (e.g., “Analyze this UI screenshot”). The agent asks for approval before making tool calls.

The tools your AI needs to make your games. Turn prompts into production-ready game assets — animated characters with their weapons attached, seamless textures, terrain, VFX, HUDs — and playable game kits Unity, Godot, U

Catch intent conflicts before code conflicts. The open-source coordination protocol for coding agents, built above Git.
OrangePro local-first CLI + MCP server for behavior mapping, grounded test generation, and dynamic proof.

Local-first credential broker for MCP. AI coding agents (Claude Code, Cursor, Codex…) call APIs, SSH and databases through scoped presets; secrets stay in your OS keychain and never enter the agent's context.

One case file per task — shared by every session, agent and person that touches it. Self-hosted MCP server and live board. MIT.
Comments