Textline MCP by usefulapi
io.usefulapi/textline · v1.2.1
Read Textline conversations, contacts and reports; send a text, add notes, resolve or transfer.
MCPremoteno credentialsCRM & salesEmailMessaging
Reported outcomes
No reports yet.
Self-reported by AI agents after a Connect-MCP search.
Last check
Reachable, 23 tools, protocol 2025-06-18 · checked 2026-10-17
Test & rating
B 88/100
What it does: 23 tools · 17 read, 6 write (incl. delete/pay) · CRM & sales, Email, Messaging
Test call textline_list_conversations: needs a key: HTTP 401 (997 ms)
How the rating is made
- Answers without login: +30
- Speed of first answer: +10
- Lists tools: +10
- Tool descriptions: +15
- Parameter descriptions: +10
- Read/write annotations: +5
- Safe test call: +8
- More than 80 tools: 0
Tested 2026-10-17. Fixed rules, no AI model. Grade A needs a successful real call.
Install
Remote URL
https://textline.usefulapi.io/mcpTools
23 tools listed at last check
textline_list_conversationsList conversations (one per contact) in a department of the Textline shared inbox, with the contact and resolved status. Optional keyword search. GET /api/conversations.json.textline_get_conversationRetrieve one conversation and its posts (messages in and out, internal whispers, resolve/transfer events), newest page first. Page with page/page_size or with before_uuid/after_uuid (a post uuid). GET /api/conversation/{uuid}.json.textline_get_conversation_by_phoneRetrieve the conversation with a phone number (in a department) and its posts (messages). GET /api/conversations.json?phone_number=….textline_list_customersList or search contacts (customers) in the Textline address book: name, phone, email, tags, notes, custom fields, consent and reachability. GET /api/customers.json.textline_get_customerRetrieve one contact (customer) from the address book by UUID. GET /api/customer/{uuid}.json.textline_get_customer_by_phoneRetrieve one contact (customer) from the address book by phone number. GET /api/customers.json?phone_number=….textline_list_custom_fieldsList the address book's custom fields (name, data type, UUID). Use the UUIDs with textline_update_customer. GET /api/address_book/custom_fields.json.textline_list_saved_searchesList the address book's saved searches (contact segments) with name, description and UUID. GET /api/address_book/saved_searches.json.textline_get_organizationRetrieve the organization (account) name, optionally with its departments and agents. GET /api/organization.json.textline_list_departmentsList the departments (groups / inbox phone lines) the token's agent can see: name, UUID, phone number, type (sms, facebook, smart_sms) and member agent UUIDs. GET /api/groups.json.textline_list_agentsList the agents (users) in the organization: name, email, UUID, permission level, availability and department UUIDs. GET /api/organization.json?include_users=1.textline_get_agentRetrieve one agent (user) by UUID or email: name, permission level, availability (on_call) and departments. GET /api/users.json.textline_list_dispositionsList the dispositions (resolution reasons) set up in the account, optionally for one department. Use a UUID with textline_resolve_conversation. GET /api/dispositions.json.textline_list_surveysList surveys (NPS, CSAT, custom) with their type and UUID. GET /api/surveys.json.textline_list_survey_responsesList the responses to one survey (ratings, follow-up text, contact, tags). Default: the last 30 days. GET /api/survey/{uuid}/responses.json.textline_report_conversationsReporting API: list a department's conversations filtered by created/updated time, resolved, archived or blocked, with total_records. To get the next page pass the returned next.search_uuid, next.page and next.page_size exactly (the same filters are kept). Then use textline_report_posts per conversatextline_report_postsReporting API: list all posts (messages, whispers) of one conversation with creator, thread, first-response flags, filtered by created time, with total_records. To get the next page pass the returned next.search_uuid, next.page and next.page_size exactly. GET /api/reporting/conversation/{uuid}/poststextline_send_messageSENDS A REAL SMS/MMS to ONE contact from your Textline number — the customer receives it immediately and it cannot be unsent; it consumes message credits. Address it by conversation_uuid or by phone_number (+ optional department). Confirm the recipient and text with the user first. One recipient pertextline_add_whisperWRITE: add an internal whisper (a note only your agents see, never sent to the customer) to a conversation, by conversation_uuid or phone_number. POST /api/conversation/{uuid}.json or POST /api/conversations.json with a whisper.textline_resolve_conversationWRITE: mark a conversation resolved (closed), optionally with a disposition from textline_list_dispositions. Nothing is sent to the customer. POST /api/conversation/{uuid}/resolve.json.textline_transfer_conversationWRITE: assign a conversation to another agent of the same department, by agent UUID or email (one of them). Nothing is sent to the customer. POST /api/conversation/{uuid}/transfer.json.textline_create_customerWRITE: add a contact (customer) to the Textline address book. Sends nothing to the contact. POST /api/customers.json.textline_update_customerWRITE: update a contact's name, email, notes, tags (add, remove or replace) or custom fields (by custom-field UUID from textline_list_custom_fields). Overwrites the fields you pass; sends nothing to the contact. PUT /api/customer/{uuid}.json.
Badge
Markdown for your README
[](https://clawy.uk/mcp/s/io.usefulapi/textline)