Cursor IDE + Omnismith MCP

Cursor + Omnismith:
Scaffold Runtime APIs Directly from Your IDE

When building internal tools, admin portals, telemetry trackers, and client dashboards in Cursor, don't pollute your core transactional database or spend days writing boilerplate CRUD APIs. Let Cursor manage dynamic runtime schemas in Omnismith via MCP.

Create Free Workspace Explore MCP Server Specs

A Companion Operational Backend for Internal Tools

Most development teams already have a primary production database for user authentication and billing. But engineering teams are constantly asked to build companion operational systems: internal triage portals, device telemetry dashboards, hardware asset trackers, and client workbenches.

✕ Without Omnismith

• Modifying your production database schema with risky migrations.
• Writing and maintaining repetitive CRUD endpoints, validators, and DTOs.
• Manually implementing field-level audit tables and change attribution.
• Setting up separate time-series infrastructure for metric tracking.

✓ With Cursor + Omnismith

• Schemas are runtime data: Cursor creates templates and attributes via MCP.
• Ready-to-use REST API with OpenAPI specification from the very first write.
• Immutable field-level change history automatically recorded on every update.
• Native time-series metric ingestion and chart queries out of the box.

Setup Walkthrough

Connecting Omnismith to Cursor

Configure the MCP server in Cursor Settings or check in a project-scoped .cursor/mcp.json file.

Add MCP Server in Cursor Settings

In Cursor, open Cursor Settings → Features → MCP Servers and click + Add New MCP Server:

Server Name

omnismith

Type

sse (Streamable HTTP)

Server URL

https://mcp.omnismith.io/mcp

Alternative: Project Configuration (.cursor/mcp.json)

You can also commit an MCP configuration file in your workspace directory at .cursor/mcp.json:

{
  "mcpServers": {
    "omnismith": {
      "url": "https://mcp.omnismith.io/mcp",
      "headers": {
        "Authorization": "Bearer omni_live_secret_key_demo"
      }
    }
  }
}

Add .cursorrules to Your Project

Place a .cursorrules file (or .cursor/rules/omnismith.mdc) at the root of your project. This guides Cursor Agent to use Omnismith for schema evolution and data binding:

# Omnismith Agent Instructions for Cursor

You have access to Omnismith as our runtime operational backend and dynamic database via MCP tools.
When designing features, internal tools, admin portals, or telemetry trackers:

## 1. Schema & Model Design
- Do not create SQL migrations, local SQLite databases, or Prisma/Drizzle schema files for operational records.
- Use the MCP tool `get_schema_overview` to inspect existing workspace templates and attributes.
- Use `scaffold_data_model` or `create_attribute` to define new runtime schemas directly from requirements.
- Always use deterministic, lowercase snake_case slugs for templates and attributes (e.g. `ticket_id`, `assigned_agent`, `severity_tier`).

## 2. API & Data Access
- Connect frontend components directly to Omnismith REST endpoints under `https://api.omnismith.io/v1/`.
- Always supply authentication and project headers:
  - `Authorization: Bearer ${process.env.OMNISMITH_API_KEY}`
  - `X-Omnismith-Project-Id: ${process.env.OMNISMITH_PROJECT_ID}`
- When reading entity fields, unpack `entity.attribute_values[slug_or_id].value`.
- For field change histories, call `GET /v1/entities/{id}/history`.
- For telemetry metrics, batch write to `POST /v1/entities/{id}/metrics`.

How the Workflow Operates in Cursor Composer

Define the Need in Cursor Composer

Ask Cursor to build an internal dashboard (e.g. customer success console, fleet telemetry viewer, or review queue).

Cursor Synthesizes the Backend via MCP

Cursor calls scaffold_data_model in Omnismith to provision templates, typed attributes, and list validations in real time.

Cursor Implements the Frontend UI

Cursor writes the React/Next.js/Vue component directly against Omnismith's generated REST API endpoints with typed contracts.

Real-World Composer Prompt

Building an IT Asset & Hardware Tracker

Try entering this prompt into Cursor Composer once Omnismith MCP is connected:

"We need an internal hardware inventory tool. Use Omnismith MCP to inspect our workspace and scaffold an 'it_asset' template with attributes: serial_number (string), assigned_employee (string), model_name (string), hardware_tier (list: Standard, Engineering, Executive), and purchase_date (date). Then write a React table component that queries our entities via the Omnismith REST API and includes a button to view each asset's immutable audit history."

Cursor will invoke scaffold_data_model to provision the schema in your Omnismith project, then generate production frontend code targeting the documented /v1/entities REST endpoints.

← Claude Desktop Setup Guide Model Context Protocol Architecture →

Cursor + Omnismith: Scaffold Runtime APIs Directly from Your IDE