Supercharge your AI with MiiTel Alternative. Log records, manage exports, centralize voice intel.

Q: How do I check if my CSV export job started with createqueue?

You use listqueues to see all your current and past jobs. The status will show 'WAITING' or 'PROCESSING,' confirming the queue was successfully created.

Q: Can I import data from a different phone system using createcallrecord?

Yes, createcallrecord is designed for this. You send it webhook-formatted data that simulates an incoming call into your MiiTel account.

Claude

ChatGPT

Cursor

Gemini

Windsurf

VS Code

JetBrains

Vercel

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

Connect to your AI in seconds.

MiiTel Alternative MCP Server automates call and meeting logging by connecting your AI agent directly to MiiTel’s backend. Use this server to trigger CSV data exports, create structured records from external webhooks, and manage the entire lifecycle of voice intelligence data through simple natural language prompts.

What your AI can do

Create call record

Imports external call data into MiiTel by simulating an incoming webhook event.

Create meeting record

Imports meeting details, including participant and host metadata, using a simulated incoming webhook.

Create queue

Starts the process of generating a CSV file containing call or meeting history data.

+ 1 more capabilities included

Log Incoming Calls

Your agent uses the create_call_record tool to log external phone system data directly into your MiiTel account.

Log Meeting Transcripts

Use create_meeting_record to import meeting details, including participant and host metadata, from outside systems.

Trigger Data Exports

The server creates a data queue using create_queue, initiating the generation of CSV files for historical call or meeting records.

Monitor Export Status

You check on your queued jobs and their status (Waiting, Processing, Completed, Error) by calling list_queues.

Ask an AI about this

Compatible AI Apps

OAuth 2.0 Compatible

Claude

ChatGPT

Cursor

Gemini

VS Code

JetBrains

Vercel

Zendesk

+ any other MCP app

Included with Plan

Waiting for input…

AI Agent

MiiTel Alternative MCP Server: 4 Tools for Voice Intelligence

These four tools let you manage the entire lifecycle of voice data within MiiTel—from logging raw call records to generating complex CSV reports.

Make your AI actually useful.

Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.

Start using MiiTel on Vinkius

Create Call Record

Imports external call data into MiiTel by simulating an incoming webhook event.

Create Meeting Record

Imports meeting details, including participant and host metadata, using a simulated...

Create Queue

Starts the process of generating a CSV file containing call or meeting history data.

List Queues

Retrieves a list and current status (e.g., WAITING, COMPLETED) for all active and...

Connect to your AI in seconds. Security and governance baked right in.

Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.

Claude AI

Open Claude Settings

Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.

Add Custom Connector

Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL:

https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp

Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. For OAuth-protected servers, expand Advanced settings to add credentials.

Start a conversation

Open a new chat. The MiiTel Alternative integration is available immediately — no restart needed.

Antigravity

Configure Agent Environment

Open your Antigravity agent's workspace configuration or mcp-servers.json file.

Bind the Endpoint

Add the Vinkius endpoint URL to your agent's MCP connections list:

"mcp_servers": {
  "miitel-alternative": {
    "serverUrl": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
  }
}

Provide your secure token in place of [YOUR_TOKEN_HERE] to ensure your agent requests are authenticated.

Execute

Start your Antigravity session. The agent will autonomously discover and utilize the MiiTel Alternative tools with full Vinkius guardrails applied.

VS Code Copilot

⚡

One-Click Install (Recommended)

In your Vinkius Dashboard, simply click the Add to VS Code button for this server. We'll automatically configure your local workspace.

Or configure manually

Open MCP Settings

Open VS Code, press Ctrl/Cmd + Shift + P, and search for GitHub Copilot: MCP Servers.

Add Server Config

Add the Vinkius endpoint configuration to your mcp-servers.json file:

"miitel-alternative": {
  "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
}

Ensure you replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com.

LangChain

Install Dependencies

Install the LangChain MCP adapters for your environment:

pip install langchain-mcp-adapters

Connect the Server

Use the SSEClient in LangChain to connect to the Vinkius managed endpoint:

from langchain_mcp_adapters.client import SSEClient

# Connect to Vinkius
client = SSEClient(url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp")
tools = client.get_tools()

CrewAI

Define the Tool

Load the Vinkius MCP tools into your CrewAI agents:

from crewai import Agent
from mcp_crewai import MCPTool

# Connect securely to Vinkius
vinkius_tools = MCPTool(url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp")

# Assign to Agent
researcher = Agent(
    role='Data Researcher',
    tools=vinkius_tools.get_all()
)

Execute Task

Run your CrewAI process. The agent will autonomously route tasks to the Vinkius managed server.

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

Start building

Make Your AI Do More

Start with MiiTel, then connect any of our 5,000+ other servers whenever your AI needs more. One click, no limits.

Use this MCP plus 5,000+ 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

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by MiiTel. 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

Your data is protected. See how we built it.

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 connection provides 4 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.

Don’t waste time exporting reports just to feed a dashboard.

Today, generating historical data means logging into MiiTel, finding the correct report filter, clicking 'Export,' and dealing with file size limits. Then, you take that messy CSV out of MiiTel and copy-paste the critical columns—like unique IDs or outcome flags—into your BI tool.

With this MCP server, you just tell your agent: 'Give me a clean data feed for Q3 meetings.' It runs `create_queue`, starts the process immediately, and gives you control over the export status via `list_queues`. The output is exactly what you need to run reports on.

The MiiTel Alternative MCP Server: Log data in one chat.

Before, logging a call from an external system meant manual webhooks or complicated middleware setup. You had to worry about formatting the payload correctly before it even touched your system.

Now, you send the raw webhook data through your agent and use `create_call_record`. The server handles the complex mapping and ensures MiiTel logs the record accurately, no matter where the call originated.

Support 24/7 support@vinkius.com ↗

Security Vinkius Trust Center ↗

SLA Service Level Agreement ↗

Report Listing Send Report ↗

What your AI can actually do with this

You’re done jumping between dashboards or manually exporting files. This server lets your AI agent talk directly to MiiTel's backend, handling all the heavy lifting for logging and data management through simple natural language prompts. It keeps you from having to mess with webhooks or complicated APIs yourself; you just tell your agent what you need.

For getting external call logs into MiiTel, you’ll use the create_call_record tool. You feed this function the raw data from an outside phone system—that's simulating a webhook event—and the server imports it directly into your MiiTel account. It treats that incoming information like a real, native call log entry. This means if you got a third-party CRM or another platform logging interactions, you just pipe that data through create_call_record, and it shows up in your system without any manual cleanup or mapping.

When you need to import meeting details from outside systems, you'll use the create_meeting_record tool. This is different from call logging because this function handles more metadata; it imports not just the basic transcript data, but also specific participant information and host details. Like the call logger, it simulates an incoming webhook event, which is how it gets all that structured data into MiiTel’s records seamlessly.

You use create_meeting_record when you've got a batch of meeting transcripts or summaries from another service, and you want them treated as official parts of your MiiTel history.

If the problem isn't logging new events, but rather getting historical data out, you’ll need to trigger an export queue. You start that process with create_queue. Telling the server to use this tool kicks off a background job—a data queue—that starts generating a CSV file containing all the call history or meeting records you specify.

This isn't instant; it runs in the background, and its whole point is to gather potentially massive amounts of historical data into one exportable format. You tell it what kind of data you want (calls or meetings), and it initiates the gathering process.

Once that job is queued up, you need to know what's going on. That’s where list_queues comes in. This tool lets you check the status of every single export job—past jobs and current ones, too. It gives you a clear breakdown: Is it still WAITING for processing? Is it currently PROCESSING and taking its sweet time? Or did it finish up cleanly and is marked as COMPLETED? If something goes wrong, this tool tells you immediately if the job hit an ERROR, so you know exactly where to look.

You use list_queues anytime you need visibility into your data export pipeline.

Basically, you're handling a full lifecycle: logging new calls with create_call_record, logging complete meetings with create_meeting_record, kicking off the historical extraction using create_queue, and finally monitoring the whole deal with list_queues. It keeps your entire voice intelligence data management system in one spot, letting you manage everything through simple prompts to your agent.

Built · Hosted · Managed by Vinkius MiiTel Alternative MCP Server - Log Calls & Export Data

Server ID 019e38c1-96ec-73be-b66b-b0f50a57c3fb

Vinkius Inspector

Compliance Grade F

Score 3.6/100

Report View Report ↗

Here's how it actually works

The bottom line is: you use your AI client to talk to the server, which translates that into specific API calls (like list_queues) to manage your voice data without logging into MiiTel.

Subscribe to the server and enter your MiiTel Tenant Code and API credentials.

Ask your AI client (Claude, Cursor, etc.) to perform an action. For example: 'Start a CSV export queue for last month's call data.'

The agent runs the appropriate tool (create_queue), updates the status in MiiTel, and reports back when the job is ready or if there's an error.

Who is this actually for?

This is for operations engineers and analysts who are tired of manual data pipelines. If you spend time exporting call logs, formatting them in Excel, and then manually uploading them to another system, this server saves hours every week. It centralizes the entire voice intelligence workflow.

Data Analyst

Triggers create_queue to generate CSVs of historical call logs so they can feed into BI dashboards for performance review.

Sales Operations Manager

Uses the server to automatically log outbound calls using create_call_record, ensuring CRM data stays synced with MiiTel without manual effort.

Support Engineer

Imports external ticket or call records via webhooks, letting their AI agent use create_meeting_record to create a unified view of customer history.

What Changes When You Connect

Stop manual data transfers. Instead of exporting logs and copying/pasting them elsewhere, you simply prompt the agent to run create_queue, and MiiTel starts the export process for you automatically.

Centralize disparate records. If your team uses a different phone system, don't worry about syncing it manually. Use create_call_record or create_meeting_record to dump that data into MiiTel using a simple webhook call.

Track jobs without checking the UI. Instead of guessing if an export worked, use list_queues. The agent checks the status in real-time and tells you exactly what's done or where it failed.

Streamline Sales Ops data flow. You can automate the export of call logs for CRM sync by triggering a queue with create_queue, eliminating the need for dedicated ETL scripts just to pull reports.

Handle complex metadata. When logging meetings, you don't just get a title; create_meeting_record handles full participant and host details in one API call.

See it in action

01 01

The Sales Team Needs CRM Sync

A sales manager needs to send yesterday's call logs to the main CRM. Instead of logging into MiiTel, downloading a file, and emailing it out, they ask their agent: 'Start an export queue for all calls from last week.' The agent runs create_queue, tracks the job using list_queues, and alerts the manager when the CSV is ready to download.

02 02

Support Needs Unified Customer View

A support engineer receives a ticket about an issue that happened on a phone call made through a different system. They use their agent to run create_call_record with the webhook data, instantly adding the external call history into MiiTel's unified customer view.

03 03

The Analyst Needs Historical Benchmarks

A business analyst needs a full dataset of all meeting interactions for Q1. They prompt their agent to run create_queue specifically targeting 'Meeting History.' The agent manages the process, and the analyst gets an exportable CSV directly into their data pipeline.

04 04

QA Testing Data Integrity

A QA tester needs to validate that new features correctly log transcripts. They instruct their agent to run create_meeting_record with mock webhook data, confirming the system accepts and processes external metadata before deployment.

The honest tradeoffs

Manual CSV Downloads

Anti-pattern

Manually navigating MiiTel's reporting section, clicking 'Export,' waiting for a download, and then manually uploading that file to another system.

The Fix

Use the create_queue tool. Your agent triggers the export job immediately, handles the process status via list_queues, and notifies you when the data is ready.

Pasting Call Details

Anti-pattern

Copying raw call details (like dates or participant names) from an email into a spreadsheet and then trying to manually input them into MiiTel.

The Fix

Use create_call_record. You send the structured, webhook-formatted data to your agent, which handles the precise API calls needed for accurate logging.

Guessing Record Status

Anti-pattern

Waiting indefinitely after running an export job because you don't know if it failed or is just still processing.

The Fix

Always run list_queues. This tool provides the definitive status (Processing, Error, Completed) and tells you exactly what went wrong.

When It Fits, When It Doesn't

Use this server if your job involves moving voice interaction data—calls or meetings—from System A to MiiTel. It's built for structured logging (create_call_record, create_meeting_record) and batch reporting (CSV generation via create_queue). Don’t use it if you just need to draft a summary email; your agent can handle that without the server. Conversely, don't use this if you are trying to manage user permissions or billing accounts—it only handles call data and queues. If you run into an issue with an export job, always start by calling list_queues before assuming failure.

Questions you might have

How do I check if my CSV export job started with create_queue? +

You use list_queues to see all your current and past jobs. The status will show 'WAITING' or 'PROCESSING,' confirming the queue was successfully created.

Can I import data from a different phone system using create_call_record? +

Yes, create_call_record is designed for this. You send it webhook-formatted data that simulates an incoming call into your MiiTel account.

What does the 'ERROR' status in list_queues mean? +

It means the export job failed to complete. The agent should report a specific error message from MiiTel, which tells you whether it was an API credential issue or data formatting problem.

Do I need to use create_meeting_record for all meeting types? +

No, but if the external system generates structured metadata (like participant lists and host names), create_meeting_record is the tool that correctly ingests and maps those specific details.

When I use `list_queues`, what kind of permissions are needed for my API credentials? +

You need read-only access to the MiiTel data layer. The credentials must have visibility into both the active and historical queue records to successfully list their status.

What is the required format when I use `create_call_record`? +

The input payload needs to be structured JSON that includes at minimum the participant IDs, start time, end time, and associated external webhook ID. Missing identifiers prevent record creation.

Does `create_queue` have any limits on how many records it can process? +

Yes, there are rate limits based on the volume of data requested per hour. For massive historical exports, consider scheduling multiple smaller queues instead of one single request.

If I use `create_meeting_record` and only have partial participant metadata, will it fail? +

The core meeting ID and the timestamps are mandatory. You can often add records with missing secondary details (like optional host names), but the primary identifiers must be present.

Can I programmatically trigger a CSV export of my call history? +

Yes. Use the create_queue tool to generate CSV exports for call or meeting histories. You can then monitor the progress using list_queues.

How do I check if my data export is ready for download? +

Use the list_queues tool. You can filter by process_status (e.g., WAITING, PROCESSING, COMPLETED) to see the current state of your requested exports.

Can I bring call data from other phone systems into MiiTel? +

Absolutely. The create_call_record tool allows you to import call history and audio files from external systems into MiiTel via webhooks.

Connect to your AI in seconds.

Create call record

Create meeting record

Create queue

MiiTel Alternative MCP Server: 4 Tools for Voice Intelligence

Make your AI actually useful.

Create Call Record

Create Meeting Record

Create Queue

List Queues

Connect to your AI in seconds. Security and governance baked right in.

Claude AI

Open Claude Settings

Add Custom Connector

Start a conversation

Claude Code

Open your terminal

Add the MCP Server

Start coding

Cursor

One-Click Install (Recommended)

Open Cursor Settings

Add New Server

Use in Composer

Antigravity

Configure Agent Environment

Bind the Endpoint

Execute

VS Code Copilot

One-Click Install (Recommended)

Open MCP Settings

Add Server Config

Windsurf

One-Click Install (Recommended)

Open Windsurf Settings

Add Server Endpoint

LangChain

Install Dependencies

Connect the Server

CrewAI

Define the Tool

Execute Task

Choose How to Get Started

Build Your Own

Make Your AI Do More

Works with Claude, ChatGPT, Cursor, and more

Don’t waste time exporting reports just to feed a dashboard.

The MiiTel Alternative MCP Server: Log data in one chat.

What your AI can actually do with this

Here's how it actually works

Who is this actually for?

What Changes When You Connect

See it in action

The Sales Team Needs CRM Sync

Support Needs Unified Customer View

The Analyst Needs Historical Benchmarks

QA Testing Data Integrity

The honest tradeoffs

Manual CSV Downloads

Pasting Call Details

Guessing Record Status

When It Fits, When It Doesn't

Questions you might have