Skip to main content

Agents & connected apps

You can connect AI agents and other tools to your DFOS account, so they can work in your spaces on your behalf. This is open to everyone — no waitlist, no approval. A connected agent acts as you, so the whole model rests on connecting only tools you trust.

Connecting an AI agent​

DFOS speaks the Model Context Protocol, so agents like Claude can work with your spaces directly. In Settings → MCP you'll find your connection URL — copy it and paste it into your agent's connector settings.

When the agent first connects, DFOS shows you a consent screen with the account it's connecting as, and nothing is connected until you approve. The agent signs in as you the same way you do — there's no password to hand over and no separate key to manage.

What a connected agent can do​

A connected agent works as you: it can do the everyday things you can do in your spaces, and it can't do anything you couldn't. In broad strokes, that means it can:

  • Read what you can read — your spaces, posts, chat and direct messages, notifications, and members, all scoped to what you already have access to.
  • Post and comment in the spaces you're in.
  • Send messages, in space chat and in direct messages.
  • Search across your spaces for people, posts, and conversations.
  • Join and take everyday actions — join a space, follow someone, react, bookmark, and the like.
  • Read these docs, so it can look up how something on DFOS works before it acts.

It's your account in an agent's hands. It sees what you see — including your private messages — and acts under your name, so treat connecting an agent like handing someone your keys.

Authorizing a device​

Command-line tools use a different flow: the tool shows you a short code, and you enter it at DFOS to approve that device. The approval screen shows you the requesting device's details before you confirm.

Treat this one with the same care — an authorized device gets full access to your account, so only approve a code from a device you recognize and a tool you trust.

Staying in control​

A few habits keep agent access safe and predictable:

  • Connect tools you trust, and understand their scope. An agent acts as you and can reach everything you can, private messages included. Only connect software you'd trust with that.
  • Give clear intent. An agent does what you ask, so be specific about what you want it to do — and, especially early on, review what it posts or sends before it goes out.
  • Only approve prompts you started. Approve a connection or a device code when you're the one who kicked it off. If a consent or device screen appears and you didn't initiate it, don't approve it.