bots.st/jointextkit-com
TextKit
Send and receive SMS; verify phones; manage numbers
2834 ms
answered our call
- State
- Answered
- Protocol
- MCP 2025-03-26
- Tools listed
- 152
- Answered
- 3 of the last 3 calls
How to reach it
- MCP, HTTP
https://mcp.jointextkit.com
What it can do
| Tool | What it says it does |
|---|---|
activate_automation | Turn an automation on, so tracked events start runs. With a live number it texts real people. With no `from`, a number approved for its `category` must exist or `issues` says what is missing; `sender` shows the numbers it will use. |
add_to_list | Add contacts to a list by contact_ids and/or phone_numbers (up to 1,000; numbers must already be contacts). |
assign_number_to_customer | Platforms: attribute a number (and its messages and usage) to one of your customers, or clear it with customer_id null. |
bulk_purchase_numbers | Buy several numbers in one area code at once (e.g. for a sender pool). Live numbers are billed monthly each. |
bulk_update_contacts | Add tags to, remove tags from, or delete many contacts by id. |
bulk_update_numbers | Act on many numbers at once: tag, untag, label, add to or remove from a pool, or release. Releasing cannot be undone. |
cancel_automation_run | Cancel a run in progress. |
cancel_batch | Cancel a batch. Messages already sent stay sent. |
cancel_scheduled_message | Cancel a scheduled message before it sends. |
check_verification | Check a verification code submitted by a user, by the phone or email it went to. Returns {verified, status, channel, charged}. Billed only when verified is true. |
clone_number_pool | Copy a sender pool under a new name. |
connect_integration | Connect a tool so its people sync in as contacts, in a list of their own, every 6 hours: Mixpanel (projectId, username, secret = a service account; sourceId = cohort id), Amplitude (apiKey, secretKey, sourceId), HubSpot (accessToken), Shopify (shopDomain, accessToken), Salesforce, or a webhook… |
create_api_key | Create an API key for an app you are building, to store as a secret in its environment (for example TEXTKIT_API_KEY) so the app can send texts itself. Same mode (test or live) as this connection; optional scopes limit it. The secret is returned once; the account owner is emailed. |
create_automation | Create a triggered text flow (as a draft): when trigger.event is tracked, run steps such as send_sms, wait, wait_for_event, and condition branches. Example: on cart_abandoned, wait 3600s, then if checkout_completed was not received send a reminder. A send_sms step with send_time… |
create_customer | Platforms sending for other businesses: create a customer to attribute numbers, messages and usage to. |
create_link | Make a tracked short link to copy into a text, ad, email or anywhere else: returns short_url. The same url again returns the same link. Suggest this whenever someone wants to know whether a link gets clicked or leads to sales. A link inside a text needs only shorten_links: true on the send. |
create_link_domain | Add a subdomain of the user's own (links.example.com) for short links. Returns two DNS records (CNAME and TXT) the user adds at their DNS host; then verify the domain. Optional: without one, tracked links use our domain. |
create_list | Create a list: a fixed group of contacts (Audience → Lists). Membership is set by hand, unlike a segment, which follows rules. |
create_number_pool | Create a sender pool from numbers you own. |
create_schedule | Send the same text to one number every day, week or month at a local time (e.g. a weekly reminder). Every occurrence runs the usual send checks. |
create_segment | Save an audience (a segment, a cohort): it appears in the console under Audience → Segments, and broadcasts can be sent to it. Everyone who can be texted: one rule, status is subscribed. Contacts matching all (or any) of up to 10 rules. Attributes: tags, contact fields, custom fields (field =… |
create_template | Save a message template. Merge tags: {{first_name}}, {{name}}, {{phone}}, {{field:<custom>}}, and per-recipient variables. |
create_topic | Create a subscription topic, so people can opt out of one kind of message (e.g. promotions) and keep others. |
create_webhook | Send events (message.received, message.delivered, message.opted_out, ...) to a URL: your app, a CRM, an automation tool. Returns the signing secret once. |
delete_automation | Delete an automation. |
delete_contact | Delete a contact. Messages, consent records, and topic preferences for the number are kept. |
delete_customer | Delete a customer. |
delete_link_domain | Remove a branded link domain. Every short link already sent on it stops working. |
delete_list | Delete a list (its contacts stay). |
delete_message | Delete a finished message (delivered, failed or received) and every copy of its text, for a privacy request. Opt-out records and billing are kept. Cannot be undone. |
delete_number_pool | Delete a sender pool. Its numbers are kept. |
delete_schedule | Delete a recurring schedule. |
delete_segment | Delete a segment. Contacts are not touched. |
delete_template | Delete a template. |
delete_topic | Delete a topic you created (built-in topics stay). |
delete_webhook | Delete a webhook endpoint. |
disconnect_integration | Disconnect a tool: its credentials and its list are deleted; the contacts stay with their consent. |
export_consent | The suppression list, or the full consent ledger with opt-in proof, as CSV text. |
export_csv | Export as CSV text for analysis: messages, deliveries, events, opt_outs, webhook_deliveries, usage, usage_monthly, audit_log or credit_history. At most 50,000 rows; narrow the date range with from and to. |
export_numbers | Your numbers as CSV text. |
fallback_verification | The text did not arrive: email a new code for the same pending verification (one id, one charge). The emailed code replaces the texted one and is checked by the email address, which it proves (not the phone). Once per verification. |
forget_identity | Privacy erasure: forget the phone number linked to a user_id, so its tracked events stop reaching automations. |
get_automation | Retrieve an automation with its trigger and steps. |
get_automation_run | Retrieve one run with its step-by-step timeline. |
get_balance | Prepaid credit balance and auto-recharge setting. |
get_batch | Retrieve a batch with its progress counts. |
get_batch_results | Results of a batch: delivered, failed, pending, replies, opt-outs (stops), spend, and failures grouped by reason. |
get_consent | Whether a number is opted in or out, per registration, with its full consent history and proof. |
get_contact | Retrieve a contact. |
get_contact_topics | A contact's subscription to each topic. |
get_customer | Retrieve a customer. |
get_customer_usage | A customer's messages, verifications and spend for a period. |
get_deliverability | Delivery rates by day, destination carrier, or sending number. |
get_integration | One connected tool and its last sync. |
get_integration_events | Confirm the events behind automations: for a Mixpanel integration, each mapped event with its Mixpanel source events and their 7-day volume, how many reached TextKit and when the last did, and which automations start on, wait for or check it. `missing` names events automations rely on that nothing… |
get_link_domain | One short-link domain, with the DNS records it needs. |
get_list | Retrieve a list and its contact count. |
get_message | Retrieve a message by its msg_... id, with its delivery timeline. |
get_number | Retrieve one of your numbers: status, sender registration, tags, pools, customer. |
get_number_pool | Retrieve a sender pool and its numbers. |
And 92 more tools.
In its maker's words
SMS for developers: send and receive texts, verify phones, and buy US and Canada numbers.
- Website
- jointextkit.com/docs/mcp?ref=mcp-registry
- Source
- github.com/textkithq/textkit-mcp
- Publisher
- jointextkit.com
- Listed from
- the official MCP Registry as
com.jointextkit/textkit - Version
- 1.0.2, updated 30 Oct 2026
- Kinds of work
- Messaging and support, Security and trust, Finance and markets
The domain it lives on
- jointextkit.com
- registered 27 Oct 2026 (1 months ago), at Squarespace Domains LLC, its home page is a working site
From our own crawl of domain names: registry records and the home page as our crawler last saw it.
Every call we made
| When | What happened | Time |
|---|---|---|
| Answered | 2834 ms | |
| Answered | 2736 ms | |
| Answered | 1160 ms |
Next door
- Inbin: email for AI agentsDisposable inboxes for agent email verification
- AgentLairEmail delegation via inbox and vault
- Mailrith Email MarketingManage email subscribers, broadcasts, and automations with r
- faxforagents-mcpSend and receive faxes with approval
- AnyHookManage webhook inboxes for agent events
Is this your bot? Claim its address to add a verified badge and keep the listing current.