This article walks you through connecting an AI assistant, such as Claude, to your DailyStory account using the Model Context Protocol (MCP). Once connected, the assistant can answer questions about your marketing data and, with your permission, create, edit and schedule emails. For what an assistant can do once it is connected, see Connect AI Assistants to DailyStory with MCP.
The assistant works as you: it signs in with your DailyStory login and can never do more than your own permissions allow.
Your MCP server address is the address you sign in to DailyStory at, followed by /mcp.
| If you sign in to DailyStory at | Your MCP server address is |
https://us-1.dailystory.com | https://us-1.dailystory.com/mcp |
| Your company's own DailyStory domain | That domain followed by /mcp |
Opening the address in a web browser brings you back to this documentation. That is expected: the address is meant for your assistant, not your browser.
Claude calls an MCP server it connects to a custom connector. Custom connectors work in Claude on the web, in Claude Desktop and in Cowork, on every Claude plan. Free plans are limited to one custom connector.
Each person's connection uses their own DailyStory login and permissions, so two people using the same connector can see and do different things.
To use DailyStory in a conversation, click the + button at the bottom left of the chat, choose Connectors, and turn on DailyStory.
In a terminal, add DailyStory as a remote MCP server, using your own MCP server address:
claude mcp add --transport http dailystory https://us-1.dailystory.com/mcpThen start Claude Code, run /mcp, choose dailystory and sign in. Connectors you have added in Claude on the web are also available in Claude Code when you sign in with the same Claude account.
Any assistant that supports remote MCP servers with OAuth sign-in can connect. Add DailyStory as a remote (sometimes called custom) MCP server using your MCP server address. The assistant then opens DailyStory's sign-in page, where you sign in and approve the permissions it asks for. DailyStory API keys cannot be used.
When you sign in, DailyStory shows which permissions the assistant is asking for, such as reading your contacts or creating emails. Approving them lets the assistant use the matching tools; see Permissions you grant for the full list.
Ask the assistant: "Which DailyStory account are you connected to?" It should name your account and your login, and list what this connection may do.
| What you see | What to do |
| The assistant says AI assistant connections are turned off for the account | An administrator can turn them back on under Settings > Login and Permissions > Connected Apps. If DailyStory turned them off, contact DailyStory support. |
| The assistant says the account or your login has not been verified | Complete verification in DailyStory, then try again. |
| The assistant can read your data but cannot create or schedule emails | The permission was not approved, or your role does not include it. Disconnect and connect again, approving the permission, or ask your administrator about your role. |
| The assistant asks you to sign in again | Connections that go unused for 30 days expire. Sign in again to reconnect. |
| Connecting fails with an API key | MCP only accepts DailyStory sign-in. Remove the API key and use the sign-in flow instead. |
Go to Settings > Personal Settings > Connected Apps and click Revoke next to the assistant. It loses access immediately. Administrators can revoke anyone's connection under Settings > Login and Permissions > Connected Apps. See Manage connected apps.