> ## Documentation Index > Fetch the complete documentation index at: https://docs.daoco.org/llms.txt > Use this file to discover all available pages before exploring further. # AI apps > Connect AI assistants and agent systems to daoco, understand the MCP tools, and follow marketing work. daoco works as an MCP server. Connect it to an AI app you already use and that app can read what your brand knows, hand daoco marketing work, and check on it. The work runs in daoco as an ordinary brand chat, so it shows up in your sidebar and uses your workspace's tokens like any other chat. Each AI app working in a brand is a **connected assistant**, next to your personal and team assistants. Each personal, team, and connected assistant uses one of your workspace's assistant slots. An app that is turned off holds no slot. When the slots are full, an app cannot start working in a brand until you turn another app off or delete an assistant. Every plan has the same number of slots; [contact us](mailto:support@daoco.org) if you need more. ## What a connected app can do * List the brands you can work in and pick one. An app works in one brand at a time until it picks another. * Read brand context: voice, positioning, audience, colors, typography, logo, and brand documents. * Start marketing work in the brand, in your words: research, campaigns, posts, articles, images, video, SEO. * Follow a thread's progress and latest update, and reply in it. * List recent threads, drafts, and what is waiting on a person, each with a link into daoco. A connected app cannot approve, publish, or schedule anything. When work needs a decision, the app gives you a link and you decide in daoco. A reply into a thread that is waiting on an approval is refused with the approval's link. ## Connect an app The server address is `https://backend.daoco.org/mcp`. You need a daoco account and access to a workspace with a brand. Selecting a brand requires a free assistant slot; starting or continuing work uses that workspace's tokens. Start from daoco or from the app. In daoco, open the **Assistants** page, choose **Create** on **Connected assistant**, pick your app, and follow its steps; the page shows when the app has signed in. In the app, add the address as a custom MCP connection and sign in. The same details are under **Settings > Account > AI apps**. Custom connections and public directory listings have separate availability. These instructions describe adding daoco by address. Use a directory's daoco listing only when it is available in your app; supporting MCP does not guarantee that an app lists daoco or supports our OAuth flow. Your app's plan and administrator settings may restrict custom connections. In Claude, open **Settings > Connectors**, choose **Add custom connector**, and paste the address. Sign in with your daoco account when asked. Open **Plugins > Add > Create MCP App**, paste the address, choose **OAuth**, and sign in with your daoco account. If your account shows Apps instead, turn on developer mode under **Settings > Apps** and create an app there. Open **Plugins > New Connector > Custom**. Give the connector a name, paste the server address, and choose **Add Connector**. Sign in with your daoco account, choose your workspace, and allow access. In chat, ask Grok to use that connector to list your brands and select one. Daoco's connection to Muse has not yet been verified end to end. Connection steps will be added after testing. Meta's [Muse connector directory](https://muse.ai/platform/docs) requires a separate submission and review; adding daoco to another MCP directory does not make it available in Muse. ```bash theme={null} claude mcp add --transport http daoco https://backend.daoco.org/mcp ``` Then run `/mcp` in Claude Code to sign in. ```bash theme={null} codex mcp add daoco --url https://backend.daoco.org/mcp codex mcp login daoco ``` For other AI assistants and agent systems, choose a remote MCP connection with **Streamable HTTP** and **OAuth**, add the address, and sign in. Client compatibility must be tested for each app. For Perplexity, its [custom remote connector guide](https://www.perplexity.ai/help-center/en/articles/13915507-adding-custom-remote-connectors) describes **Account settings > Connectors > Custom connector > Remote**, with the server URL, OAuth, and Streamable HTTP. For Cursor, its [MCP setup guide](https://cursor.com/help/customization/mcp) describes adding a server URL to `mcp.json`. These are client setup references; daoco compatibility has not yet been verified end to end for these clients. This address connects directly to daoco's backend. If you previously added a `convex.site` address or `https://daoco.org/mcp`, update the server address in your app and sign in again. OAuth tokens are issued for the configured server address. ## Follow marketing work Ask your app to list your brands, select the one you want, and hand daoco your request. For example: * "Use my Acme brand and tell me its voice and target audience." * "Draft three LinkedIn posts for Acme's product launch and keep me updated." * "Make the second post shorter and show me what needs review." Work can take minutes. Starting a thread confirms that work has started; check its status to find out whether it has finished. Your app can answer a clarification or request changes in that thread. When approval is needed, open the returned daoco link and decide there. ## MCP tool reference The server exposes these tools to authenticated clients. All tools except `list_brands` and `use_brand` require a selected brand. Reads return brand data or work summaries; writes select a brand or create a message in a durable daoco thread. | Tool | Access | Inputs | Result or effect | | - | - | - | - | | `list_brands` | Read | None | Accessible brands and the app's selected brand. | | `use_brand` | Write | `brandId` | Selects the brand for subsequent calls, subject to membership and available assistant slots. | | `get_brand_context` | Read | None | Brand identity, voice, audience, positioning, visual identity, and documents. | | `find_drafts` | Read | Optional `text`, `days` | Recent unpublished post drafts and review links. `days` defaults to 30 and accepts 1–365. | | `list_needs_you` | Read | None | Approvals, questions, and failures with links to act in daoco. | | `list_recent_work` | Read | Optional `limit` | Recent threads with IDs, status, and links. Default 10, maximum 25. | | `start_work` | Write | `request` | Starts marketing work and returns `threadId`, `status`, and `url`. Request maximum 8,000 characters. | | `continue_work` | Write | `threadId`, `message` | Sends a follow-up or queues it while the thread is working. Refuses replies to threads awaiting approval and returns a review link. Message maximum 8,000 characters. | | `get_work_status` | Read | `threadId` | Status, plan, latest update, and thread link. | Poll status no more than once every 20 seconds. `start_work` and `continue_work` are not idempotent. If a connection drops after a write, check recent work and the thread's status before retrying to avoid creating duplicate work or messages. There is no MCP tool to cancel a run; manage the thread in daoco. Tool results include text and, on success, structured data. A tool result with `isError: true` reports a failed call. Missing or expired authentication returns HTTP 401 and requires sign-in; a disallowed browser origin returns 403. A missing account, lost workspace access, a turned-off app, unavailable assistant slots, or insufficient tokens can block a tool call. Follow the returned explanation or daoco link before retrying. ## Authentication and data access OAuth sign-in uses WorkOS AuthKit. The protected resource metadata is at `https://backend.daoco.org/.well-known/oauth-protected-resource/mcp`. The advertised scopes are `openid`, `profile`, `email`, and `offline_access`. Workspace membership determines which brands the person can access; these scopes do not grant access to other workspaces. Connected apps receive the brand context, draft content, and thread information requested through their tools. Work requests and follow-ups are stored as ordinary daoco chat messages. Review your AI app's data policies before sharing brand documents or customer information. Turning off an app stops its MCP access; deleting its connection does not delete marketing work already created in daoco. ## See and turn off connected apps Connected assistants appear on the **Assistants** page in their own **Connected assistants** section, since each app picks the brand it works in, and in **Settings > Account > AI apps**. An app appears after its first request, however you added it. Open an app for its page. Until the app works in a brand, the page keeps the setup steps and says what it is waiting for. After that it shows the brand the app works in, what needs you, and the threads it started or continued; **Connection** holds who connected it, when it last worked, and the steps to add it again. Ask the app to list your brands and pick one. The person who connected it, or a workspace admin, can switch its brand on its page. **Turn off** stops the app at once and frees its slot; **Allow again** restores it if a slot is free. **Delete app** (under the **⋯** menu) removes it and frees its slot, but if Daoco is still added in the app, it comes back the next time you use it there. The person who connected an app, or a workspace admin, can turn it off or delete it. An app loses access to a brand as soon as you leave its workspace. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.