MCP server Claude CodeCodexCursor +2
MCP server "chrome-devtools" as configured in objectstack-ai/objectstack. Launched with chrome-devtools-mcp.
MCP server Claude CodeCodexCursor +2
MCP server "chrome-devtools" as configured in objectstack-ai/objectstack. Launched with chrome-devtools-mcp.
Skill Claude CodeCodex
Design ObjectStack AI skills, tools, knowledge sources, and the open-edition MCP server surface. Use when the user is adding .skill.ts / .tool.ts, configuring an LLM provider, wiring the tools a skill grants, or indexing ObjectStack data as a knowledge source for RAG. Agents themselves are platform-internal (ask /…
Skill Claude CodeCodex
Design the server-side API surface that an ObjectStack runtime exposes — REST endpoints, auth providers, realtime channels, error envelopes, batch contracts. Use when the user is adding .endpoint.ts, configuring auth providers, defining custom routes, or extending the REST generator. Do not use for: consuming an…
Skill Claude CodeCodex needs its repo
Design ObjectStack automation — Flows (visual logic), Triggers, Approvals, state machines, and the jobs (defineJob) / webhooks (defineWebhook) stack collections. Use when the user is adding .flow.ts, wiring an event-driven rule, modelling an approval chain, or building an interactive screen flow / wizard…
Skill Claude CodeCodex
Design ObjectStack data schemas — objects, fields, relationships, validations, indexes, hooks, security, seeds and datasources. Use when the user is creating or modifying .object.ts files or src/data/.ts seed modules, picking field types, modelling relationships, writing beforeInsert/afterUpdate hooks, configuring…
Skill Claude CodeCodex
Author CEL expressions used across ObjectStack — formula fields, field conditional rules (visibleWhen, readonlyWhen, requiredWhen), validation / sharing / visibility predicates, flow conditions, and dynamic seed values. This is the companion skill that objectstack-data, -ui, -api and -automation each tell you to load…
Skill Claude CodeCodex
Author ObjectStack translation bundles — object/field labels, view text, app navigation strings, automation messages — and configure locale fallback, coverage reporting, and the source layout. Use when the user is adding .translation.ts files, authoring a translation metadata item in the Studio or through the metadata…
Skill Claude CodeCodex
Bootstrap, configure, extend, and operate ObjectStack runtimes. Covers project setup (defineStack, drivers, scaffolding), declaring platform capabilities (requires: — which service plugins boot), plugin and service development (PluginContext, DI, kernel hooks like kernel:ready), and operations (CLI commands…
Skill Claude CodeCodex
Construct ObjectQL queries — filters, sorting, pagination, aggregation, relation expansion, and full-text search. Use when the user is writing a query DSL expression or picking a pagination strategy. Do not use for defining objects / fields / relationships (see objectstack-data), for designing the API endpoint that…
Skill Claude CodeCodex
Author ObjectStack UI metadata — Views (list/form/kanban/calendar/gantt), Apps (navigation), Pages (structured plus the HTML and React source-authoring tiers, ADR-0080/0081), Dashboards, Reports, Charts, Actions, and package Docs (src/docs/.md). Use when the user is adding .view.ts / .page.ts / .app.ts / .dashboard.ts…
Skill Claude CodeCodex
Upgrade an ObjectStack metadata project across a protocol major — run the deterministic conversion chain, then work the semantic residue the chain cannot express (intent choices, custom code on retired APIs, stale prose) to a decision with the project's owner, and finish with a green validate plus a human-readable…
Plugin Claude Code
Bundles 1 skill, 1 command, 1 MCP server · 65 tokens together
Connect Claude Code to any ObjectStack deployment over MCP: discover objects, query and change records, and run business actions — under your own permissions and row-level security. OAuth self-serve; the deployment URL is the only input.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: