Prerequisites
- A Dayalogs account, or a temporary demo session if you only want to try the sandbox
- Permission to connect external AI tools to your organisation when using a real account
- A supported, MCP-compatible AI client
- The Dayalogs remote MCP endpoint
https://www.dayalogs.com/mcp
Try the demo sandbox
You can test Dayalogs without creating an account. Add the MCP endpoint in a compatible AI client and, when the OAuth screen opens, choose Continue in demo.
Demo limits — Demo sessions are isolated, last 24 hours, and can create or import surveys and open preview links. They cannot publish surveys, distribute links, send campaigns or export real responses.
Connect with MCP
Add the remote endpoint, authenticate with OAuth, and your assistant can manage the Dayalogs areas allowed by your account and user permissions.
Local-only clients — A few clients only support local stdio MCP servers rather than remote MCP. A packaged Dayalogs bridge for those is on the roadmap; until it ships, use a client that supports remote MCP.
Add the remote endpoint
Remote MCP endpoint
Use this path for clients that support remote MCP with OAuth. The user signs in through Dayalogs and grants only the permissions needed by the client.
- Open your AI client's connector or MCP settings.
- Add a remote server URL:
https://www.dayalogs.com/mcp. - Authenticate with Dayalogs when prompted, or choose Continue in demo for a 24-hour sandbox.
https://www.dayalogs.com/mcp
Quick guides by client
The Dayalogs endpoint is always the same. What changes is where each AI client lets you register a remote MCP server.
Claude
- Open Customize → Connectors.
- Click + and choose Add custom connector.
- Name it Dayalogs.
- Set the URL to
https://www.dayalogs.com/mcp. - Click Add, then Connect and complete Dayalogs OAuth.
On Claude Team or Claude Enterprise, a Claude workspace owner may need to add the connector first from Organization settings → Connectors. This refers to your Claude workspace role, not your Dayalogs account role.
Grok
- Open Skills and Connectors.
- Select the Connectors tab.
- Click New Connector.
- Choose Custom.
- Name it Dayalogs and set the MCP URL to
https://www.dayalogs.com/mcp. - Choose Connect by OAuth and complete Dayalogs authorization.
ChatGPT / OpenAI
- Use ChatGPT Web. OpenAI custom MCP apps are configured there.
- Enable developer mode from Settings or Workspace settings, depending on your plan.
- Create a custom app and provide the Dayalogs MCP endpoint.
- Choose OAuth when asked, scan tools, then create the app.
- Open a new chat and select Dayalogs from the tools/apps menu.
Codex
Use the same OpenAI app registration path as ChatGPT. Register Dayalogs once from ChatGPT Web, then use it from Codex-compatible OpenAI surfaces when apps/MCP tools are available for that account or workspace.
- First complete the ChatGPT / OpenAI setup.
- In Codex, select the Dayalogs MCP/app tools when the workspace exposes them.
- If Dayalogs does not appear, return to ChatGPT Web and confirm the app is enabled for your account or workspace.
"Can you see Dayalogs capabilities?"
What to try first
Once connected, try these prompts:
"Load the Dayalogs authoring pack and then create a 5-question NPS survey for our post-purchase experience."
"List my Dayalogs surveys and show me the response count for each."
"Validate this survey JSON and tell me what's wrong: [paste JSON]"
"Create a preview link for the survey with slug 'customer-satisfaction-q2'."
Available MCP tools
Tool availability matrix Technical reference for plans, scopes and visible MCP tools.
Once connected, the client only sees tools allowed by the organisation plan and the authenticated user's permissions. The matrix below shows what each plan can enable; user scopes can still narrow the visible tool list.
Sandbox tools are temporary and preview-only. They cannot publish surveys, distribute links, send campaigns or export responses.
View full reference →Troubleshooting
Check whether your client supports remote MCP. If it only supports local stdio MCP servers, it can't connect yet — use a client with remote MCP support.
Remove the existing Dayalogs connection from the client and reconnect through OAuth. Confirm that you select the intended organisation during authorization.
Ask it to load the authoring pack first: "Load the Dayalogs authoring pack." This gives the AI the full schema and examples as context.
Quick reference
Getting help
Still stuck? Contact us.