Claude & Model Context Protocol (MCP)

The Omnismith Model Context Protocol (MCP) Server enables seamless integration between your Omnismith workspaces and AI assistants like Claude Desktop, Cursor, or tools in the Claude Connectors Directory.

Through MCP, Claude gains first-class tools and dynamic resources to explore schemas, scaffold data structures, query time-series metrics, and trigger automations on your behalf.

1. Quick Setup for Claude Desktop (1-Click OAuth)

Omnismith supports native OAuth 2.1 authentication for Claude Desktop. You do not need to manually generate or paste API keys into headers.

Option A: 1-Click Connect via Remote SSE

Open your Claude Desktop configuration file:
- macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
- Windows: %APPDATA%\Claude\claude_desktop_config.json
- Linux: ~/.config/Claude/claude_desktop_config.json
Add the omnismith server configuration:

{
  "mcpServers": {
    "omnismith": {
      "url": "https://mcp.omnismith.io/mcp/sse"
    }
  }
}

Restart Claude Desktop.
When Claude Desktop connects, your browser will open the Omnismith Authorization Screen.
Select the Omnismith project you wish Claude to access and click Authorize.
Claude Desktop will securely store the credentials and immediately enable Omnismith tools in your chat toolbar.

Option B: Pre-Shared API Key (Headless / CLI)

If you are running in headless CI/CD environments or tools where interactive browser consent is unavailable:

Open your workspace and navigate to Access & Security → Access Tokens.
Click Add Token to generate a new programmatic access token (omni_live_...).
Set the authorization header in your configuration:

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

2. Claude Connectors Directory & Remote Endpoints

Omnismith provides native Server-Sent Events (SSE) remote transport for web-based connectors and distributed agents:

Resource	URL	Description
SSE Transport Endpoint	`https://mcp.omnismith.io/mcp/sse`	Live JSON-RPC stream for tool execution and resource subscription.
Protected Resource Metadata	`https://mcp.omnismith.io/.well-known/oauth-protected-resource`	RFC 9728 discovery endpoint for OAuth 2.1 authentication.
Connector Manifest	`https://mcp.omnismith.io/mcp/manifest.json`	Claude Connectors Directory standard discovery descriptor.

3. Available Tools & Capabilities

When connected via MCP, Claude has access to a curated catalog of specialized operations:

📐 Schema & Modeling

scaffold_data_model: High-level synthesis tool to design and provision templates, attributes, and relationships in a single prompt.
list_templates / get_template_details: Introspect data schemas, field bindings, and UI groups.
create_attribute / update_attribute: Create and configure dynamic attribute definitions.

📊 Records & Metrics

search_entities: Query and filter entity records across dynamic attributes.
create_entity / patch_entity: Create and update records according to template schemas.
query_metric_series: Query time-series telemetry with aggregation and windowing.

⚡ Dashboards & Automations

list_dashboards / get_dashboard: Inspect visual dashboards and widgets.
list_automations / create_automation: Inspect and configure event-driven webhook actions.

4. Security & Permissions

All MCP tool invocations execute under the security context of your authenticated Omnismith user and selected project:

Role-Based Access Control: Claude cannot perform operations exceeding your role permissions (Owner, Admin, Editor, Viewer).
Project Isolation: MCP sessions are strictly scoped to the project chosen during OAuth authorization.
Audit Logging: All record creations, schema modifications, and automation triggers executed via MCP are immutably logged to the project audit log.