Use MarcoPolo MCP with
Sokko.
Connect MarcoPolo MCP and tell Sokko what to do. It runs the actions you ask for and reacts to what happens. No workflows, no code.
Works with 1,000+ tools · No code required
Actions
Everything Sokko can do in MarcoPolo MCP
Every MarcoPolo MCP action Sokko can run. Ask for one in a sentence and it's done.
Connection setup
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`.
Connections list
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.
Data query
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 demo connection
Install hosted demo data with no user credentials.
Pass a demo id or natural-language request. Use `connection_setup` for
real user-owned connections.
Workspace shell
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.
Get connected
Live in your Slack in two minutes.
No workflows to wire up. Turn on the tools you already use, and your agent gets to work.
Add to Slack
1
Add Sokko to Slack
One click from the Slack marketplace. Your whole team gets Sokko at once.
2
Connect your tools
Sokko works with 1,000+ apps and any MCP server.
Martin
9:53 AM
@Sokko
What can you do with MarcoPolo MCP?
3
Put Sokko to work
@mention Sokko in any channel and it gets going. Minutes, not a weekend.
Questions, answered.
Sokko is an AI assistant that lives in your Slack. Connect your apps, ask for what you need in plain language, and Sokko takes the work off your plate.
Sign up to Sokko, ask Sokko to connect to MarcoPolo MCP, and approve the connection when prompted. From then on you can ask Sokko to do things in MarcoPolo MCP whenever you need.
No. There's nothing to build or configure. You ask Sokko in Slack the same way you'd ask a colleague, and Sokko handles the rest.
Yes. Ask once and tell Sokko when to repeat it, like every Monday at 9am, and it becomes a routine that runs without you.
Read and act on data in MarcoPolo MCP, and trigger workflows when something changes there. Tell Sokko the outcome you want and it handles the rest.
Yes. Sokko connects to 1,000+ apps and any MCP server, so you can ask for tasks that span MarcoPolo MCP and the rest of your stack in a single request.