MarcoPolo MCP

Create a browser setup URL for a credentialed connection. Use a canonical `type` when known; otherwise pass `intent_text`. For hosted demo data with no credentials, use `install_demo_connection`.

List visible Marcopolo connections ready in the execution workspace. Returned names are valid `connection_name` values for `data_query`. Capabilities and workspace paths describe supported workspace commands.

Run a bounded governed query against a visible connection. Use this tool in generated code that re-queries live data at view or load time: Remote Artifacts, external web apps, scheduled scripts, and any other programmatic interface that fetches fresh data on each run. Do NOT use it for agent-side analytics or one-off snapshot visualizations — use the `workspace_shell` tool with the connection query CLI instead. Pass the full workspace-relative `query_file` path including the connection prefix, e.g. `connections/<name>/queries/<file>`. Paths resolve from `/workspace`, not from any current directory. Author new query files through `workspace_shell` before calling this tool so query text is durable and reusable. Returns `rows` as a parsed list of record dicts and `row_count` as the total — no JSON parsing needed. Results are capped by `max_rows` (1–5000).

Install hosted demo data with no user credentials. Pass a demo id or natural-language request. Use `connection_setup` for real user-owned connections.

Run a shell command in the persistent /workspace runtime. Use for all agent-side work: query authoring, analytics, DuckDB joins, workspace files, scripts, git, diagnostics, and cron. The `connection` and `cron` CLIs exist only inside this runtime and must be invoked through this tool.