What does this server do out of the box?
This server is a template with no pre‑defined tools. Developers must add their own tool implementations to make it functional.
@larryhudson
Basic information
No overview available yet
Add this server to your MCP-compatible client using the configuration below.
{
"mcpServers": {
"figma-mcp-server-larryhudson": {
"command": "npx",
"args": [
"@modelcontextprotocol/inspector",
"npx",
"tsx",
"src/index.ts"
]
}
}
}Tool 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.
Fetch the live tool list by running this server in a temporary sandbox using the button above.
It is a template project for building Model Context Protocol (MCP) servers. It provides a starting structure for adding custom tool definitions, configuring environment variables, and publishing the server as an npm package. It is intended for developers who want to create new MCP-compatible integrations.
Developers add tool definitions in src/index.ts, update the placeholder information in package.json, and build the server with npm run build. They can test the server locally using the @modelcontextprotocol/inspector library. After testing, they publish the package to npm with npm login and npm publish --access public. To run the server, users set an API key as an environment variable (API_KEY_ENV_VAR) and add the MCP configuration to their client (e.g., VS Code or Claude).
src/index.ts)This server is a template with no pre‑defined tools. Developers must add their own tool implementations to make it functional.
Add tool definitions and implementations in `src/index.ts`. The file is the single entry point for all tool logic.
You need Node.js and `npx` (to run the server via npm). The server is built with TypeScript and uses the MCP SDK.
Run `npx @modelcontextprotocol/inspector npx tsx src/index.ts` to start the inspector and test tools locally.
The API key must be set as the environment variable `API_KEY_ENV_VAR`, either in the MCP client’s configuration or directly in the shell. The exact name of this variable is defined in the template’s configuration.

Official JSON2Video MCP server. Video API for automated video production at scale: render videos from templates with AI voiceovers, subtitles and AI images. Remote server with OAuth (https://mcp.json2video.com/mcp) or lo
Access 20+ AI video and image models from Google, OpenAI, xAI, ByteDance, and more. Generate and edit videos with Veo 3.1, Sora 2, Seedance, Kling O3, and images with FLUX, Nano Banana, Seedram 4, GPT Image — all in one

Build and run AI product photography workflows from your AI assistant: on-model shots, catalog images, prints and edits, with results returned in chat.

EveryGen AI MCP Server lets AI assistants create videos, images, voiceovers, music and complete multi-shot films. Connect your EveryGen AI account, describe what you want, review the credit quote and approve the creation

Remote MCP server for AI image, video, voice and music generation. Your agent creates and edits images with Nano Banana 2, GPT-Image 2 or FLUX 1.1 Pro, generates video with Veo 3.1 Fast, Seedance 2.5, Kling, MiniMax or W
Comments