Skip to main content

Vibe Coding with Centia.io

Vibe coding is a modern approach to software development where developers use AI agents to build applications through natural language and high-level abstractions. Centia.io is built to be the perfect backend for this workflow, providing the tools and interfaces AI agents need to be productive.

What is Vibe Coding?​

Vibe coding isn't about writing every line of code yourself. It's about:

  • Natural Language First: Describing what you want to build and letting AI agents handle the implementation details.
  • Agent-Centric Workflow: Using tools like Claude Code, Junie, or Windsurf that can "understand" your project and make changes.
  • High-Level Abstractions: Focusing on the "what" and "why" while the AI handles the "how".

The @centia-io/mcp Server​

Centia.io provides a dedicated Model Context Protocol (MCP) server that allows AI agents to interact directly with your Centia.io backend. By connecting an AI agent to the @centia-io/mcp-server server, you give it the ability to:

  • Manage Schemas: Create and modify tables, columns, indexes, and constraints.
  • Execute SQL: Run queries and mutations directly against your database.
  • Handle Auth: Manage users, rules, and OAuth clients.
  • Introspect: Allow the agent to explore your database structure to better understand your data.

An AI agent can build an app from scratch with the necessary data models and authentication logic.

Installing the MCP Server​

You can add the Centia.io MCP server to your AI agent (like Claude Desktop or Junie) using the following configuration:

{
  "mcpServers": {
    "centia-io": {
      "command": "npx",
      "args": ["-y", "@centia-io/mcp-server"],
      "env": {
        "API_TOKEN": "your-access-token",
        "API_BASE_URL": "https://api.centia.io"
      }
    }
  }
}

Configuration​

The server accepts the following environment variables:

  • API_BASE_URL (optional) — Base URL for the Centia.io API. Set it when using a self-hosted deployment. Default: https://api.centia.io
  • API_TOKEN (recommended) — Personal access token for Centia. Most endpoints/tools require authentication; set this to enable them.
info

Get your access token from the console.

Agent Guide (AGENTS.md and skills)​

To ensure AI agents work effectively with Centia.io, we maintain a AGENTS.md file and Skills folder. These contain "Prime Directives" and "Hard Rules" that help agents choose the right tools for the job, whether it's using the SDK for runtime code or MCP tools for provisioning.

AGENTS.md contains the core rules (tool priority, security baselines, destructive-ops policy), while each skill in skills/*/SKILL.md covers a specific workflow area.

To ensure your AI agent follows these rules while developing your application:

  1. Copy AGENTS.md and the skills/ folder from this repository to the root of your own application's repository.
  2. When starting a session with your AI agent, it will automatically find and follow the guidelines.
info

In Claude Code, copy AGENTS.md to CLAUDE.md, because Claude Code automatically reads CLAUDE.md.

AGENTS.md covers:

  • Prime Directive: Preferring MCP tools and official SDKs.
  • Tool Priority: Order of interaction (MCP tools > SDK > HTTP).
  • Security & Auth: How to handle tokens and OAuth flows correctly.
  • Destructive Operations Policy: Requiring explicit confirmation before destructive changes.

Skills (skills/*/SKILL.md) cover task-specific workflows:

  • centia-runtime-sdk — Building JS/TS runtime code with @centia-io/sdk
  • centia-provisioning — Schema, tables, columns, constraints, indexes, migrations
  • centia-json-rpc — JSON-RPC method lifecycle and TypeScript interfaces
  • centia-auth-model — Auth across browser, backend, CLI, and provisioning
  • centia-types-formats — PostgreSQL types, casts, type hints, output formats
  • centia-file-import — File import workflow
  • centia-openapi-docs — OpenAPI and docs fallback policy
  • centia-delivery — Delivery checklist and quality gate

Key Takeaways for Agents​

When an agent is working in a Vibe Coding environment with Centia.io, it follows these priorities:

  1. Centia.io MCP tools: For schema changes and provisioning.
  2. @centia-io/sdk: For application runtime logic.
  3. OpenAPI: For direct HTTP calls when needed.

By providing these clear instructions, Centia.io ensures that "Vibe Coders" can build robust, production-ready backends with minimal friction.