Database · MODEL CONTEXT PROTOCOL

nrjchnd voipbin mcp

VoIPBin MCP Server

WHAT IT CONNECTS

What nrjchnd voipbin mcp gives an AI Agent

  • Full VoIPBin API integration through MCP protocol
  • Support for both stdio and SSE transport modes
  • Comprehensive tool definitions with proper annotations
  • Type-safe request/response handling
  • Asynchronous HTTP requests
  • Proper error handling and validation
  • Docker support for easy deployment
  • `get_calls`: Retrieve a list of calls with optional filtering
  • `get_call`: Get details of a specific call
  • `create_call`: Create a new call
  • `end_call`: End an active call
  • `get_agents`: Retrieve a list of agents
  • `get_agent`: Get details of a specific agent
  • `update_agent_status`: Update an agent's status
  • `get_campaigns`: Retrieve a list of campaigns
  • `get_campaign`: Get details of a specific campaign
  • `create_campaign`: Create a new campaign
  • `get_recordings`: Retrieve a list of call recordings
  • `get_recording`: Get details of a specific recording
  • `get_queues`: Retrieve a list of call queues
  • `get_queue`: Get details of a specific queue
  • `get_conferences`: Retrieve a list of active conferences
  • `create_conference`: Create a new conference
  • `get_chats`: Retrieve a list of chat conversations
  • `send_chat_message`: Send a message in a chat conversation
  • `get_billing_info`: Retrieve current billing information
  • `get_billing_history`: Retrieve billing history with optional date filtering
  • Create a virtual environment:
  • Install dependencies:
  • Create a `.env` file:
  • Update the `.env` file with your VoIPBin API credentials:
  • Build and run using Docker Compose:
  • Or build and run using Docker directly:
  • `readOnlyHint`: Indicates if the tool only reads data
  • `destructiveHint`: Indicates if the tool modifies or deletes data
  • `idempotentHint`: Indicates if repeated calls have the same effect as a single call
  • `openWorldHint`: Indicates if the tool operates in an open world context
  • Invalid API credentials
  • Network connectivity issues
  • Invalid request parameters
  • Rate limiting
  • Server errors
  • Add the tool definition in the `list_tools()` function
  • Implement the tool handler in the `voipbin_tool()` function
  • Update the documentation
  • API keys are stored securely in environment variables
  • All requests are authenticated
  • HTTPS is enforced for API communication
  • Input validation is performed on all requests
  • Docker container runs as non-root user
  • Health checks ensure container is running properly
  • Fork the repository
  • Create a feature branch
  • Commit your changes
  • Push to the branch
  • Create a Pull Request
  • Use it commercially
  • Modify it
  • Distribute it
  • Use it privately
  • Sublicense it
  • Include the original copyright notice
  • Include the license text
  • Provide clear attribution to the original source
  • Maintain attribution in any derivative works
  • Hold the author liable for damages
  • Remove or obscure the attribution
  • Claim the work as your own

SECURITY

An MCP listing is not a security review

An MCP server may receive model context, credentials, local files, or permission to call external systems. Review its code, requested environment variables, network behavior, package provenance, and maintenance status before connecting it to an agent.