Get started

What is Parlo?

Parlo turns cloud drives and APIs into folders you can use from a shell, script, editor, or agent.

Parlo makes remote resources feel local.

Connect a cloud drive or API, then use it under ~/parlo like a regular folder:

bash

5 lines

1parlo mount2cd ~/parlo3ls4 5# main  github  linear  stripe

Example layout:

bash

5 lines

1~/parlo/2  main/        # cloud-backed files3  github/      # GitHub issues, PRs, repos4  linear/      # Linear issues and projects5  stripe/      # Stripe customers, invoices, subscriptions

Use normal file commands on any of them:

bash

4 lines

1ls github/issues2cat github/issues/42.md3grep -R "billing" github/issues linear/issues4cp ./notes.md main/reports/notes.md

The core idea: cloud drives and APIs become paths.

Why this helps

Normally, every service needs its own app, SDK, API client, or agent tool. Parlo gives them a shared shape:

bash

1 line

1folder -> file -> read or write

Humans, scripts, and agents can all work the same way.

Simple example

Say you need to investigate a billing bug.

bash

13 lines

1cd ~/parlo2 3# Find related issues.4grep -R "billing\|invoice\|subscription" github/issues linear/issues | head5 6# Read the useful files.7cat github/issues/42.md8cat linear/issues/ENG-123.md9cat stripe/customers/cus_8x92.md10 11# Save the result to a cloud-backed drive.12mkdir -p main/reports13vim main/reports/billing-bug.md

No separate GitHub tool, Linear tool, Stripe tool, or Drive tool. Just paths.

Read the README first

Every connection explains itself:

bash

1 line

1cat github/README.md

Example output:

bash

11 lines

1# GitHub2 3Useful paths:4- issues/5- pulls/6- repos/7 8Examples:9  ls issues/10  cat issues/42.md11  grep -R "billing" issues/

Native mount or direct commands

Best experience:

bash

3 lines

1parlo mount2cd ~/parlo3cat github/README.md

Fallback for CI, containers, or restricted sandboxes:

bash

3 lines

1parlo ls github/issues/2parlo cat github/issues/42.md3parlo write main/reports/report.md --from ./report.md

Same data, different access mode.

What Parlo is for

You want to...	Use Parlo to...
Work with cloud files	mount them as local folders
Read API data	expose it as markdown files
Update supported resources	edit or write files
Delete a remote resource	`parlo rm` (gated by policy, opt-in per client)
Connect a new API instantly	paste an OpenAPI, GraphQL, or MCP URL on the connections page
Give agents access	use `ls`, `cat`, `grep`, and writes instead of large tool lists
Find tools by intent	semantic `toolSearch` via vector similarity, not just name matching
Use drives from an MCP client	MCP `toolList` returns drives; `toolUse` accepts a `drive` target
Search big repos	use `parlo rg` without cloning

Next steps

Goal	Read
Install and try it	Quickstart
Understand file operations	Filesystem model
Connect an API	API connections
Use cloud drives	Cloud drives
Use with agents	Coding agents

Quickstart