Assistable

Search Assistable's registered MCP tools by the task the user wants to do. Returns up to 5 exact tool definitions with JSON input schemas and annotations. Use this first when you need to choose a tool; the result is not authorization to call it.

List assistants in a subaccount (excludes archived by default). Note: voice_settings and platform_tools are returned only by assistants_get, not in the list.

Fetch an assistant's full configuration by ID. The response includes voice_settings (greeting mode, opening messages, voicemail) and platform_tools (attached platform-catalog tool names).

Create an assistant. Required: subAccountId, name. Optional config blocks (llmConfig, voiceConfig, chatConfig) mirror the dashboard create dialog. voice_settings configures call greeting mode, opening messages, and voicemail behavior; platform_tools attaches platform-catalog tools (declarative full-replace — see the field description).

Patch an assistant. Only supplied fields change; nested config blocks are upserted. voice_settings updates call greeting mode, opening messages, and voicemail behavior; platform_tools declaratively replaces the attached platform-catalog tools (an empty array detaches all — see the field description).

Archive (soft-delete) an assistant.

List tools visible to a subaccount. Pass includePrebuilt=false for only custom tools.

Fetch a tool's full configuration.

Create a custom tool (toolType=CUSTOM). Name must match /^[a-zA-Z0-9_-]+$/ and be unique in the subaccount.

Patch a custom tool. Supplying parameters/headers replaces those rows; omit to leave them.

Soft-delete a custom tool.

List contacts in a subaccount. meta.total is the number of matching contacts, so use it to answer how many contacts there are.

Fetch a contact by ID.

List conversations in a subaccount.

List appointments in a subaccount within an optional date range.

Fetch a call (status, recording, transcript) by ID.

Only when you have no Assistable API key: start signing in. Returns verification_uri_complete and user_code; send the person that link (or the code) so they can sign in to Assistable, pick the account and approve. Then call assistable_connect_finish with device_code every interval seconds until it returns api_key. If they have no account, the link lets them sign up first.

Check an assistable_connect sign-in. error.code authorization_pending means the person has not approved yet: wait interval seconds and call again. On approval it returns api_key once: use it as the Authorization: Bearer header for this MCP server (mcp_url) and keep it safe; it cannot be shown again.

Only when the person has no Assistable account (assistable_connect is for people who have one): start one with their email and name, and area_code or city/state for their local number. Emails them a 6-digit code; ask them for it, then call assistable_signup_finish. If they say the email told them they already have an account, use assistable_connect instead.

Finish assistable_signup with signup_id, the code the person read to you, and a strong password you generate and keep in your vault (it is their dashboard login). Returns api_key once: send it as the Authorization: Bearer header to this MCP server. Calls and texts answer card_required until the person opens card_url, which saves their card, adds starting credit and buys their local number; send them that link.