Skip to main content
A connection is a data source Vistazo can read. They all speak MCP, which is what lets the agent work out what a source offers without anyone modelling it first. It reads the server’s own tool descriptions. Connections live under Settings → Connections.

​
Connections belong to you, not the workspace

Each person connects their own sources with their own credentials. Vistazo never holds a shared service account on your behalf. The consequence worth knowing is that a scheduled refresh runs as the dashboard’s owner, on the owner’s connections. On-demand refreshes run on yours. If a dashboard depends on a source you have not connected, Vistazo tells you how many of its charts are affected.

​
Three kinds of source

Five public data sources are operated by Vistazo: World Bank, weather, SEC EDGAR, U.S. Treasury and exchange rates. They need no account or key of your own, and they are connected for you when you sign up, so you will usually find them already in the list. See Curated sources.
The list also carries a Vistazo row, which is Vistazo’s own MCP server, the one your agent connects to. It is not a data source and cannot be removed. See MCP server.

​
Authorizing

How a connection is authorized depends on what the server supports.
  • OAuth with dynamic registration. Vistazo runs the flow in a browser window and there is nothing to set up.
  • Your own OAuth app. Where a server cannot register clients automatically, you create an app at the provider with the redirect URL Vistazo shows you, then paste the client id and secret.
  • No authorization at all, for servers that need none.
Tokens are encrypted and held server-side. They are never written where the browser can read them. Vistazo will only talk to public HTTPS endpoints.

​
Managing a connection

Open a connection to see the tools it exposes and to act on it. The hosted curated sources can be disabled but not removed. Add to an agent covers Vistazo’s own server and the curated sources; there is no generated snippet for your own connections, since your agent would connect to those directly.

​
When something is wrong

A connection in trouble is surfaced on the widget that depends on it, not just in Settings. Degraded connections sort to the top of the list, and the status is click-to-reconnect.