Gentic Data Architect — Documentation

Point your agent at a Google Drive folder. The Data Architect reads every doc, PDF, and spreadsheet, proposes an import plan — what becomes a queryable table, what becomes searchable knowledge, and what needs a human — then, on your approval, converts and loads it all into your Gentic workspace. Scan, plan, apply — all through the Model Context Protocol.

1. Getting Started

Sign Up & Get Your API Key

Before you can use Gentic Data Architect, you need an API key to authenticate your requests.

Go to gentic.co/architect and create an account.
Create an organization from your dashboard. API keys and billing are scoped to the organization.
Generate an API key and use it as a Bearer token in your MCP client.

2. Connecting to the MCP Server

The server is available at https://mcp.gentic.co/architect. For Claude Code:

claude mcp add gentic-architect \
  --transport http \
  https://mcp.gentic.co/architect \
  --header "Authorization: Bearer YOUR_API_KEY"

For Claude Web and ChatGPT you can also connect via OAuth — no API key needed. See the connect section on the landing page for other MCP clients (n8n, OpenClaw).

3. Agent Skill

For the best results, pair the MCP server with the Gentic Data Architect agent skill. The MCP server gives your agent tool access; the skill teaches it the optimal workflow order. Both the raw SKILL.md and a ready-to-upload .skill bundle are generated on demand from the live manifest, so they always reflect the current tools and pricing.

Add the skill directly via URL:

https://gentic.co/architect/SKILL.md

Or upload a .skill bundle to Claude Managed Agents:

https://gentic.co/architect/gentic-architect.skill

Download this file and upload it wherever Claude Managed Agents asks for a .skill file. It's a zip bundle generated on demand from the latest SKILL.md.

4. When to Apply

User wants to import a Google Drive folder of files into AI-ready data.
User has spreadsheets, PDFs, docs, or CSVs that need to become queryable tables or searchable knowledge.
User wants to review what will be imported — and why — before anything runs.
User wants to re-run a folder after updating files, refreshing the data in place.
User asks what happened to a specific file in a previous import (imported, skipped, or flagged).

5. Workflow

1. Scan the folder first
Call `architect_scan_folder` with a Google Drive folder link. It enumerates the files it can read, inspects each one, and produces an import plan: for every file a proposed destination (queryable table, searchable knowledge, table + search, or needs-review), plus the structure it detected — header row, which tab, which columns should get semantic search. Ambiguous files are flagged with a specific reason rather than guessed at. Nothing is imported at this stage. Surface the returned plan to the user before applying.
2. Review the plan before applying
Use `architect_get_plan` to fetch the current plan for a scanned folder (e.g. to re-display it, or after the user steps away). Walk the user through it file by file — especially anything flagged needs-review, which won't import until the user decides. The plan is the product: it's the gate the user approves against.
3. Apply only approved files
`architect_apply` runs the import for the approved files and converts each into its planned destination in the user's Gentic workspace: tables you can query in plain English, documents your AI can search and cite. It returns a receipt — what landed, what was skipped, and why. Imports are enforced server-side against the approved plan, so an agent cannot import a file the user didn't approve.
4. Re-run safely to refresh
If files change, re-scan and re-apply the folder. Changed files refresh their tables in place rather than creating duplicates, so re-running is safe and idempotent.
5. Present results clearly
Don't dump raw JSON. Show the plan as a readable per-file list (filename → destination → one-line detail), call out flagged files with their reason, and after apply, summarize the receipt: how many files landed as tables, how many as knowledge, and what was skipped.

6. Tool Reference

3 tools, rendered live from the Gentic MCP manifest. Parameter tables come directly from each tool's JSON Schema.

architect_apply

Free

Apply an approved Data Architect plan: approve/reject/skip each item, resolving any conflicts (table_name_override). Approved items only; the review gate is structural and validated atomically — any unresolved conflict rejects the whole submission and nothing changes. Import of approved items runs server-side.

Parameter	Type	Description
`scan_id` required	`string`	—
`approvals` required	`object[]`	Per-item decisions. Duplicate-name conflicts MUST be resolved here (table_name_override or skip).

architect_get_plan

Free

Read the review plan for a Data Architect scan: per-file destination, proposed spec, conflicts to resolve, and current state. Approve/reject items with architect_apply.

Parameter	Type	Description
`scan_id` required	`string`	The scan_id returned by architect_scan_folder.

architect_scan_folder

5¢ / result (min 5¢)

Onboard a whole Google Drive folder into GenticDB: classify every file (brain doc vs data table vs hybrid vs skip vs needs-human) and return a REVIEW PLAN. Nothing is written until you approve the plan with architect_apply. Use this for 'onboard this Drive folder' / 'sort these files into brain vs tables' — a single 'import this CSV' or 'add this doc to the brain' stays on the data/brain tools. Free — you're billed only for files actually imported at apply.

Parameter Type Description

Parameter	Type	Description
`folder_url`	`string`	Public 'anyone with the link' Google Drive folder URL.
`file_urls`	`string[]`	Fallback when folder enumeration is blocked: explicit public file links.
`max_files`	`integer`	Hard cap (default 100). 1 – 100

folder_url

string

Public 'anyone with the link' Google Drive folder URL.

file_urls

string[]

Fallback when folder enumeration is blocked: explicit public file links.

max_files

integer

Hard cap (default 100).

1 – 100

7. Pricing

Pricing is pulled live from the Gentic MCP manifest. All prices are per call and deducted from your Gentic credits.

Tool	Cost
architect_apply	Free
architect_get_plan	Free
architect_scan_folder	5¢ / result (min 5¢)

8. Notes

Your Drive is read-only to the Architect — it reads files to plan and import; it never modifies your Drive. Converted copies live in your Gentic workspace with a full audit trail.
Nothing imports without approval: `architect_apply` only acts on files approved in the plan, enforced server-side.
Two separate meters: scanning a folder (architect_scan_folder) is billed per file inspected, whether or not it ends up imported; applying a plan (architect_apply) is billed per file actually imported — files you skip or that fail cost nothing on apply. Exact per-tool pricing is pulled live from the Gentic MCP manifest below.
Ambiguous files are never guessed at — they're flagged in the plan with a specific reason and a suggested fix, and left for a human to decide.
Supported file types include Google Docs, Google Sheets, Excel workbooks, PDFs, CSVs, and plain text files.