Cradley for AI assistants
Your care search,
connected to your assistant.
The Model Context Protocol (MCP) lets your AI assistant work with Cradley. Find pre- and postnatal care, organize your favorites, and stay in touch with providers — with you in control.
MCP server URL
https://www.searchcradley.com/api/mcpMCP 2026-07-28 · Streamable HTTP · OAuth for your account
Connect your assistant
Use an assistant or client that supports remote MCP servers over Streamable HTTP. Account features also require OAuth with dynamic client registration.
- Add a remote MCP server. In your client’s connector settings, name it Cradley and paste the server URL above.
- Connect your account. When prompted, sign in with your Cradley parent account and review the permissions. Public provider search works without signing in.
- Start with a search. Ask your assistant to find care. Favorites, care teams, and messages become available according to the permissions you approve.
Try asking
- “Find postpartum doulas near ZIP code 22201.”
- “Show me my saved providers.”
- “Add this provider to my care team.”
Adding someone to your care team does not book an appointment. Confirm availability, prices, and insurance coverage directly with the provider.
Available tools
Ten tools cover provider discovery and your parent account. Tools marked Public do not require account access.
search_providersPublic- Find care providers by care type, ZIP code, language, price, insurance, and more.
get_providerPublic- Read a provider’s public profile, services, pricing, FAQs, and reviews.
list_favoritesfavorites:read- See your saved providers.
add_favoritefavorites:write- Save a provider to your favorites.
remove_favoritefavorites:write- Remove a saved provider.
get_care_teamcare-team:read- View your care team.
update_care_teamcare-team:write- Add or remove a provider in your care team.
list_conversationsmessages:read- List your conversations with providers.
get_conversationmessages:read- Read messages in one of your conversations, newest first.
send_messagemessages:send- Send a message to one provider when you explicitly ask your assistant to send it.
Appointment booking, payments, meal calendars, and visitor scheduling are not available through MCP. Care providers use a separate server, described below.
Permissions & privacy
You choose which permissions to grant during connection. Reading favorites or your care team does not grant permission to change them. Reading messages and sending messages are separate permissions, too.
Your assistant should send a message only when you explicitly ask it to contact that provider with that message. Sending may notify the provider by email.
You can disconnect an app at any time in Connected apps. Disconnecting blocks its access immediately. Signing out of the session used to connect, or that session expiring, also blocks the connection.
Manage connected appsYou’ll need to sign in to manage connections. Read our privacy policy for more about how Cradley handles your information.
For providers
If you list your practice on Cradley, connect your assistant to the provider server to keep your profile current and keep up with families who message you. Sign in with the provider account you used to set up your profile.
Provider MCP server URL
https://www.searchcradley.com/api/mcp/providerYour assistant asks for all four provider permissions when you connect: viewing and editing your profile, FAQs, and endorsements, and reading and replying to your conversations. Every provider tool needs your account; none are public.
get_profileprovider-profile:read- Read your profile as families see it, plus your ZIP, service radius, and role.
update_profileprovider-profile:write- Change your tagline, About text, prices, insurance, languages, and other profile details.
list_faqsprovider-profile:read- List the FAQs on your profile.
save_faqprovider-profile:write- Add an FAQ or rewrite an existing one.
delete_faqprovider-profile:write- Remove an FAQ from your profile.
list_reviewsprovider-profile:read- Read reviews families left, with your rating summary.
list_endorsementsprovider-profile:read- See endorsements other providers wrote for you, including ones waiting for your approval.
respond_to_endorsementprovider-profile:write- Approve an endorsement to show it on your profile, or decline it.
pin_endorsementprovider-profile:write- Feature up to two approved endorsements at the top of your profile, or unpin one.
create_endorsement_requestprovider-profile:write- Get a link to send a colleague so they can write you an endorsement.
list_conversationsprovider-messages:read- List conversations families started with you, with unread counts.
get_conversationprovider-messages:read- Read messages in one conversation, newest first.
send_replyprovider-messages:send- Reply to a family in an existing conversation once you approve the exact text.
Try asking
- “Do I have any unread messages from families?”
- “Draft a reply to the newest one, and show it to me before sending.”
- “Add an FAQ about whether I offer virtual visits.”
- “Do I have any endorsements waiting for approval?”
Profile, FAQ, and endorsement changes are visible to families as soon as they are saved, so your assistant should confirm the exact change with you first. Replies may notify the family by email. Only practice admins can change profile details; any team member can manage FAQs, endorsements, and replies.
For developers
Transport & discovery
Cradley supports MCP protocol revision 2026-07-28 using TypeScript SDK v2. Requests are stateless: no initialization handshake or MCP session ID is needed. Older clients using the 2025-11-25 protocol remain supported through the same endpoint with their existing initialization flow.
Send requests with POST. Modern clients include the protocol version and client capabilities in each request’s _meta, with matching MCP-Protocol-Version and Mcp-Method headers. Tool calls also include Mcp-Name. SDK v2 clients can opt in with versionNegotiation: { mode: "auto" }.
Use server/discover for protocol capabilities and tools/list for current input schemas. GET and DELETE return 405. This endpoint returns JSON tool results and does not offer persistent subscription streams.
OAuth
Use the authorization code flow with PKCE (S256). Dynamic public-client registration is supported; Client ID Metadata Documents are not currently supported. Set the resource parameter on authorization and token requests to the exact MCP server URL for your environment.
Request only the scopes your integration needs. A request without scopes asks for every permission of the server in its resource parameter, and the consent screen lists each one. Add offline_access for rotating refresh tokens. Without it, the connection ends when the access token expires.
Account tools require a bearer access token; browser cookies are not accepted. Access tokens last five minutes and remain subject to live consent and session checks. Native and server clients can connect without an Origin header; cross-origin browser clients require an allowed origin.
Pagination & message retries
Search, favorites, conversations, and conversation messages accept limit (1–50, default 20) and offset (0–10,000, default 0). Conversation messages are newest first. The care-team tool returns the whole team.
Sending a message requires a provider ID, message content (1–4,000 characters), and a UUID requestId. For a timeout or uncertain result, retry with the same request ID, recipient, and content. A new request ID means a new message. Sending is limited to 20 new messages per parent per hour.
The provider server works the same way. It requires a bearer token on every request, including discovery, and its 401 challenge lists all four provider scopes. Parent and provider permissions cannot be granted together; connect each server separately. Replies take a conversation ID, content, and a UUID requestId, and are limited to 30 per provider per hour.
Staging
https://staging.searchcradley.com/api/mcphttps://staging.searchcradley.com/api/mcp/providerUse the staging origin for discovery, OAuth, and the resource parameter when testing. Keep staging and production connections separate.
Troubleshooting
The server URL shows “Method not allowed” in my browser.
That is expected for a browser GET request. Paste the URL into your MCP client’s remote server settings to connect.
Authentication fails or I get a 401.
Use the full production URL with www. Reconnect and sign in with a parent account, or with your provider account for the provider server. An expired session, disconnected app, or invalid token will block access, even to public tools when an invalid token is supplied.
A tool returns 403 or insufficient scope.
Check that the client requested the tool’s permission during registration and authorization, then reconnect to review and approve it. Read access does not include write or send access.
My client cannot complete OAuth.
Confirm it supports Streamable HTTP, authorization code with PKCE, and dynamic client registration. Use the same environment throughout discovery, authorization, and token exchange.
Still stuck? Contact Cradley support with your client name and the error message. Leave out access tokens, authorization codes, and private message content.