FrameIO MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_moduleB | Generate complete module scaffolding with package.json, index.ts, tsconfig.json, and registry entry |
| generate_entityC | Generate entity definition code using defineEntity() builder |
| validate_moduleA | Validate module structure, code, and conventions. Use modulePath when the MCP runs with cwd at the FrameIO repo root. Use files (package.json + src/index.ts contents) when the MCP is remote or cannot read your disk. |
| get_example_moduleC | Fetch example code from existing modules |
| generate_workflowB | Generate workflow definitions with states, transitions, and approvals using defineWorkflow() builder |
| generate_pageC | Generate custom page components with SDK integration and routing |
| generate_widgetC | Generate dashboard widget definitions (stat, table, list, chart, or custom) |
| generate_navigationB | Generate navigation sections and items for sidebar and mobile navigation |
| analyze_moduleC | Analyze module for issues, unused code, missing relationships, and best practice violations |
| generate_migrationC | Generate database migration scripts for schema changes |
| generate_testB | Generate Vitest test files for modules, entities, workflows, pages, or widgets |
| fix_moduleC | Auto-fix common module issues like naming conventions, imports, and exports |
| generate_api_endpointC | Generate custom API endpoints with Express route handlers and Swagger documentation |
| generate_hookC | Generate custom React hooks with SDK integration |
| generate_storybook_storyC | Generate Storybook stories for component documentation |
| generate_documentationB | Auto-generate README.md and API documentation for a module |
| check_dependenciesC | Check for dependency conflicts, version mismatches, and missing packages |
| generate_seed_dataC | Generate seed data scripts for development and testing |
| generate_pluginB | Generate complete plugin scaffolding with package.json, index.ts, tsconfig.json, migrations, routes, and registry entry |
| generate_plugin_migrationA | Generate a new database migration for a specific plugin with table definitions |
| validate_pluginC | Validate plugin structure, route contract (createRouter(deps)), build contract (tsconfig.build.json), and registry |
| add_plugin_to_registryA | Add a plugin to plugins/.registry.ts and regenerate plugin-imports (apps/web plugin map). Use after generating a new plugin. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| module_creation_guide | Step-by-step guidance for creating a new FrameIO module |
| entity_design_guide | Guidance for designing entities with proper fields, views, and permissions |
| validation_checklist | Checklist for validating a module before completion |
| plugin_creation_guide | Step-by-step guidance for creating a new FrameIO plugin with migrations and API routes |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| FrameIO Design Philosophy & Platform Architecture | Canonical design philosophy and platform architecture: modules vs plugins, no domain in core, registration-based design, widget data from plugins only, route and build contracts |
| FrameIO Framework Guide | Comprehensive framework documentation covering module structure, entities, fields, navigation, and best practices |
| Field Types Reference | Complete reference of all available field types with options, validation rules, and examples |
| BOM Module Example | Example code from the pos-bom module |
| Rewards Module Example | Comprehensive feature example from module-rewards |
| Best Practices Guide | Naming conventions, design patterns, and module/plugin organization guidelines |
| FrameIO Plugin Guide | Comprehensive guide to plugin architecture, development, migrations, API routes, and management |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/danielldt/frameio-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server