MCP connections let daoco read and write data in your commerce and site tools through governed connections. You connect providers once on Connections, then inspect or update store and site data from brand chat withDocumentation Index
Fetch the complete documentation index at: https://docs.daoco.org/llms.txt
Use this file to discover all available pages before exploring further.
/mcp or natural language.
Writes use the scopes you grant at connect time. daoco proposes changes in chat first; for SEO or live content updates, confirm the exact diff before anything is published or mutated on the provider.
Before you start
Enable MCP connections for your workspace in Preview Features. Without that opt-in, the MCP tab and/mcp slash command do not appear.
Who provides each MCP server
| Provider | MCP server | What that means |
|---|---|---|
| Shopify Admin | daoco-hosted Shopify Admin MCP | Built and operated by daoco for DAOCO workspaces. Curated tools for catalog, merchandising, inventory, SEO, metafields, bulk updates, and store summaries. Connect with your your-store.myshopify.com domain and Admin API OAuth. |
| Square | Square-hosted remote MCP (Square MCP docs) | Official Square Model Context Protocol server at mcp.squareup.com. daoco connects over OAuth with the scopes you approve. Tool surface follows Square’s API catalog (items, orders, customers, payments, sites, and more). |
| WordPress | WordPress.com-hosted MCP (WordPress.com MCP docs) | Official WordPress.com MCP at public-api.wordpress.com. Requires a WordPress.com account with MCP enabled on your profile. Access matches your WordPress.com role and the read/write tools you enable there. |
Square and WordPress are third-party MCP servers. daoco does not operate those endpoints; we broker OAuth, route delegated chat runs, and enforce approval rules on top of their tools.
Provider capabilities
Shopify Admin (daoco)
Typical read workflows:- List or search products, collections, locations, inventory levels, and metafields.
- Pull product SEO, media, variant, and merchandising summaries.
- Run aggregate product, inventory, and store-summary analytics.
- Create, update, or delete products and collections.
- Update product SEO titles and descriptions.
- Adjust variants, options, inventory quantities, and tags.
- Set or delete metafields; run bounded bulk product updates (often with a preview step before execution).
Square (Square-provided)
Square’s MCP exposes their REST API through tools such as service discovery and API requests. In practice, teams use it for:- Catalog — items, categories, and related catalog data.
- Orders and payments — order lookup, checkout-related data, refunds, and payment context.
- Customers — customer profiles, groups, and segments.
- Merchant operations — locations, inventory, invoices, loyalty, team, and Square Online sites where applicable.
ITEMS_*, ORDERS_*, CUSTOMERS_*). The exact API calls available depend on Square’s MCP tool catalog and your authorized scopes. See Square’s MCP documentation for the full service list and beta status.
WordPress (WordPress.com-provided)
WordPress.com MCP tools are grouped around site content and configuration. Common areas include:- Content authoring — create and update posts and pages (role-dependent).
- Site editor context — inspect site structure and editor-related context.
- Posts search and post details — find and read content across connected sites.
- Site statistics — traffic and performance summaries where your role allows.
- Site settings, users, comments, plugins — available primarily for administrators.
Connect an MCP provider
Complete OAuth
For Shopify Admin, enter your shop domain, then authorize in the popup window. For Square or WordPress, follow the provider OAuth flow.
Manage MCP connections
On the MCP tab you can:- View health: See whether a connection is healthy, retrying, or needs reconnect.
- Review scopes: For Shopify, see which Admin API scopes were granted.
- Reconnect: Re-authorize if tokens expire or the provider revokes access.
- Disconnect: Remove a connection you no longer need.
Read vs write in chat
| Action | How it works |
|---|---|
| Read | Ask for reports, lookups, audits, or summaries. The assistant uses MCP tools to fetch current provider data. |
| Write | Ask to create, update, delete, or publish on the provider. The assistant uses write-capable MCP tools only when your connection scopes allow it and your message clearly requests that change. |
| SEO or live content changes | The assistant maps URLs to real resources, shows a proposed diff, and waits for your explicit approval before applying changes on Shopify, Square, or WordPress. |
/mcp is a fast way to start that kind of work.
/mcp appears in the slash menu only when MCP connections is enabled for your workspace.Limits and safety
- Work runs through delegated, governed MCP access—not arbitrary third-party servers you paste into chat.
- Only Shopify, Square, and WordPress connections you set up on the MCP tab can be used.
- Scopes matter: connect-time OAuth scopes define which read and write tools are allowed.
- Human approval: destructive or live SEO/content changes expect explicit confirmation in the thread before daoco applies them on the provider.
- daoco does not show raw API tokens in chat; tokens stay on the connection record and MCP transport layer.
Troubleshooting
I do not see the MCP tab or/mcp
- Confirm MCP connections is enabled under Preview Features and saved.
- Refresh the page after saving.
- Allow popups for daoco in your browser, then try Add MCP again.
- Open Connections → MCP and reconnect the provider.
- For Shopify, confirm the shop domain and that required Admin scopes were granted.
- The provider may not be configured for your deployment yet. Contact support@daoco.org if you expect it to be available.
- Connect at least one healthy MCP provider on the MCP tab before using
/mcp.
Next steps
Preview Features
Enable MCP connections for your workspace.
Connect social platforms
Link social accounts for posts and scheduling.
Assistants and slash commands
See all slash commands including
/mcp.Brand chat
Continue follow-up work in the same thread.