How to connect Claude to your X DMs

What you need

• A Claude account that can add custom connectors. Anthropic decides which plans can do this, and it changes from time to time, so check their help pages if you cannot find the option.
• A Spaces account. Your trial starts when you connect a chat account, with no card needed.
• The X account your customers already message you on.
• A short note about your business: what you sell, prices, opening hours and the things you never want promised. You will paste it into Claude later.
• About ten minutes for the setup, and a little longer to try it on a few real messages.

Step 1: connect your X account to Spaces

You sign in to X through a secure link and approve the connection. Your account stays yours, and you keep using it on your phone as normal.

Once it is connected, the account shows in your Spaces dashboard. Connecting does not send anything. It only means Spaces can read and send on that account when an AI agent you have added asks it to.

Connect the X account people DM about your events, such as the venue or festival account. Claude will be able to read every DM on it.

Step 2: add Spaces to Claude

1. Open Customize, then Connectors, then Add custom connector.
2. Name it Spaces and paste https://api.spacesos.com/mcp as the URL.
3. Choose Sign in, then sign in to Spaces and approve access.
4. On a Team or Enterprise plan, an owner adds it once under Organization settings, then Connectors.

To check it worked: Open the Search and tools menu in a chat. Spaces and its tools are listed.

You sign in on Spaces' own page during this step, so Claude never sees your X login or your Spaces password. If Spaces does not show up:

• Open a new chat and check the Spaces connector is turned on in it.
• Sign in to Spaces again from the connector, in case the first sign-in did not finish.
• Remove the connector and add it again, checking the address is exactly https://api.spacesos.com/mcp.
• If it still does not appear, Anthropic's help pages have their current steps, and our Claude setup page has ours.

Step 3: try it

Open a new chat in Claude, make sure Spaces is turned on, and ask in plain words:

• Show me the X DMs about Saturday's gig that still need a reply.
• Summarise the long DM thread with Priya and tell me what she is asking for.
• Draft replies to the access questions from the Project notes, and wait for my OK.
• From last month's DMs, list the ten questions people asked most.

Start with a question that only reads, like the first one. It shows you that Claude can see your X messages before you let it send anything. Then try a draft, read it carefully, and only then let it send.

Good to know

Claude acts when you ask it to in a chat. It does not watch your inbox on its own. For replies around the clock, use an agent that runs all the time, such as Claude Code, Codex, OpenClaw or Hermes, or set up a Spaces routine that sends set replies to set questions.

In practice, treat Claude as a quick helper you sit down with a few times a day: first thing, at lunchtime and before you close. Each time, ask what came in, check its drafts and let it send the ones you are happy with. Customers who message in between wait until your next session, just as they would if you were answering by hand.

A Spaces routine is not an AI. It sends a reply you wrote in advance when something happens, such as a new message or a keyword. That makes it a good way to send "Thanks for your message, we will reply first thing tomorrow" after hours, while Claude writes the real answers in your next session.

Keep one Claude Project for your X DMs, with door times, access details and the ticket rules in its instructions, and start every DM session from inside it.

What Spaces does on X

Spaces works with the direct messages on your X account: listing them, reading whole threads, and replying in the conversation. Public posts and replies are not part of what Spaces does on X. For a venue that is a good split: you post the announcements yourself, and Claude helps with the questions people send privately afterwards.

Keep your event details in a Claude Project

A Project keeps instructions and files together, and every chat you start inside it begins with them. Create one called something like "X DMs" and put the facts that people ask about in its instructions:

You help me answer X DMs for The Lantern, a 300-capacity music venue.
Doors: 7pm unless the event page says otherwise. Last entry 10pm.
Access: step-free entrance on Mill Lane, accessible toilet, a viewing platform. A free companion ticket for anyone who needs one: ask them to email access@ with the event name.
Tickets: we cannot change names or refund in DMs. Point people to the ticket seller's help page.
Bags: small bags only. No large bags or cases.
Age: 14+ with an adult, unless the event page says 18+.
Tone: friendly, plain, short. Use their first name if we know it.
Never: promise a refund, a name change, a guest list place or a set time we have not published.
Leave for me: complaints, press, artists and their teams, anything about safety on the night.

Add the current event list as a file in the Project and replace it each week. Claude can then answer "is Friday sold out?" from what you gave it, and say so when it does not know.

A worked example: the week of a sold-out gig

Here is a session for a small venue two days before a sold-out show. Names and details are examples.

Claude left the set time because the note says never to give one that has not been published, and it left Priya because reselling tickets is a judgement call. That is the right instinct for a public-facing account: answer the facts, pass on the decisions.

Long threads are where Claude helps most

Some DM threads run to twenty messages over three days, with the real question buried halfway down. Ask Claude to read the whole thread and give you three things: what the person wants, what they have already been told, and what is still open. You then reply to the point rather than starting again.

1. Ask: "Summarise the thread with Priya in three lines."
2. Ask: "What have we already told her?" so you do not contradict an earlier reply.
3. Decide the answer yourself if it is a judgement call.
4. Ask Claude to draft the reply in your tone, read it, and send it.

Turn a month of DMs into better information

The questions people DM are the questions your event pages do not answer clearly enough. Once a month, ask Claude to read the month's DMs and list the most common questions, with a suggested answer for each. Then add the answers to your website or ticket pages.

The DMs do not stop, but they get shorter, and more of them can be answered with a link. Claude reads your DMs through Spaces for this. It does not post anything or change your website, so you stay in charge of what goes public.

What to let Claude answer

Common mistakes to avoid

• Forgetting to update the event file, so Claude says a gig has tickets when it has sold out.
• Letting Claude promise a refund or a guest list place to calm someone down.
• Answering access questions with a guess. Keep your exact access wording in the Project.
• Using DMs to tell past attendees about the next event. Post it publicly instead.
• Expecting Claude to answer on the night while you are working the door. It acts only when you ask.

Summing up

With Spaces, Claude can read and answer the DMs on your X account from the facts in a Claude Project. Keep the event file current, let Claude handle door times, access and bag rules, keep refunds, set times and safety for yourself, and use each month's DMs to make your event pages clearer.

How Spaces keeps your account safe

Whatever you ask, Spaces keeps your X account inside safe limits: at least 20 seconds between messages, up to 100 a day, and 20 new conversations a day at most, with a gentler start for a newly connected account. If your AI tries to go faster, Spaces holds the message and says when it can try again.

New conversations warm up over the first weeks after you connect:

These are Spaces' own limits. They lower the risk of a restriction, but they cannot remove it, because X makes its own decisions about accounts. Read the note at the top of this page before you connect.

Pricing

Plans from $19 a month

Can Claude post event updates on X for me?

No. Spaces works with DMs on X, and public posts and replies are not available. Post announcements yourself, and let Claude help with the questions that follow.

Will Claude answer DMs on the night of an event?

Only when you ask it in a chat. Claude does not watch your DMs on its own. A Spaces routine can send a set reply, such as pointing people to the event page, when a new DM arrives.

Can my team use the same set-up?

Yes. On a Claude Team or Enterprise plan, an owner adds the connector once under Organization settings. Agree who handles DMs when, so two people do not answer the same thread.

Does Claude see my X login?

No. You sign in to X on Spaces' secure link, and Claude signs in to Spaces. Claude never sees your X password.

What if Claude does not know the answer?

Tell it in the Project instructions to say it will check and to leave the DM for you. A short honest reply beats a confident wrong one, especially about access or tickets.

How fast does Spaces send the replies?

At least 20 seconds apart, and up to 100 messages a day once the account has settled in. A newly connected account starts lower and warms up over a few weeks.

Can Claude send DMs to people who bought tickets?

Spaces can start a DM with a username within tight new-chat limits, but X restricts unrequested messages. For a change to an event, post it publicly and email ticket holders through your ticket seller.