Gemini

Connect Google's Gemini CLI (or other Gemini-based coding assistants) to AiNecto via MCP.

Add the AiNecto MCP server

Gemini CLI reads MCP server configuration from ~/.gemini/settings.json:

{
  "mcpServers": {
    "ainecto": {
      "httpUrl": "https://ainecto.com/mcp"
    }
  }
}

Restart Gemini CLI. The first AiNecto tool call triggers the OAuth flow.

Gemini CLI's MCP support and config schema is evolving — consult the Gemini CLI docs for the current version.

List my ERD documents in AiNecto.

Show me the schema of the orders table in ERD document <uuid>.

In ERD document <uuid>, add an order_items table linking orders and products with quantity and unit_price columns. Use description "Add line items".

Use the ERD document UUID in scripted prompts to avoid name resolution.
Description matters — every write needs one and it shows up in your version history.
Combine with Gemini's code generation — ask Gemini to read the schema first, then generate Go/Python/TypeScript model code that matches.

Gemini doesn't list AiNecto tools Check ~/.gemini/settings.json is valid JSON and Gemini CLI was restarted after edits.

Auth flow fails Ensure your browser can open the AiNecto authorization URL; if not, copy/paste the URL manually.

Tool call returns 403 Confirm your account has access to the target document (OWNER or EDITOR for writes).