Architect MCPv2.1 · Tool-based platform management

Architect Your Platform with Tools, Not Clicks

Docyrus Architect MCP provides a high-level toolset for shaping your tenant: create data sources, define fields, manage enums, and keep your OpenAPI spec in sync.

See CapabilitiesDocyrus on GitHub
Apps
Data Sources
Fields
Enums
OpenAPI

Operations as Primitives

Standardized tools to govern your entire tenant architecture.

Discovery-first

Discovery Tools

Find what exists before changing anything. Inspect apps, available data sources, and understand fields, enums, and relations with a single tool call.

listApps() describeDs()
// Result: listApps
[0] app_crm (Active)
[1] app_billing (Production)
- ds_invoices
- ds_subscriptions

Enum Catalog

Manage enum options consistently across all select and status fields with versioned operations.

DraftDraft
ActiveActive
ArchivedArchived

Custom Query Pack

Work with saved SQL templates: list, fetch definitions, and execute with runtime filters.

monthly_revenueTemplate
active_subscriptionsTemplate
churn_rate_30dTemplate

Schema Orchestration

Evolve data models safely. Bootstrap new app schemas or modify existing fields without manual admin clicks.

createDs()updateField()deleteDs() Destructive
// JSONata Playground
$sum(invoices.total)
// Result: 1240.22

AI ideas fail without architecture

Don't click through menus. Connect your agent to the Architect MCP and bootstrap an entire app model programmatically discover, create, define fields and enums, then regenerate the OpenAPI spec for downstream dev.

Platform teams

Building consistent schemas across apps without manual admin work.

Ops teams

Bootstrapping new app models programmatically from agent instructions.

AI builders

Connecting agents to the Architect MCP so they can shape the tenant's own data model.

Solution consultants

Delivering repeatable tenant setups faster with tool-based schema templating.

Safe by Design

Tool-level safeguards so agents can operate with power without creating risk.

Read / Write Separation

Tools are explicitly labeled. Read-only tools cannot modify state, preventing accidental changes.

Explicit Approvals

Destructive tools like deleteDs() require explicit human confirmation via the UI.

Tenant Boundaries

Every operation is strictly scoped to the tenant context, ensuring data isolation.

Spec Verification

Changes are validated against platform standards before the OpenAPI spec is updated.

Frequently asked questions about Docyrus Architect MCP

What is Docyrus Architect MCP?+

Docyrus Architect MCP is the MCP interface for managing Docyrus apps, data sources, fields, enums, queries, and architecture assets.

When should developers use Docyrus Architect MCP?+

Developers should use it when coding assistants or agent workflows need to manage platform structure rather than just runtime records.

What can teams ship with Docyrus Architect MCP?+

Teams can ship schema changes, app architecture updates, OpenAPI generation, and platform setup flows through MCP.

How does Docyrus Architect MCP fit with other Docyrus developer tools?+

It complements Data MCP and the API by focusing on structure and configuration instead of runtime record access.

Architect Your Growth

Use tools for schema, queries, and OpenAPI so your platform stays consistent as it grows.

Connect Architect MCPSee Capabilities