Apps and integrations
Stand MCP
Connect your agent to Stand over remote MCP to inspect conversations and usage or manage Sites, Stand-ins and website knowledge. The AI host connects to Stand directly, so it does not need the Stand CLI installed.
- Availability
- All plans
- Configured in
- Your AI host’s remote MCP settings → https://app.stand.chat/mcp
- Category
- Apps and integrations
- Reference status
- Current
Before you begin
Plan availability: All plans, within existing feature and usage allowances, where Stand has enabled remote MCP for your host. A compatible, admitted OAuth host is required.
Prerequisite: Remote Streamable HTTP and OAuth support; browser sign-in and consent; completed Stand profile and organization setup; the scopes, membership and resource permissions required for the task.
Key boundary: The 34 tools exclude file and image uploads, history export, conversation writes, billing, account deletion and team-member changes. MCP cannot edit or deploy your website files.
Connection and account access
Add https://app.stand.chat/mcp as a remote MCP server in a host that supports browser OAuth authorization. There is no local server command or CLI package to install. Local MCP support alone does not establish compatibility, and each host’s OAuth client must be admitted by Stand. Some hosts also require a registered client configuration supplied for Stand.
The account holder signs in and approves the requested permissions in the browser. Signup and initial profile or organization setup remain in the Stand app. Authorization applies to the user’s account rather than one Site; every operation still checks current membership, ownership, role and plan allowances.
The connection has no visitor-facing screen. Saved configuration changes affect Stand through the same rules as the underlying API. Reading data does not make a rep Available. Reconnect if the host’s authorization expires; removing a connection does not erase data already retrieved by that host.
What the tools expose
This is a curated set of 34 tools, not every operation in the public API. Use the Stand app or CLI for uploads, exports and other supported operations outside this list.
| Area | Tools and boundaries |
|---|---|
| Identity and usage | Read your identity, profile, plan, usage, permitted statistics, team, recent widget shows and live-chat count. |
| Sites | List, read, create, update and delete Sites; read and replace Site instructions. Installation output must be applied by a person or a host with website-editing access. |
| Stand-ins | List, read, create, update, delete and enable owned Stand-ins; inspect or change Stand-in coverage. New Stand-ins begin disabled. |
| Knowledge | List or create bases, crawl website sources, inspect source/document/task lists, search indexed knowledge, and read or replace a Stand-in’s knowledge attachments. Plan limits still apply. |
| Conversations | Search accessible archived conversations and read an accessible transcript. The tools do not send messages, take over conversations or export history. |
Permissions requested by the host
Each tool declares one required business scope. Write scopes do not include reads, and approving a scope does not make a member an owner. The host can request the permissions needed for its task from these 11 scopes.
| Scopes | Access |
|---|---|
| profile:read, org:read, team:read | Read your identity and profile, plan and usage, or the team. |
| sites:read, sites:write | Read Sites and their instructions, or change them. |
| standins:read, standins:write | Read Stand-ins and coverage, or change them. |
| knowledge:read, knowledge:write | Inspect or search knowledge, or create, crawl and attach it. |
| sessions:read, analytics:read | Read permitted conversations or statistics. |
Results, changes and failures
- List results can be paginated, and transcript reads are bounded. Follow available pagination and report the selection actually inspected. If a result is too large, narrow the query or use a smaller page; MCP does not provide a complete-history export.
- Read existing settings before a write. Collection replacements must retain every intended member. Stand-in updates can return a replacement ID; use that ID for subsequent work. The same owner permissions and browser opt-ins apply as in the public API.
- A write with an uncertain result may already have succeeded. Inspect current state before retrying. There is no general idempotency or configuration-revision guarantee.
- Missing permissions require authorization or an eligible account, not repeated tool calls. Signup, initial onboarding, payment and subscription changes, team-member changes and account deletion remain browser workflows.