oitvoip-mcp-server
OfficialClick on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@oitvoip-mcp-server List all active call queues"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
OITVOIP MCP Server
šÆ Production-Ready NetSapiens Integration
Comprehensive MCP server providing AI agents with full access to NetSapiens VoIP platform
A Model Context Protocol (MCP) server that provides AI agents with seamless access to the NetSapiens VoIP platform. This server enables AI applications to interact with NetSapiens functionality including user management, call detail records, and system information.
ā” Features
š„ User Management: Search users, get details, devices, answer rules, greetings, and voicemails
š Phone Number Management: List and manage phone numbers across domains
šÆ Call Center Operations: Manage call queues, agents, login/logout, and statistics
š Call Analytics: Access CDR records, agent statistics, and call patterns
š¢ Domain Administration: Complete domain management and configuration
š¤ Auto Attendant: Configure and manage automated attendants
šµ Media Management: Handle greetings, voicemail, and music on hold
š° Billing Integration: Access billing information and usage data
š§ Real-time Operations: Live access to NetSapiens platform data
ā” Error Handling: Robust error handling with detailed logging
š”ļø Rate Limiting: Built-in rate limiting for API protection
š TypeScript: Full TypeScript support with comprehensive type safety
Related MCP server: VoIPBin MCP Server
šļø Architecture
oitvoip-mcp-server/
āāā src/
ā āāā index.ts # Main MCP server implementation
ā āāā netsapiens-client.ts # NetSapiens API client
āāā types/
ā āāā config.ts # TypeScript type definitions
āāā docs/ # Documentation
āāā build/ # Compiled JavaScript output
āāā package.json # Project dependencies
āāā tsconfig.json # TypeScript configuration
āāā README.md # This fileš Quick Start
Prerequisites
Node.js 18.0.0 or higher
npm or yarn package manager
NetSapiens API credentials
Installation
Option 1: From npm (Recommended)
npm install -g oitvoip-mcp-serverOption 2: From Source
Clone the repository
git clone https://github.com/OITApps/oitvoip-mcp-server.git cd oitvoip-mcp-serverInstall dependencies
npm installBuild the project
npm run buildConfigure in your MCP client
Add the server to your MCP client configuration with your NetSapiens credentials (see MCP Client Setup section below)
Development Mode
For development with hot reloading:
npm run devš§ Configuration
This MCP server is configured entirely through your MCP client's configuration file. No separate .env file is needed - all configuration is passed through environment variables in the MCP client config.
Required Configuration
NETSAPIENS_API_URL: Your NetSapiens API endpoint (usuallyhttps://api.ucaasnetwork.com)NETSAPIENS_API_TOKEN: Your NetSapiens API token
Optional Configuration
DEBUG: Set totrueto enable debug logging (default:false)NETSAPIENS_TIMEOUT: API request timeout in milliseconds (default:30000)
š MCP Client Setup
OpenCode
For OpenCode, add the MCP server to your configuration file at ~/.opencode/mcp.json:
If installed via npm:
{
"mcpServers": {
"oitvoip": {
"command": "oitvoip-mcp-server",
"env": {
"NETSAPIENS_API_URL": "https://api.ucaasnetwork.com",
"NETSAPIENS_API_TOKEN": "your_api_token_here"
}
}
}
}If installed from source:
{
"mcpServers": {
"oitvoip": {
"command": "node",
"args": ["/path/to/oitvoip-mcp-server/build/index.js"],
"env": {
"NETSAPIENS_API_URL": "https://api.ucaasnetwork.com",
"NETSAPIENS_API_TOKEN": "your_api_token_here"
}
}
}
}Claude Desktop
For Claude Desktop, add the server to your configuration file:
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
If installed via npm:
{
"mcpServers": {
"oitvoip": {
"command": "oitvoip-mcp-server",
"env": {
"NETSAPIENS_API_URL": "https://api.ucaasnetwork.com",
"NETSAPIENS_API_TOKEN": "your_api_token_here"
}
}
}
}If installed from source:
{
"mcpServers": {
"oitvoip": {
"command": "node",
"args": ["/path/to/oitvoip-mcp-server/build/index.js"],
"env": {
"NETSAPIENS_API_URL": "https://api.ucaasnetwork.com",
"NETSAPIENS_API_TOKEN": "your_api_token_here"
}
}
}
}Cursor
For Cursor, add the server to your MCP configuration file at ~/.cursor/mcp.json:
If installed via npm:
{
"mcpServers": {
"oitvoip": {
"command": "oitvoip-mcp-server",
"env": {
"NETSAPIENS_API_URL": "https://api.ucaasnetwork.com",
"NETSAPIENS_API_TOKEN": "your_api_token_here"
}
}
}
}If installed from source:
{
"mcpServers": {
"oitvoip": {
"command": "node",
"args": ["/path/to/oitvoip-mcp-server/build/index.js"],
"env": {
"NETSAPIENS_API_URL": "https://api.ucaasnetwork.com",
"NETSAPIENS_API_TOKEN": "your_api_token_here"
}
}
}
}Configuration Notes
Replace
/path/to/oitvoip-mcp-serverwith the actual path to your installationReplace
your_api_token_herewith your actual NetSapiens API tokenAll configuration is handled through the MCP client - no separate
.envfile is neededAfter configuration, restart your MCP client to load the server
š ļø Available Tools (23 Total)
š„ User Management
1. Search Users
Search for users in the NetSapiens system by username.
{
"name": "search_users",
"arguments": {
"query": "john.doe",
"domain": "company.com",
"limit": 20
}
}2. Get User Details
Retrieve detailed information about a specific user.
{
"name": "get_user",
"arguments": {
"userId": "john.doe",
"domain": "company.com"
}
}3. Get User Devices
Get devices assigned to a specific user.
{
"name": "get_user_devices",
"arguments": {
"userId": "john.doe",
"domain": "company.com"
}
}š Phone Number Management
4. Get Phone Numbers
Get phone numbers for a domain.
{
"name": "get_phone_numbers",
"arguments": {
"domain": "company.com",
"limit": 50
}
}5. Get Phone Number Details
Get details of a specific phone number.
{
"name": "get_phone_number",
"arguments": {
"domain": "company.com",
"phoneNumber": "+15551234567"
}
}š¢ Domain Management
6. Get Domains
Get list of domains in the NetSapiens system.
{
"name": "get_domains",
"arguments": {}
}7. Get Domain Details
Get detailed information about a specific domain.
{
"name": "get_domain",
"arguments": {
"domain": "company.com"
}
}šÆ Call Center Management
8. Get Call Queues
Get call queues for a domain.
{
"name": "get_call_queues",
"arguments": {
"domain": "company.com"
}
}9. Get Call Queue Details
Get details of a specific call queue.
{
"name": "get_call_queue",
"arguments": {
"domain": "company.com",
"queueId": "sales-queue"
}
}10. Get Call Queue Agents
Get agents assigned to a call queue.
{
"name": "get_call_queue_agents",
"arguments": {
"domain": "company.com",
"queueId": "sales-queue"
}
}11. Get Agents
Get agents for a domain.
{
"name": "get_agents",
"arguments": {
"domain": "company.com"
}
}12. Login Agent
Login an agent to a call queue.
{
"name": "login_agent",
"arguments": {
"domain": "company.com",
"queueId": "sales-queue",
"agentId": "agent001"
}
}13. Logout Agent
Logout an agent from a call queue.
{
"name": "logout_agent",
"arguments": {
"domain": "company.com",
"queueId": "sales-queue",
"agentId": "agent001"
}
}š Call Analytics
14. Get CDR Records
Retrieve call detail records with optional filtering.
{
"name": "get_cdr_records",
"arguments": {
"startDate": "2024-01-01",
"endDate": "2024-01-31",
"user": "john.doe",
"domain": "company.com",
"limit": 100
}
}15. Get Agent Statistics
Get agent statistics for a domain.
{
"name": "get_agent_statistics",
"arguments": {
"domain": "company.com",
"agentId": "agent001"
}
}š¤ Auto Attendant
16. Get Auto Attendants
Get auto attendants for a domain.
{
"name": "get_auto_attendants",
"arguments": {
"domain": "company.com"
}
}š Answer Rules
17. Get User Answer Rules
Get answer rules for a user.
{
"name": "get_user_answer_rules",
"arguments": {
"userId": "john.doe",
"domain": "company.com"
}
}18. Get User Answer Rule
Get specific answer rule for a user.
{
"name": "get_user_answer_rule",
"arguments": {
"userId": "john.doe",
"domain": "company.com",
"timeframe": "business"
}
}šµ Media Management
19. Get User Greetings
Get greetings for a user.
{
"name": "get_user_greetings",
"arguments": {
"userId": "john.doe",
"domain": "company.com"
}
}20. Get User Voicemails
Get voicemails for a user.
{
"name": "get_user_voicemails",
"arguments": {
"userId": "john.doe",
"domain": "company.com"
}
}21. Get Music on Hold
Get music on hold files for a domain.
{
"name": "get_music_on_hold",
"arguments": {
"domain": "company.com"
}
}š° Billing
22. Get Billing
Get billing information for a domain.
{
"name": "get_billing",
"arguments": {
"domain": "company.com"
}
}š§ System
23. Test Connection
Test connectivity to the NetSapiens API.
{
"name": "test_connection",
"arguments": {}
}š API Examples
Searching for Users
// Search for users with "john" in a specific domain
const result = await mcp.callTool('search_users', {
query: 'john',
domain: 'company.com',
limit: 10
});Getting User Details
// Get detailed information about a specific user
const result = await mcp.callTool('get_user', {
userId: 'john.doe',
domain: 'company.com'
});Getting Call Records
// Get call records for a specific user in the last month
const result = await mcp.callTool('get_cdr_records', {
startDate: '2024-01-01',
endDate: '2024-01-31',
user: 'john.doe',
domain: 'company.com'
});Getting User Devices
// Get devices assigned to a user
const result = await mcp.callTool('get_user_devices', {
userId: 'john.doe',
domain: 'company.com'
});šāāļø Development
Available Scripts
npm run build- Compile TypeScript to JavaScriptnpm run dev- Run in development mode with hot reloadingnpm start- Run the compiled servernpm run watch- Watch mode for developmentnpm run clean- Clean build directory
Project Structure
src/
āāā index.ts # Main server entry point
āāā netsapiens-client.ts # NetSapiens API client
āāā tools/ # Individual tool implementations
types/
āāā config.ts # Configuration types
āāā netsapiens.ts # NetSapiens API typesAdding New Tools
Define the tool in the
ListToolsRequestSchemahandlerAdd a handler method in the
CallToolRequestSchemahandlerImplement the tool logic in the NetSapiens client
Update type definitions as needed
š Security
š MCP Security Best Practices
API Tokens: Configure your NetSapiens API tokens securely in your MCP client configuration
Token Security: Use strong API tokens and rotate them regularly
Access Control: Ensure API tokens have minimal required permissions
Rate Limiting: Built-in rate limiting prevents API abuse
Error Handling: Secure error logging without exposing sensitive data
Input Validation: All inputs are validated before processing
šØ Security Guidelines
Secure MCP Configuration: Store your MCP client configuration files securely
Strong API Tokens: Use secure NetSapiens API tokens and rotate regularly
Monitor Access: Check NetSapiens access logs for unauthorized usage
Regular Audits: Run
npm auditregularly for dependency vulnerabilitiesKeep Updated: Maintain latest versions for security patches
HTTPS Only: All API communications use secure HTTPS connections
Environment Isolation: Use different tokens for development/production environments
š Troubleshooting
Common Issues
Connection Failed
Verify your API URL and token in
.envCheck network connectivity to NetSapiens server
Ensure API token has proper permissions
Build Errors
Run
npm run cleanand rebuildCheck TypeScript configuration
Verify all dependencies are installed
Tool Not Found
Ensure the tool name matches exactly
Check the tool is properly registered in
ListToolsRequestSchema
Debug Mode
Enable debug logging by setting DEBUG=true in your .env file:
DEBUG=trueš Documentation
š¤ Contributing
Fork the repository
Create a feature branch (
git checkout -b feature/amazing-feature)Commit your changes (
git commit -m 'Add some amazing feature')Push to the branch (
git push origin feature/amazing-feature)Open a Pull Request
š License
This project is licensed under the MIT License - see the LICENSE file for details.
š¢ About OITVOIP
OITVOIP provides comprehensive VoIP solutions powered by the NetSapiens platform. This MCP server enables seamless integration between AI applications and our VoIP infrastructure.
Built with ā¤ļø by the OITVOIP team
From frontend finesse to backend brilliance - we stack it all! ā
Available Tools
23 toolsget_agentsB
Get agents for a domain
Inputs: domain (required).
get_agent_statisticsB
Get agent statistics for a domain
Inputs: domain (required), agentId.
get_auto_attendantsC
Get auto attendants for a domain
Inputs: domain (required).
get_billingB
Get billing information for a domain
Inputs: domain (required).
get_call_queueB
Get details of a specific call queue
Inputs: domain (required), queueId (required).
get_call_queue_agentsB
Get agents assigned to a call queue
Inputs: domain (required), queueId (required).
get_call_queuesB
Get call queues for a domain
Inputs: domain (required).
get_cdr_recordsB
Retrieve call detail records (CDR)
Inputs: startDate, endDate, user, domain, +1 more.
get_domainB
Get detailed information about a specific domain
Inputs: domain (required).
get_domainsC
Get list of domains in the NetSapiens system
Inputs: no named parameters.
get_music_on_holdB
Get music on hold files for a domain
Inputs: domain (required).
get_phone_numberC
Get details of a specific phone number
Inputs: domain (required), phoneNumber (required).
get_phone_numbersC
Get phone numbers for a domain
Inputs: domain (required), limit.
get_userC
Get detailed information about a specific user
Inputs: userId (required), domain (required).
get_user_answer_ruleC
Get specific answer rule for a user
Inputs: userId (required), domain (required), timeframe (required).
get_user_answer_rulesC
Get answer rules for a user
Inputs: userId (required), domain (required).
get_user_devicesB
Get devices assigned to a specific user
Inputs: userId (required), domain (required).
get_user_greetingsC
Get greetings for a user
Inputs: userId (required), domain (required).
get_user_voicemailsC
Get voicemails for a user
Inputs: userId (required), domain (required).
login_agentC
Login an agent to a call queue
Inputs: domain (required), queueId (required), agentId (required).
logout_agentB
Logout an agent from a call queue
Inputs: domain (required), queueId (required), agentId (required).
search_usersC
Search for users in the NetSapiens system
Inputs: query (required), domain, limit.
test_connectionB
Test connectivity to NetSapiens API
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelogā¦
TDQS
Scored across 23 tools
Most tools target distinct resources (agents, domains, users, call queues, phone numbers, etc.), but there are a few potentially confusing pairs like `get_call_queue` vs `get_call_queues` and `get_phone_number` vs `get_phone_numbers`, though descriptions clarify the singular/plural distinction.
The vast majority of tools follow the 'get_<resource>' pattern, with only three exceptions (`login_agent`, `logout_agent`, `test_connection`). This deviation is minor but prevents a perfect score.
23 tools is slightly above the typical range for a focused server, but the domain (VoIP management) has many distinct resource types, so the count is reasonable and each tool serves a clear purpose.
The tool surface is heavily read-oriented with almost all tools being getters. Only two mutation tools exist (login/logout agent). Missing CRUD operations for domains, users, phone numbers, etc., severely limits management capabilities.
Maintenance
Related MCP Connectors
MCP server enabling AI agents to manage Bitrix24 features via standardized protocol
The Telnyx MCP server is an official implementation of the Model Context Protocol that enables AI clients (like Claude Desktop, Cursor, and OpenAI Agents) to interact with Telnyx's telephony, messaging, and AI assistant APIs. It provides comprehensive capabilities including making and managing phone calls, sending SMS/MMS messages, purchasing and configuring phone numbers, creating AI assistants with custom instructions, managing cloud storage buckets, scraping and embedding website content, and handling integration secrets. The server exists as both a local implementation and a remotely hosted version, allowing developers to integrate real-world communication infrastructure directly into AI applications.
Hosted MCP server connecting AI assistants to 9,000+ apps and 40,000+ actions via Zapier.
MCP server unifying ERPs, CRMs, APIs and knowledge base for Claude, ChatGPT and Gemini.
Related MCP Servers
- AlicenseBqualityCmaintenanceThe Voyp MCP Server enables AI systems to integrate with VOYP's calling capabilities, allowing for secure telephony actions such as making calls, scheduling appointments, and tracking call statuses through the Model Context Protocol.753 npm10MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables AI models to interact with VoIPBin's VoIP services, supporting features like call management, agent management, campaigns, conferences, and chat functionality.4MIT
- AlicenseNot gradedqualityBmaintenanceAn MCP server that enables AI assistants to manage Cisco Unified Communications Manager (CUCM) via AXL SOAP API, supporting provisioning, configuration, and database queries through natural language.318 npm7MIT
- AlicenseAqualityCmaintenanceMCP server for the Ringer WARP platform giving AI agents 135 tools to manage SIP trunking, phone numbers, porting, messaging, billing, and analytics.13566 npmMIT