# Two MCP servers: one for your account, one to build a demo from your code.

> DemoPage has two MCP servers. The account server at app.demopage.io/api/mcp uses an account key and offers eight tools for team, connections, demo links, and events. The vendor server at app.demopage.io/mcp uses Sign in with DemoPage and lets a coding agent send candidate pages that stay unpublished until you approve them.

Page: https://demopage.io/integrations/mcp · Last reviewed 2026-10-26

## The account server

JSON-RPC at https://app.demopage.io/api/mcp, with an account key as a bearer token. Its tools match the account API.

| Tool | What it does |
| --- | --- |
| get_account | Read the account, team, connections, and recent events. No key secrets. |
| list_team | List the people on the account. |
| add_team_member | Add an admin, AE, or SE. Doesn't email them or create a login. |
| list_connections | List HubSpot, Salesforce, Zapier, Calendar, and Chili Piper, and whether each is connected. |
| connect_tool | Record that a tool is connected. DemoPage doesn't call or write to that tool. |
| disconnect_tool | Remove a recorded connection. Nothing changes in the other tool. |
| list_demos | List the demo links. Doesn't start a demo. |
| record_event | Store a contact, booking, or demo request from a connected tool. |

## The vendor server

Streamable HTTP at https://app.demopage.io/mcp. Without a token it answers 401 and points the client at its OAuth metadata, so the client can start Sign in with DemoPage (OAuth 2.1 with PKCE). The server card is at https://app.demopage.io/.well-known/mcp/server-card.json.

- Call demopage_status first, then demopage_list_pages.
- Send each screen's title, its https address on your product's domain, a short visible text, and a one or two sentence description with demopage_import_pages. Send nothing else from the code.
- Pages arrive held. Approve only the ones you pick with demopage_approve_pages.
- Checkout, billing, API key, password, 2FA, sign-up, and account deletion screens are refused.

## Limits

- The MCP connection alone can't read a repository. A coding client with local file access reads the code and sends only candidate-page fields.
- The account server stores connections and events. It writes nothing to HubSpot, Salesforce, a calendar, or Chili Piper.

## When not to use DemoPage for this

- Starting a demo for a visitor. Neither server starts a visitor's demo.
- Reading source code. The server receives only the fields you send.

## Questions

**Which MCP server do I need?**
The account server if you manage connections and events with an account key. The vendor server if a coding agent should map your product's screens for a new demo.

**How does the vendor server sign in?**
OAuth 2.1 with PKCE, started by Sign in with DemoPage. Tokens are stored as hashes and end when the password is reset.

**Does connect_tool change my CRM?**
No. It records that a tool is connected. DemoPage doesn't call that tool and doesn't write to it.

## Related

- [All integrations](https://demopage.io/integrations.md)
- [Build your demo from your code](https://demopage.io/docs/ai-tools.md)
- [Demo guardrails](https://demopage.io/demo-guardrails.md)
- [How AI agents can use DemoPage](https://demopage.io/agents.md)

## Try it free

Start free at https://app.demopage.io/signup with a work email; no card. See it first: https://app.demopage.io/d/demopage.