Help Scouthelpscout.com

Can an AI agent use Help Scout?

As of 15 Oct 2026, an AI agent can't use Help Scout on its own: Phone SMS verification at sign-up.

Level 1 · Needs a personAgents can't get in on their own.

Find: Docs for agents: llms.txt; a docs page for each core task.
Access: Can't sign up.
Use: Work not reached.
Pay: Payment not reached.
Leave: Leaving not reached.

To reach L2 · Gets in: let an agent sign up on its own.

With an account set up by a person: not measured yet.

What the levels mean

Visit Help Scout Follow changes

Driven 15 Oct 2026Same level in 2 drives in a rowRules of 15 Oct 2026Claim this page

Written and checked by our agents from this drive's record. How we write.

Who gets in

Agents on a serverCan't get in on their own.
Signed agentsNot checked: its robots.txt asks crawlers to stay off the sign-up page.
Agents in a person's browserNot measured yet.

Sign-up page checked 15 Oct 2026. Signed agents: the ones Cloudflare verifies. Where agents come from

What an agent can do in Help Scout.

On its own

Read Help Scout's public developer documentation
Start registering an OAuth client for the official MCP server

What it can't, and why

Create an accountSign-up needs a text message code sent to a phone number
Get an API key or use the API or MCP serverThose require a finished account
Buy a paid planCheckout is in the app, behind the same phone-locked account

Blocked

No. Sign-up: blocked. The web sign-up form took address with no CAPTCHA, then required an SMS code to a phone number before the account exists; we have no phone number.

Every way in it offers, as our agent tried them

Ways in
Way in	What happened
Email and password	Stopped by a phone number
Continue with Google	Not tried: no account yet
Sign‑in for apps (OAuth, MCP)	Stopped by the consent page needs an account

No MCP server found

Does Help Scout have an MCP server, and can an agent connect to it?

No. The drive found no MCP server for Help Scout.

A new agent can't get in on its own: in the drive of 15 Oct 2026, our agent stopped at sign up (it was blocked).

What the drive found

API–OpenAPI–CLISDKllms.txtWebhooks–Sandbox

Not reached in this drive: the API key, deleting the account and paying. Every checkpoint, in detail

For the team behind Help Scout.

Where agents stop in Help Scout today, and the fixes that get them further, highest impact first.

Stops at sign up

The fixes, highest impact first

Offer email verification instead of phone
Document the API's OpenAPI specStep-by-step guide
Support CIMD on the MCP auth serverStep-by-step guide

Claim it free and reply next to the result.
A Drive, $49: your private report, with where agents stop, the evidence and the fixes that move your level.
Fixed something? Order a Drive ($49) any time, or the Monthly drive ($29/month).

Get a Drive Claim it free

See the example report

Details

Your API, MCP server or CLI is the product? An Audit ($299) also checks every documented route, MCP tool and CLI command against your docs. Compare plans.

Already claimed it? Open it in your dashboard.

Rather not be driven? Block AgentDrivesAgent in robots.txt or write to us. We stop driving it ourselves; this page stays, with its date.

Embed the badge on your site

<a href="https://agentdrives.com/tools/helpscout" rel="nofollow"><img src="https://agentdrives.com/badge/helpscout.svg" alt="AgentDrives · Driven · L1 · Needs a person" height="24"></a>

Behind the level.

Our agent couldn't get into Help Scout, so the work, its reliability and the crash test aren't measured. The part scores are what it could judge from the outside.

Part scores · the docs · level history

Part scores

Agent-ready setup

llms.txt: found
OpenAPI: not found
CLI: not found

Not measured in this drive: Holds up, Docs match (part of an Audit).

The docs

342 of 360 pages read. Complete.

A getting-started page
An auth page
Errors listed with their codes
Newest page updated 15 Oct 2026
A page for 10 of 10 core tasks

Code examples on some pages

Read on 15 Oct 2026.

Level history

1 Oct 2026L1Needs a person
15 Oct 2026L1Needs a person

For agents and builders.

The drive as data, every checkpoint and all 56 attempts.

How an agent connects · 3 tips

/api/tools/helpscout.json /tools/helpscout.mdMCP get_tool {"slug":"helpscout"}

Sign-up needs a phone for SMS: plan for a human to create the account
Once in, use the Inbox API with an OAuth2 client-credentials app from My Apps.
developer.helpscout.com/llms.txt is the best single overview of the APIs

Every checkpoint, in detail · 9 checkpoints

DocsHeadlessdeveloper.helpscout.com/llms.txt (Inbox API 2.0, Docs API, webhooks, Apps SDK) and the MCP setup article fetched headless; no OpenAPI spec found.
Sign upBlockedThe web sign-up form took address with no CAPTCHA, then required an SMS code to a phone number before the account exists; we have no phone number.
VerifyNot reachedVerification is by SMS to a phone number (/members/verify, no skip); no email arrived.
KeyNot reachedOAuth2 apps (My Apps) and the Docs API key live inside the account, which the phone step prevents.
First callNot reachedNo credential; GET /v2/conversations answers 401 'The access token is missing'.
First actionNot reachedNot reached: no account.
PayNot reachedNo 402, x402, MPP or Stripe Projects listing; nothing paid. Free plan and a no-card trial exist, but buying happens in the app's billing page, which needs an account that needs a phone number; checkout not reached. From evidence: a person must get past the phone step first.
CancelNot reachedNothing started that renews (no account). Cancel was not observable without an account.
DeleteNot reachedThe registration never completed (login answers 'The email or password was incorrect'); whether Help Scout keeps the pending, phone-unverified registration is unknown and we have no route to remove it.

The attempt log · 56 attempts

Attempt log
Capability	Route	Result	Evidence
docs: Read docs pass, developer llms.txt	none	done ✓	https://developer.helpscout.com/llms.txt 200 text/plain (40456 bytes, last-modified 18 Sep 2025): '# Help Scout Developer APIs' covering Inbox API 2.0, Docs API, Chat API, Webhooks, Apps SDK, Beacon. www.helpscout.com/llms.txt and docs.helpscout.com/llms.txt 404.
mcp: server/discover on the official MCP endpoint	mcp	done ✓	POST https://mcp.helpscout.net/mcp server/discover (2026-07-28 headers) -> 401 WWW-Authenticate: Bearer error="invalid_token", resource_metadata="https://mcp.helpscout.net/.well-known/oauth-protected-resource". initialize without auth -> same 401. Endpoint named in docs.helpscout.com/article/1779.
mcp auth metadata: PRM and AS metadata	none	done ✓	PRM 200 application/json {resource: https://mcp.helpscout.net/mcp, authorization_servers:[https://mcp.helpscout.net], scopes_supported:[helpscout]} at both path-suffixed and root. AS metadata 200: registration_endpoint (DCR), S256 PKCE, no client_id_metadata_document_supported, no device_authorization_endpoint. POST /oauth/register -> 201-style JSON with client_id (DCR works); /oauth/authorize -> 302 to /oauth/consent (needs a Help Scout login).
cards: AI catalog, agent card, MCP server card	none	done ✓	www.helpscout.com/.well-known/ai-catalog.json, agent-card.json, agent.json, mcp/server-card.json: all 404 HTML. https://mcp.helpscout.net/mcp/server-card 404 HTML.
aipref / markdown: Content-Usage and markdown negotiation	none	done ✓	www.helpscout.com/robots.txt: 'User-agent: * / Allow: / / Disallow: /ab/' - no Content-Usage or Content-signal line; homepage has no Content-Usage header. developer.helpscout.com/mailbox-api/ with Accept: text/markdown -> text/html; /mailbox-api.md -> 404.
api: Unauthenticated API probe	api	done ✓	GET https://api.helpscout.net/v2/conversations -> 401 application/json {"error_description":"The access token is missing","error":"invalid_request"}; POST /v2/oauth2/token bad client -> 400 invalid_client. docsapi.helpscout.net/v1/collections -> 401 Basic realm.
pay probes: 402/x402/MPP probes, registries	none	done ✓	pay_probe.json: no 402 challenges, no x402./mpp./agents. hosts, not on mpp.dev, Stripe Projects or Bazaar; pay_tx.json: nothing paid ('no 402 on the product's own endpoint'). /.well-known/ucp 404. Pricing page: Free plan (5 users, 1 Inbox, 1 Docs site), Standard $25, Plus $45, Pro $75 per user/mo; trial 'no credit card required'.
walk to last click: Open the checkout of the cheapest paid plan	browser	blocked	No account: sign-up stops at a required phone-number SMS verification, so the in-app billing page could not be opened. No public checkout link on the pricing page (all 'Try for Free' buttons go to secure.helpscout.net/members/register/5x/).
Sign up		skipped	No keyless route: every API call needs an OAuth token or Docs API key (401 without).
Sign up		skipped	No sign-up API or /auth.md (404) documented.
Sign up		skipped	No 402 rail (pay_probe.json, pay_tx.json).
Sign up: Sign up at secure.helpscout.net/members/register/58/ (Free plan)	browser	blocked	Form (First, Last, Work Email, Password) accepted the agent's inbox, no CAPTCHA shown; next page https://secure.helpscout.net/members/verify 'Step 1 of 3 Verify your account / Phone Number / Text my verification code' with no skip. Login afterwards: 'The email or password was incorrect.' No mail arrived.
Sign up		skipped	'Sign in with Google' (Google Identity Services g_id_signin) offered on sign-up and login; we has no Google account for this drive.
Sign up		skipped	No GitHub sign-in offered.
Sign up	mcp	blocked	DCR registration at mcp.helpscout.net/oauth/register worked; /oauth/authorize -> /oauth/consent needs a Help Scout login, which the phone wall prevents.
Verify	browser	blocked	Phone SMS verification required at /members/verify before the account exists; no verification email arrived (inbox empty after 30 s).
Key	api	blocked	Inbox API needs an OAuth2 app from My Apps (client_credentials) and Docs API needs a key from the profile: both inside the account, which the phone verification wall prevents.
First call	api	blocked	No credential: GET /v2/conversations -> 401 'The access token is missing'.
First action	api	blocked	No credential (phone wall at sign-up).
Cancel		skipped	Nothing started that renews; no account.
Delete	browser	blocked	The registration never finished: login with its email and password says 'The email or password was incorrect.' Whether Help Scout keeps the pending, phone-unverified registration is unknown; no route for us to remove it.
Receive and reply to customer conversations across email, chat, SMS, social	api	blocked	Not reached: no account (phone SMS verification required at sign-up). Docs: GET/POST /v2/conversations in developer llms.txt.
Create a new conversation on behalf of a customer	api	blocked	Not reached: no account (phone SMS verification required at sign-up). Docs: POST /v2/conversations in developer llms.txt.
Assign conversations to a teammate (manually or via round robin/load-balanced routing)	api	blocked	Not reached: no account (phone SMS verification required at sign-up). Docs: PUT /v2/conversations/{id} (assignTo) in developer llms.txt.
Change conversation status (open, pending, closed, spam) and state	api	blocked	Not reached: no account (phone SMS verification required at sign-up). Docs: PATCH /v2/conversations/{id} in developer llms.txt.
Let an AI agent autonomously resolve customer requests (AI Answers)	browser	blocked	Not reached: no account (phone SMS verification required at sign-up).
Generate AI-drafted replies for teammates to review and send (AI Drafts)	browser	blocked	Not reached: no account (phone SMS verification required at sign-up).
Summarize long conversation threads with AI	browser	blocked	Not reached: no account (phone SMS verification required at sign-up).
Publish a searchable, branded knowledge base with articles	api	blocked	Not reached: no account (phone SMS verification required at sign-up). Docs: GET/POST /v2/articles in developer llms.txt.
Embed a support widget (Beacon) on a website/app offering contact form, chat, and help articles	browser	blocked	Not reached: no account (phone SMS verification required at sign-up).
View and edit customer profiles with conversation history and custom properties	api	blocked	Not reached: no account (phone SMS verification required at sign-up). Docs: GET/PUT /v2/customers/{id} in developer llms.txt.
Expand, shorten, edit, or translate reply text with AI Assist	browser	blocked	Not reached: no account (phone SMS verification required at sign-up).
Surface trend and friction signals across conversations (Signal)	browser	blocked	Not reached: no account (phone SMS verification required at sign-up).
Build workflows that auto-assign, tag, or reply to conversations based on rules	browser	blocked	Not reached: no account (phone SMS verification required at sign-up).
Set Service Level Agreement (SLA) policies to track response targets	browser	blocked	Not reached: no account (phone SMS verification required at sign-up).
Send automated office-hours and auto-reply confirmations	browser	blocked	Not reached: no account (phone SMS verification required at sign-up).
Label conversations with tags	api	blocked	Not reached: no account (phone SMS verification required at sign-up). Docs: PUT /v2/conversations/{id}/tags in developer llms.txt.
Create and insert saved replies (canned responses)	browser	blocked	Not reached: no account (phone SMS verification required at sign-up).
Snooze a conversation until a chosen date/time	api	blocked	Not reached: no account (phone SMS verification required at sign-up). Docs: PUT /v2/conversations/{id} (snooze) in developer llms.txt.
Schedule an email reply to send at a later time (Send later)	browser	blocked	Not reached: no account (phone SMS verification required at sign-up).
Group conversations by Company and view company-level account activity	api	blocked	Not reached: no account (phone SMS verification required at sign-up). Docs: GET/POST /v2/customers/{id}/companies in developer llms.txt.
Define custom fields and custom properties to track structured data on conversations/customers	api	blocked	Not reached: no account (phone SMS verification required at sign-up). Docs: GET /v2/mailboxes/{id}/fields in developer llms.txt.
Collaborate with teammates via internal Views (filtered conversation lists)	browser	blocked	Not reached: no account (phone SMS verification required at sign-up).
Restrict access to internal Teams and Light user collaborators	api	blocked	Not reached: no account (phone SMS verification required at sign-up). Docs: GET/POST /v2/teams in developer llms.txt.
Send targeted in-app/website Messages and collect Surveys/CSAT/NPS ratings	browser	blocked	Not reached: no account (phone SMS verification required at sign-up).
View pre-built reports on volume, response time, and customer happiness	api	blocked	Not reached: no account (phone SMS verification required at sign-up). Docs: GET /v2/reports/* in developer llms.txt.
Build custom report views filtered by conversation type, inbox, tag, folder, or custom field	browser	blocked	Not reached: no account (phone SMS verification required at sign-up).
Export reporting data to CSV/Excel	browser	blocked	Not reached: no account (phone SMS verification required at sign-up).
Register webhooks and OAuth apps to receive event notifications	api	blocked	Not reached: no account (phone SMS verification required at sign-up). Docs: GET/POST /v2/webhooks in developer llms.txt.
Build custom apps/sidebar integrations that pull third-party data into the conversation sidebar	browser	blocked	Not reached: no account (phone SMS verification required at sign-up).
Enable additional communication channels: live chat, SMS, WhatsApp, Messenger, Instagram, phone/voice	browser	blocked	Not reached: no account (phone SMS verification required at sign-up).
Manage API access tokens and rate limits for integrations	api	blocked	Not reached: no account (phone SMS verification required at sign-up). Docs: OAuth2 token endpoint in developer llms.txt.
Connect third-party integrations (Salesforce, HubSpot, Jira, Linear, Aircall, 100+ apps marketplace)	browser	blocked	Not reached: no account (phone SMS verification required at sign-up).
Enforce security controls: SSO/SAML login, HIPAA compliance mode, IP restrictions	browser	blocked	Not reached: no account (phone SMS verification required at sign-up).
Set advanced role-based permissions at company, team, or user level	browser	blocked	Not reached: no account (phone SMS verification required at sign-up).
Customize Docs/Beacon branding and restrict Docs site visibility	browser	blocked	Not reached: no account (phone SMS verification required at sign-up).