StageGrow developer docs

Overview

StageGrow (formerly DesignGrow) is the operating system for US home staging companies, from solo stagers to regional operators. It runs projects and schedules, inventory and warehouses, clients and realtors, proposals and contracts, invoicing and collections (AR), and reporting. Every record belongs to one organization; no credential can see another organization's data.

StageGrow has no built-in chat assistant. You bring your own agent (Claude, ChatGPT, OpenClaw or anything that speaks MCP) and connect it to your organization. The rule we build by: anything the web app does, an MCP tool does.

• MCP server (primary agent interface): https://my.designgrow.app/mcp. Streamable HTTP, organization-scoped.
• Docs MCP (public, no credentials): https://my.designgrow.app/docs/mcp.
• OpenAPI contract: https://my.designgrow.app/openapi.json.
• AI Catalog of everything above: https://my.designgrow.app/.well-known/ai-catalog.json.

Connect an agent (MCP quickstart)

The MCP endpoint is https://my.designgrow.app/mcp (the older https://my.designgrow.app/api/mcp serves the same server). Transport is Streamable HTTP; replies are plain JSON, so clients that cannot read an SSE stream work too.

Claude Code, OpenClaw, scripts (API key). An organization owner creates a key in Settings → Developers and picks its scopes. Then:

claude mcp add --transport http stagegrow https://my.designgrow.app/mcp --header "Authorization: Bearer mcp_YOUR_KEY"

Or in a JSON client config:

{
  "mcpServers": {
    "stagegrow": {
      "type": "http",
      "url": "https://my.designgrow.app/mcp",
      "headers": {
        "Authorization": "Bearer mcp_YOUR_KEY"
      }
    }
  }
}

claude.ai and ChatGPT (OAuth). Add a custom connector with the URL https://my.designgrow.app/mcp. The client discovers the authorization server from the 401 response, registers itself, and sends an organization owner to a consent screen. See Authentication.

Status: new OAuth connections are not enabled yet. Until they are, connect with an MCP API key from a client that can send headers (Claude Code, Claude Desktop, OpenClaw).

Check the connection with two JSON-RPC calls:

curl -s https://my.designgrow.app/mcp \
  -H "Authorization: Bearer mcp_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"curl","version":"1"}}}'

curl -s https://my.designgrow.app/mcp \
  -H "Authorization: Bearer mcp_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/list"}'

tools/list returns only the tools your credential's scopes allow, so a read-only key sees a short list. Start with get_workflow and search/fetch; agent role instructions come from list_agent_profiles and get_agent_profile when your organization publishes them.

Authentication

Two credential types reach the MCP server. Both are pinned to one organization.

OAuth details. Authorization code grant with PKCE; only S256 is accepted. Redirect URIs must match a registered URI exactly. Clients register with RFC 7591 dynamic client registration. Access tokens last one hour. Refresh tokens rotate on every use and stop after 30 days without use. Revoking the connector in Settings → Developers ends the refresh token and every access token at once. Only an organization owner can approve a connector, and the grant is pinned to that owner's organization.

Status: new OAuth connections are not enabled yet. Until they are, connect with an MCP API key from a client that can send headers (Claude Code, Claude Desktop, OpenClaw).

• Protected-resource metadata (RFC 9728): https://my.designgrow.app/.well-known/oauth-protected-resource/mcp
• Authorization-server metadata (RFC 8414): https://my.designgrow.app/.well-known/oauth-authorization-server
• Registration: POST https://my.designgrow.app/api/oauth/register; authorize: https://my.designgrow.app/oauth/authorize; token: POST https://my.designgrow.app/api/oauth/token

An unauthenticated MCP request gets 401 with a challenge that names the metadata document:

HTTP/1.1 401 Unauthorized
WWW-Authenticate: Bearer resource_metadata="https://my.designgrow.app/.well-known/oauth-protected-resource/mcp"

Shop keys (scope shop) are a separate credential for the Superb shop MCP and are refused by /mcp.

Scopes

A credential sees only the tools its scopes allow. Pick the smallest set the agent needs: a reporting bot needs read, a collections bot read + finance. There is no unrestricted scope for new keys or connectors.

REST API

Base URL: https://my.designgrow.app/api/v1 (every path also answers unversioned at /api). The full contract, with parameters, error responses and security schemes, is https://my.designgrow.app/openapi.json.

These endpoints serve the StageGrow web app and authenticate with a signed-in session; webhook subscriptions use the Zapier OAuth token. For agents, the MCP server covers the same operations and more.

Webhooks

Subscribe with POST /api/v1/webhooks/subscribe (event_type, target_url, optional secret), authenticated with a Zapier OAuth access token. Events:

Errors and rate limits

Error bodies are JSON with an error field (OAuth endpoints add error_description, per RFC 6749):

{ "error": "Too many requests. Please try again later." }

Burst limits apply per IP on expensive and abuse-prone endpoints, for example OAuth client registration (10 per minute) and public form endpoints (5 to 10 per minute).

Pricing

Every paid plan has a 14-day free trial and a 90-day money-back guarantee. Annual billing saves 20%. Full details: https://my.designgrow.app/pricing.

Inventory management is an add-on available on every plan:

Discovery files

Need help? Email support@designgrow.app.