Use theDocumentation Index
Fetch the complete documentation index at: https://docs.vizkraft.com/llms.txt
Use this file to discover all available pages before exploring further.
Connectors area to add the data sources your team wants to analyze.

Connector types available in the app
Vizkraft currently lets customers add:- PostgreSQL
- MySQL
- ClickHouse
- Custom MCP server
Add a new connector
- Open
Connectors. - Select
Add connector. - Choose the connector type you want to add.
- Enter the connection details shown in the form.
- Test the connection.
- Save the connector.

Saving a SQL connector automatically starts an initial indexing run, which uses one slot from your monthly indexing-runs allowance (Pro 5/mo, Business 20/mo, Enterprise unlimited). You can see your remaining runs on
Profile → Usage. See Indexing runs and your plan for the full breakdown.Managed database connectors vs custom MCP servers
Managed database connectors
Use these when you want Vizkraft to connect directly to a supported SQL database. This is the fastest path if your data is already in PostgreSQL, MySQL, or ClickHouse.Custom MCP server
Use this when your team already has an MCP-compatible server or when you want Vizkraft to access tools beyond a single managed SQL connector.What to name a connector
Choose names that help people pick the right source in chat. Good examples:Production PostgreSQLMarketing warehouseFinance MCPCustomer support analytics
Edit or retest an existing connector
From the connectors list you can:- Open a connector to review its status.
- Edit its settings.
- Run another connection test after credentials or endpoints change.
- Jump directly into indexing for supported SQL sources.
Use one or more connectors in chat
After connectors are saved, they become available in chat. You can:- Enable a single connector for a focused question.
- Enable multiple connectors when the answer needs information from more than one source.
- Switch connectors between questions without rebuilding the connector itself.
Best practices
- Create one connector per stable data source rather than reusing a generic catch-all name.
- Test the connector before saving it so your first chat session starts smoothly.
- If a connector feeds charts or dashboards for multiple teams, give it a clear business name.
- Run indexing after setup for the best chart and dashboard suggestions.