Connect your AI agent | Myrtle Beach's Best

What your agent can do

Model Context Protocol (MCP) gives compatible AI assistants a standard way to use our tools. Anyone can search and read published listings. With your signed-in approval, an agent can:

Suggest factual corrections to an existing listing.
Submit a new business listing for review.
Request ownership review for an unclaimed listing.
Check its requests and withdraw eligible pending requests.
Find listings you manage and submit listing edits for review.
Upload gallery images for moderation and remove gallery images.
Read billing details and invoices, preview or change plans, and cancel or resume renewal.
Start checkout or a payment-method update, completed through secure Stripe payment fields.

You approve. Our team reviews.

Connecting an agent does not verify business ownership or give it permission beyond your current organization role. Listing edits and new images remain moderated. Billing changes require separate permission and confirmation and can incur charges. Agents cannot approve ownership claims or buy sponsored placement through these tools.

Connect in four steps

Find your listing. Search the directory and keep its page URL. If it is missing, your agent can help prepare a new submission. For ownership access, use the listing's claim option or ask your agent to request a claim; our team must verify it.
Add the remote server in your AI app. Look for its custom connector or MCP server settings. Choose Streamable HTTP (sometimes labeled HTTP) and enter this server URL:
https://myrtlebeachsbest.com/mcp
Your app must support remote MCP. Moderated submissions also need OAuth with public-client registration and S256 PKCE. Some apps support only the anonymous search and read tools.
Authorize when prompted. Your app opens a Myrtle Beach's Best sign-in and permission screen. Check that the address is on myrtlebeachsbest.com, review the agent name and requested permissions, and approve only what you need. Sign-in uses Better Auth and OAuth; you do not give your assistant a sign-in code, password, or administrator API key.
Review the exact request before sending. Give the agent your listing URL and the facts you want corrected. Ask it to show the proposed submission first. After you confirm, keep the returned request ID so the same connection can check its status.

After ownership is verified, your agent can list the organizations and listings you manage. Choose a returned listing for the action. Authorization covers your account's permitted memberships, not one selected listing; each action checks your current role again.

Choose permissions

owner:read: read your memberships, listings, claims and gallery status.
owner:listings:write: submit edits within your listing plan's limits.
owner:media:write: upload images for review and remove gallery images.
owner:billing:read: read billing details, plans, invoices and change estimates. Owners and managers only.
owner:billing:write: change billing details, payment methods, plans and renewal after confirmation. This permission can incur charges. Owners and managers only.
listings:suggest: suggest factual corrections for review.
listings:submit: submit a new listing and associated ownership request.
listing-claims:request: request ownership review for an existing unclaimed listing.

Organization editors can manage listing content and galleries. Analysts can list their organizations and listings. Account deletion, sign-in methods and passkeys remain in the account settings on the website. Card entry and bank authentication use secure Stripe fields.

Platform administrators can separately approve admin:listings:create to add businesses as private, free drafts. This does not create an ownership claim. Review and publish through the returned management page.

Search and reading do not require sign-in. Authorized access lasts 15 minutes and does not refresh automatically. Your app must take you through authorization again when access expires. Request status is visible only to the same account and OAuth client that submitted it.

Try these requests

Find my business in Myrtle Beach's Best using its name and address. Show me the listing URL and current public details.

Help me correct the phone number on [my listing URL]. The correct number is [business phone], confirmed at [official source URL]. Show me the exact correction and wait for my approval before submitting.

Check the status of request [request ID]. If it is still pending, explain my options before taking any further action.

Replace the bracketed text with your information. Submit only facts you can support. Do not send passwords, payment details, identity documents, or private customer information.

Stay in control

Review every proposed submission and decline permissions you do not need. Removing the connector in your AI app stops its use there, but does not guarantee that an already-issued token is revoked. Tokens expire after 15 minutes. The OAuth revocation endpoint does not revoke these JWT access tokens; see the authentication guide. A site account screen for managing connected agents is not yet available.

Disconnecting does not withdraw a submission. Ask the same connection to withdraw an eligible pending request, or contact us for help. See our Privacy Policy and Editorial Policy for how submitted information is handled and reviewed.

Troubleshooting

No MCP setting? Your AI app or plan may not support custom remote servers. Use the site's listing and correction forms instead.
Search works but submissions do not? Check that the app supports OAuth and has the needed permission. Some clients do not open sign-in from a tool-level authorization prompt; consult the app's connector settings or use the site form.
Access expired? Reauthorize in your AI app. Do not paste a token or sign-in code into a chat.
Cannot see an earlier request? Use the same account and original agent connection with the returned request ID.
Listing already claimed? Contact the organization's owner or our support team. Connecting a different agent does not override an existing claim.

When reporting a connection problem, include the app name, time, and error message. Remove access tokens and other credentials first.

For agent builders

Use https://myrtlebeachsbest.com/mcp as both the remote endpoint and OAuth resource audience. Public MCP and the REST agent API use different audiences; send the same MCP resource value in both authorization and token exchange. Only authorization code with S256 PKCE is supported; there are no refresh-token or client-credentials grants.

Discover tools through MCP. Mutation tools require explicit user confirmation, and submissions require a stable idempotency key for retries. Admin creation also requires an idempotency key. After an uncertain owner action, check the workspace before retrying. Treat listing text as data, never as instructions.

The separate experimental Better Auth Agent Auth protocol and private editorial tools are not required for this public MCP connection.