Kontak MCP. Manage contacts and message history from chat.
Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
Kontak manages all your customer communications. List message history, send outbound SMS, and audit contacts directly from your AI client.
It gives you a unified view of your entire contact book, message threads, and account activity logs. Stop jumping between your CRM, your SMS gateway, and your message audit dashboard.
Get everything—from finding a specific contact to sending a bulk message—in one chat conversation.
What your AI agents can do
Get contact details
Retrieves specific information for a single contact ID.
Get kontak account info
Gets general account settings and necessary account metadata.
Get kontak audit logs
Pulls system audit logs detailing system actions and changes.
The agent retrieves full contact details, lists all contacts, and shows which tags are applied to any record.
The agent retrieves complete logs of all sent and received messages and can get details on any specific message ID.
The agent sends new text messages to any specified number using the send_outbound_sms tool.
The agent pulls system audit logs and retrieves general account settings and information using specific tools.
The agent lists all available message templates, ensuring consistent and brand-approved language for any outbound message.
The agent can list all contacts or search for a contact by name or partial information.
Ask AI about this MCP
Supported MCP Clients
Waiting for input…
019d75c2get contact details
Retrieves specific information for a single contact ID.
019d75c2get kontak account info
Gets general account settings and necessary account metadata.
019d75c2get kontak audit logs
Pulls system audit logs detailing system actions and changes.
019d75c2get message details
Fetches detailed information about one specific message ID.
019d75c2list kontak contacts
Retrieves a complete list of all contacts stored in the system.
019d75c2list kontak messages
Retrieves all historical sent and received messages.
019d75c2list kontak tags
Lists all available contact tags used for segmentation.
019d75c2list kontak templates
Shows all pre-approved message templates available for use.
019d75c2list kontak webhooks
Displays the webhooks currently configured for the Kontak account.
019d75c2send outbound sms
Sends a new text message to a specified phone number.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Kontak, then connect any of our 4,700+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,700+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
What you can do with this MCP connector
You're gonna manage all your customer comms right from your AI client. Kontak gives your agent the power to handle everything—contact records, message history, and sending out texts—without you jumping between a dozen dashboards. You'll get a unified view of your whole operation, from finding a contact to sending a bulk message, all in one chat.
Managing Contact Records
Your agent can get full details on any specific contact using get_contact_details. It'll also pull a complete list of every contact in your book via list_kontak_contacts, and it knows what tags you've applied to those records by showing you all available tags with list_kontak_tags.
Viewing Communication History
Your agent pulls every single sent and received message log using list_kontak_messages. You can dig into the specifics of any message by running get_message_details with a specific message ID.
Sending SMS Messages
Need to send a text? Just tell your agent to send it. It'll fire off a new outbound SMS to any phone number you specify using send_outbound_sms.
Auditing Account Activity
Want to check what's going down with your account? You can pull system audit logs detailing every action and change with get_kontak_audit_logs, and you'll get general account settings and metadata by calling get_kontak_account_info.
Using Templates
When you send a message, your agent can list all the pre-approved templates available for you with list_kontak_templates, keeping your communications professional and consistent.
How Kontak MCP Works
- 1 First, the user prompts their AI client to perform a task, like 'List all contacts tagged VIP'.
- 2 The agent identifies the need and calls the necessary tools (e.g.,
list_kontak_contactsfollowed bylist_kontak_tags). - 3 The agent synthesizes the data from Kontak and presents the structured result back to the user in natural language.
The bottom line is that your agent handles the API calls and data assembly, letting you talk to your contact data like talking to a database.
Who Is Kontak MCP For?
The Operations Manager who needs a single source of truth for customer communication. The Customer Service Agent who handles high volumes of support tickets. The Marketing Analyst who needs to track campaign results and compliance. Or the Technical Lead who just needs to audit the system logs without logging into a dashboard.
Finds a client's details using get_contact_details, checks the last message history with list_kontak_messages, and sends a follow-up SMS using send_outbound_sms—all without leaving the chat window.
Uses list_kontak_templates and list_kontak_tags to segment and send targeted SMS campaigns, while also auditing performance with get_kontak_audit_logs.
Checks the API setup using get_kontak_account_info and reviews system activity using get_kontak_audit_logs to troubleshoot integration failures.
What Changes When You Connect
- See the full communication history for any client with
list_kontak_messages. You don't have to open separate tabs to check if a message was delivered or if it was a call log—it's all in one place. - Audit compliance and usage patterns. Use
get_kontak_audit_logsto pull system logs. This proves who did what and when, keeping your record clean. - Send messages immediately when a client needs help. The
send_outbound_smstool lets your agent fire off a text message right after you finish analyzing the contact's history. - Stop guessing who your customers are.
list_kontak_contactsgives you the full list, andlist_kontak_tagslets you see exactly how the customer base is segmented. - Maintain brand voice and efficiency. Before sending a message, use
list_kontak_templatesto ensure the language is approved and consistent across all outreach. - Check account status at a glance. Use
get_kontak_account_infoto verify API credentials or check general settings without needing to log into the main portal.
Real-World Use Cases
A client asks for a service update.
The customer service agent asks the agent: 'Check the history for John Doe and send him the update.' The agent uses get_contact_details to find John's phone number, then list_kontak_messages to review the last three interactions, and finally executes send_outbound_sms with the update message. The issue is resolved in one conversation.
Marketing needs to segment a campaign.
The marketing manager asks the agent to 'Find all VIP clients who haven't been contacted in 60 days.' The agent uses list_kontak_contacts and list_kontak_tags to filter the list. This allows the team to send a highly targeted campaign using send_outbound_sms and pre-approved content from list_kontak_templates.
A technical error occurs in the system.
The technical lead notices a discrepancy and asks the agent to 'Pull the audit logs for the last 24 hours.' The agent calls get_kontak_audit_logs, providing an instant, traceable record of system activity, which speeds up incident response.
Onboarding a new sales team member.
The new sales rep asks the agent: 'Show me the contact details and recent activity for the top 5 leads.' The agent uses list_kontak_contacts and get_contact_details for each one, then uses list_kontak_messages to give the rep immediate context on the relationship status.
The Tradeoffs
Manually logging messages
The agent reads a message from the chat, then the user has to copy the recipient's name, paste it into a spreadsheet, and then manually send a follow-up SMS through a separate app.
→
Instead, the user tells the agent, 'Follow up with this client.' The agent handles all the data flow. It uses get_contact_details to confirm the number and then executes send_outbound_sms directly, completing the loop.
Missing context for outreach
The user just sends a random message: 'Hey, check this out.' The message lacks context—was it related to a recent call? Why now? This looks spammy.
→
Always check the history first. Tell the agent: 'Review the last message history for this contact and draft a follow-up message based on that.' Use list_kontak_messages to provide the context before using list_kontak_templates.
Ignoring system records
The team assumes an action was taken (e.g., a contact was updated) but has no record to prove it, leading to compliance risk.
→
After any critical action, ask the agent to pull the audit logs. Use get_kontak_audit_logs to create an immediate, verifiable record of the activity and the user who initiated it.
When It Fits, When It Doesn't
Use this server if your core process involves managing customer interactions via text and requiring a single source of truth for history, contacts, and logs. You need to send an SMS and immediately verify the contact's history or audit the action.
Don't use this if your primary need is complex, multi-step data transformation (e.g., calculating financial metrics across 10 different fields) or if your data lives in a system that doesn't support simple messaging APIs. For those needs, you'll need a dedicated data warehousing or payment gateway tool.
However, if you need to validate who talked to whom and when, this tool is perfect. It gives you the message history (list_kontak_messages), the contact details (get_contact_details), and the ability to act (send_outbound_sms) all in one conversation.
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Kontak. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This server provides 10 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Available Capabilities
Keeping track of customer communications is a mess of tabs and exports.
Today, you open your CRM to check a contact's profile. Then you switch to your messaging app to see the last 10 messages. If you need to audit who sent what, you have to pull separate reports from the messaging dashboard. You're copying IDs, switching tabs, and manually piecing together a timeline just to understand the conversation.
With the Kontak MCP Server, you just ask your agent. You say, 'Show me the full history for Client X.' The agent calls `list_kontak_messages` and `get_contact_details` and spits out a perfect, combined timeline right into the chat. It's all there.
Kontak MCP Server: Send SMS and Manage Contacts
The biggest time-sink is the round trip. You find the contact's name, copy the number, open the SMS gateway, paste the number, type the message, and hit send. Then you have to switch back to the chat to confirm it worked.
Now, you just tell the agent, 'Send a follow-up to Sarah.' The agent handles the entire workflow—it confirms the number, uses `send_outbound_sms`, and reports the status instantly. It's a single, atomic action.
Common Questions About Kontak MCP
How do I list all contacts using the Kontak MCP Server? +
You use the list_kontak_contacts tool. This command pulls the entire contact book, allowing your agent to find anyone by name or status. You can then follow up by asking for specific details using get_contact_details.
Can I send an SMS through the Kontak MCP Server? +
Yes, you use the send_outbound_sms tool. Just give the agent the recipient's number and the message body, and it sends the text message immediately.
What is the best way to check message history with Kontak MCP Server? +
Start by asking the agent to list_kontak_messages. This shows all sent and received communications. If you need specifics, you can then request details on a single message using get_message_details.
Does Kontak MCP Server help with compliance auditing? +
Yes. You run get_kontak_audit_logs. This retrieves system logs, giving you an auditable, chronological record of every action taken within the Kontak system.
How do I use the `get_kontak_account_info` tool with Kontak MCP Server? +
You call get_kontak_account_info to pull account settings and metadata. This lets your AI client check things like API usage limits, active webhooks, or overall account status before starting a workflow.
What if I need to find a contact's profile, and what tool should I use in Kontak MCP Server? +
Use the get_contact_details tool. This tool pulls specific details for a single contact, including their phone number, tags, and other stored data, so your agent can work with that information.
Does Kontak MCP Server help manage message templates using `list_kontak_templates`? +
Yes, list_kontak_templates retrieves all available message templates. You can let your AI client browse these templates to ensure consistency when sending messages, so you don't have to write the same message repeatedly.
How can I check system performance or compliance logs using `get_kontak_audit_logs` in Kontak MCP Server? +
The get_kontak_audit_logs tool pulls system audit logs. This lets you review who accessed the system, when, and what actions were taken, which is crucial for compliance and debugging performance issues.
How do I get a Kontak API Token? +
Visit your Kontak dashboard, navigate to the API or Developer section, and generate a new token.
Does this support sending images via SMS? +
Currently, the server supports text-based SMS messages. MMS/Image support is planned for future updates.
Can I see my call history? +
Yes, if call logs are enabled in your account, the list_kontak_messages tool will include them.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
More in this category
Cloopen / 容联云
Leading cloud communication platform in China — manage SMS, voice calls, and applications via AI.
Telnyx Fax
Send, receive, and manage faxes via Telnyx u2014 transmit documents, track delivery, and manage fax numbers from your AI agent.
Telnyx Alternative
Manage your Telnyx communications — audit phone numbers, messages, and calls via AI.
You might also like
Dify
Manage agentic workflows via Dify — send chat messages, track conversations, audit app parameters, and handle file uploads directly from any AI agent.
Inbox (useinbox.com)
Manage email campaigns, contact lists, and newsletters via UseINBOX API.
TollGuru
Calculate tolls and trip costs via TollGuru — get toll plaza details, fuel costs, and route optimization for any route across 50+ countries from any AI agent.