Cursor

Connect Cursor to Ainecto via MCP.

---

Add the Ainecto MCP server

Cursor reads MCP server configuration from ~/.cursor/mcp.json (or the workspace-level .cursor/mcp.json):

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

Restart Cursor (or reload the MCP config from settings) and Cursor will detect Ainecto.

The first time you invoke an Ainecto tool, Cursor opens Ainecto's authorization page in your browser. Sign in and approve, and Cursor caches the token for subsequent calls.

Cursor's MCP support and config schema evolves — consult the Cursor MCP docs for the current version if the format above doesn't apply.

---

Try it

In Cursor's chat:

@ainecto list my ERD documents

@ainecto show the orders table in ERD document <uuid>

Cursor will route the request through Ainecto and inline the results into the chat.

---

Tips

• Mention the server explicitly — Use @ainecto (or whatever name you gave the server in mcp.json) when you want Cursor to use Ainecto vs. its built-in tools.
• Use UUIDs in scripted prompts - when automating with Cursor's rules or system prompts, prefer the ERD document UUID over the title to avoid ambiguity.
• Watch the version log — Every write through Cursor creates an Ainecto version snapshot tagged "Updated via MCP". You can roll back if Cursor makes an unwanted change.

---

Troubleshooting

Cursor doesn't see the server Check ~/.cursor/mcp.json syntax (must be valid JSON), then restart Cursor.

Auth loop Clear the cached token in Cursor settings → MCP, and re-authorize.

"plan does not include MCP" MCP is a paid feature. See Plans.