Getting started

The console walks you through ten steps. You can leave and continue later; it resumes where you stopped.

1. Request access at mcpconsole.deemwar.com/signup; when approved, sign in at mcpconsole.deemwar.com/signin with that email: we email you a one-time sign-in link (or a 6-digit code).
2. Point at your API. Paste a base URL or an OpenAPI/Swagger URL, or upload the spec file. We probe the usual paths (/openapi.json, /swagger.json, /v3/api-docs and more), parse the operations and group them. If no spec is found, upload one.
3. Questions. What the API is for (shown to the AI as the overview), who uses it, and which actions are sensitive.
4. Review tools. Enable or disable operations, edit summaries and groups, and mark sensitive ones as needing confirmation.
5. Sign-in. Choose how your users sign in (Sign-in methods) and test each method.
6. Roles. Map a claim in your users’ JWT to the operations each role may call (Roles & confirmations).
7. API docs. Your OpenAPI operations are always included; add guide URLs or files (API docs & ask_docs). Publishing waits until the docs are built.
8. Validate. Sign in as a test user (a token, or a username and password against your login endpoint). We call one operation per group and show pass or fail with the HTTP status. Test credentials are used for that request only.
9. Ready. Approve to publish. You get the endpoint URL and copy-paste connect instructions for every client.
10. Get widget. List the sites allowed to use the widget and copy the script tag (Chat widget).

Before you can approve

Approval needs:

• at least one enabled operation,
• an upstream URL,
• at most 15 groups,
• built docs.

When your API changes

Run discovery again: the console shows what changed against the published version and keeps your edits.