Supported actions
Read brand context, chat with the brand agent, and read brand content through the current MCP capability set.
MCP + INDOO
Give compatible AI clients secure, brand-scoped Indoo context.
Connect compatible AI clients and automation tools to brand context, agent chat, and content reads using a revocable brand-scoped MCP token.
WHAT MATTERS
The operating details behind the promise.
Setup
Generate a token, copy it immediately, add the Streamable HTTP endpoint to the client, and send the token as a Bearer credential.
Limitations
Tokens are brand-scoped, shown once, and should be rotated if exposed. The current integration does not advertise unrestricted write access.
HOW IT WORKS
Move from context to accountable action.
Every stage keeps the brand, goal, evidence, permissions, and work history attached.
- 01
Create a scoped token
Choose the intended brand and generate a credential only for that connection.
- 02
Configure the client
Add the endpoint as a Streamable HTTP server and store the Bearer token securely.
- 03
Rotate deliberately
Revoke or replace the token when a client, person, or automation should no longer have access.
INDOO PRINCIPLE
Treat MCP tokens as credentials. Keep read and write authority narrow, use separate tokens where practical, and never place tokens in public client code.
COMMON QUESTIONS
Direct answers, then the details.
What can the Indoo MCP server expose?
The current product describes brand context, agent chat, and content read capabilities for a brand-scoped connection.
Can an MCP token access another brand?
Tokens are created for a specific brand and should be enforced at the same tenant and brand boundaries as the web product.
ONE BRAND BRAIN · ONE LOOP
Put this workflow to work on your real brand.
- No payment card in signup
- Website-first brand setup
- Human approval available