didlogic_mcp
This archived MCP server lets LLMs interact with the Didlogic API to manage account, SIP, DID, and billing data.
Check account balance.
List/get/create/update/delete SIP accounts.
View/add/remove SIP account IP allowlists.
List purchased DIDs, purchase new DIDs, and remove DIDs.
List/add/delete DID destinations.
Browse countries, regions, cities, and available DIDs for purchase.
Query inbound/outbound call history.
Load transaction history.
Click 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., "@didlogic_mcp check my account balance"
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.
Didlogic MCP Server
This project is archived and no longer maintained. It has been superseded by the official Didlogic MCP server:
Hosted server: https://mcp.didlogic.com
A Model Context Protocol (MCP) server implementation for the Didlogic API. This server allows Large Language Models (LLMs) to interact with Didlogic services through a standardized interface.
Features
Full access to Didlogic API through MCP tools
Specialized prompts for common operations
Balance management tools
SIP account (sipfriends) management
IP restriction management
Purchases management
Call hisory access
Transaction history access
Related MCP server: Twilio MCP Server
Installation
Using uv (recommended)
When using uv no specific installation is needed. We will
use uvx to directly run didlogic_mcp.
Using PIP
Alternatively you can install didlogic_mcp via pip:
pip install didlogic_mcpAfter installation, you can run it as a script using:
DIDLOGIC_API_KEY=YOUR_DIDLOGIC_KEY python -m didlogic_mcpTransport Modes
The server supports three transport modes:
STDIO Mode (Default)
For local integration with Claude Desktop or similar tools. Uses the DIDLOGIC_API_KEY environment variable for authentication.
# Using uvx (recommended)
DIDLOGIC_API_KEY=your_key uvx didlogic_mcp
# Using uv run
DIDLOGIC_API_KEY=your_key uv run didlogic_mcp
# As Python module
DIDLOGIC_API_KEY=your_key python -m didlogic_mcp --transport stdioHTTP Mode
For remote access and web clients. Requires Bearer token in Authorization header for each request.
# Using default port (8000)
python -m didlogic_mcp --transport http
# Custom port via environment variable
PORT=9000 python -m didlogic_mcp --transport http
# Custom host and port
python -m didlogic_mcp --transport http --host 0.0.0.0 --port 9000
# With debug logging
python -m didlogic_mcp --transport http --log-level DEBUGEnvironment Variables:
PORT- Server port (default: 8000)DIDLOGIC_API_URL- Didlogic API base URL (default: https://app.didlogic.com/api)
Note: In HTTP mode, clients must provide their API key as a Bearer token in the Authorization header.
SSE Mode (Server-Sent Events)
For streaming communication with persistent connections. Ideal for real-time updates and streaming scenarios. Requires Bearer token in Authorization header for each request.
# Using default port (8000)
python -m didlogic_mcp --transport sse
# Custom port via environment variable
PORT=9000 python -m didlogic_mcp --transport sse
# Custom host and port
python -m didlogic_mcp --transport sse --host 0.0.0.0 --port 9000
# With debug logging
python -m didlogic_mcp --transport sse --log-level DEBUGEnvironment Variables:
PORT- Server port (default: 8000)DIDLOGIC_API_URL- Didlogic API base URL (default: https://app.didlogic.com/api)
Note: In SSE mode, clients must provide their API key as a Bearer token in the Authorization header for persistent streaming connections.
Configuration
Configure for Claude.app
Add to your Claude settings:
Using uvx
"mcpServers": {
"didlogic": {
"command": "uvx",
"args": ["didlogic_mcp"],
"env": {
"DIDLOGIC_API_KEY": "YOUR_DIDLOGIC_KEY"
}
}
}Using pip installation
"mcpServers": {
"didlogic": {
"command": "python",
"args": ["-m", "didlogic_mcp"],
"env": {
"DIDLOGIC_API_KEY": "YOUR_DIDLOGIC_KEY"
}
}
}Configure for Claude Code
For Claude Code, you can connect to a running SSE server instance:
claude mcp add didlogic --transport sse http://localhost:8000/sse --header "Authorization: Bearer YOUR_DIDLOGIC_API_KEY"Prerequisites:
Start the server in SSE mode:
python -m didlogic_mcp --transport sseRun the above command, replacing
YOUR_DIDLOGIC_API_KEYwith your actual API keyThe server must be running and accessible at the specified URL
Custom configuration:
To use a different port: Change
http://localhost:8000/sseto match your server's PORT settingTo connect to a remote server: Replace
localhostwith the server's hostname or IP address
License
MIT
Available Tools
22 toolsadd_allowed_ipA
Whitelist an IP to a SIP account
Args: sipaccount_name: Name of SIP account ip: IP address to allow
Returns a JSON object with all whitelisted IP addresses for account Example output: { "allowed_ips": [ "88.99.12.33", "99.33.55.11" ] }
Inputs: ip (required), sipaccount_name (required).
add_destinationB
Add a DID destination.
Args: number: DID number in DIDLogic callhunt: flag indicates do destination is part of ring all group active: flag indicates is destination enabled or not transport: transport of destination where: 1 = SIP address destination (ex: 123@example.com) 4 = PSTN (phone number) destination (ex: 15551231233) 5 = SIP account destination (ex: 12345) destination: destination
Returns a JSON object with did destination where: id: ID of destination destination: destination priority: priority of selection callhunt: flag indicates do destination is part of ring all group active: flag indicates is destination enabled or not transport: transport of destination where: 1 = SIP address destination (ex: 123@example.com) 4 = PSTN (phone number) destination (ex: 15551231233) 5 = SIP account destination (ex: 12345)
Example:
{
"did_destination": {
"id": 1234455,
"destination": "12345",
"priority": 1,
"callhunt": false,
"active": true,
"transport": 5
}
}Inputs: destination (required), number (required), active, callhunt, +1 more.
create_sip_accountA
Creates a new SIP account
Args: password: Password to be used for this SIP account callerid: CallerID associated with this SIP account label: label fot this SIP account rewrite_enabled: do SIP account have calling number rewriting rule rewrite_cond: prefix to be rewrited (ex: 00) rewrite_prefix: prefix to what should be rewritten (ex: 44) didinfo_enabled: do DIDLogic will attempt send DID number as TO when receiving calls to this account ip_restrict: do we need to allowlist IP addresses for this account call_restrict: flag indicates what SIP account should have maximum call time call_limit: maximum call duration in seconds channels_restrict: flag indicates what SIP account should have maximum channels limit max_channels: maximum sip channels cost_limit: flag indicates what SIP account should have maximum call cost max_call_cost: maximum call cost for this SIP account
Returns a JSON object with SIP account details where: id: ID of SIP account name: SIP account name (login) callerid: CallerID associated with this SIP account label: label fot this SIP account charge: charge for calls on this month talk_time: total talk time for this month rewrite_enabled: do SIP account have calling number rewriting rule rewrite_cond: prefix to be rewrited (ex: 00) rewrite_prefix: prefix to what should be rewritten (ex: 44) didinfo_enabled: do DIDLogic will attempt send DID number as TO when receiving calls to this account ip_restrict: do we need to allowlist IP addresses for this account allowed_ips: IP addresses allowed for this SIP account call_restrict: flag indicates what SIP account should have maximum call time call_limit: maximum call duration in seconds channels_restrict: flag indicates what SIP account should have maximum channels limit max_channels: maximum sip channels cost_limit: flag indicates what SIP account should have maximum call cost max_call_cost: maximum call cost for this SIP account created_at: date of creation this SIP account
Example:
{
"sipaccount": {
"id": 61,
"name": "12345",
"callerid": "17254999999",
"label": "TEST DEVICE",
"host": "dynamic",
"charge": "0.0",
"talk_time": 0,
"rewrite_enabled": false,
"rewrite_cond": "8",
"rewrite_prefix": "7",
"didinfo_enabled": false,
"ip_restrict": false,
"call_restrict": true,
"call_limit": 2800,
"channels_restrict": false,
"max_channels": 1,
"cost_limit": false,
"max_call_cost": "5.0",
"created_at": "2024-06-03 06:06:47 UTC",
"allowed_ips": ["1.2.3.4", "3.4.5.6"]
}
}Inputs: password (required), label, callerid, call_limit, +10 more.
delete_allowed_ipC
Delete an whitelisted IP from a SIP account
Args: sipaccount_name: Name of SIP account ip: IP address to remove from whitelist
Returns "IP removed successfully" when IP removed from whitelisted
Inputs: ip (required), sipaccount_name (required).
delete_destinationC
Remove destination from DID.
Args: number: DID number in DIDLogic id: destination ID to remove
Returns a Destination deleted on success
Inputs: id (required), number (required).
delete_sip_accountC
Delete a SIP account
Args: name: SIP account name
Returns a SIP Account deleted message on success
Inputs: name (required).
get_allowed_ipsB
Get list of whitelisted IPs for a SIP account
Args: sipaccount_name: Name of SIP account
Returns a JSON object with array of whitelisted IP for SIP Account Example output: { "allowed_ips": [ "88.99.12.33" ] }
Inputs: sipaccount_name (required).
get_balanceB
Get the current DIDLogic account balance
Returns a JSON object with balance in USD
Example output: {"balance": 35.22}
Inputs: no named parameters.
get_call_historyB
Query Call history in DIDlogic
Args: call_type: Type of call history items where: sip = outbound sip calls incoming = inbound calls to DID from_date: Date to search from, should be in YYYY-MM-DD format to_date: Date to search to, should be in YYYY-MM-DD format number: Number to search for incoming calls sip_account: SIP account name to search for outbound calls from_search: Number from whom was the call to_search: Number to what was the call page: page of result starting with 1 per_page: how many results should be on per page
Returns a JSON object with a call history results where: calls: array of call history objects where: timestamp: date of the call type: call type where: sip = outbound sip call incoming = inbound call to DID amount: charge for this call in USD duration: duration of call in seconds from: from number for this call to: to number which this call was made destination_name: destination network name for this call sip_account: SIP account name for outbound SIP calls pagination: Pagination details for results page: current page of results per_page: results per page total_pages: total pages results total_records: total query records (maximum 5000)
Example response:
{
"calls": [
{
"timestamp": "2024-11-20T13:29:19Z",
"type": "sip",
"amount": 0.02,
"duration": 0,
"from": """ <1212123123>",
"to": "1555123123",
"destination_name": "United States - NOT EXISTED",
"sip_account": "12345"
}
],
"pagination": {
"page": 1,
"per_page": 100,
"total_pages": 50,
"total_records": 5000
}
}Inputs: from_date (required), to_date (required), call_type, from_search, +5 more.
get_sip_accountB
Get details about SIP account
Args: name: SIP account name
Returns a JSON object with SIP account details where: id: ID of SIP account name: SIP account name (login) callerid: CallerID associated with this SIP account label: label fot this SIP account charge: charge for calls on this month talk_time: total talk time for this month rewrite_enabled: do SIP account have calling number rewriting rule rewrite_cond: prefix to be rewrited (ex: 00) rewrite_prefix: prefix to what should be rewritten (ex: 44) didinfo_enabled: do DIDLogic will attempt send DID number as TO when receiving calls to this account ip_restrict: do we need to allowlist IP addresses for this account allowed_ips: IP addresses allowed for this SIP account call_restrict: flag indicates what SIP account should have maximum call time call_limit: maximum call duration in seconds channels_restrict: flag indicates what SIP account should have maximum channels limit max_channels: maximum sip channels cost_limit: flag indicates what SIP account should have maximum call cost max_call_cost: maximum call cost for this SIP account created_at: date of creation this SIP account
Example:
{
"sipaccount": {
"id": 61,
"name": "12345",
"callerid": "17254999999",
"label": "TEST DEVICE",
"host": "dynamic",
"charge": "0.0",
"talk_time": 0,
"rewrite_enabled": false,
"rewrite_cond": "8",
"rewrite_prefix": "7",
"didinfo_enabled": false,
"ip_restrict": false,
"call_restrict": true,
"call_limit": 2800,
"channels_restrict": false,
"max_channels": 1,
"cost_limit": false,
"max_call_cost": "5.0",
"created_at": "2024-06-03 06:06:47 UTC",
"allowed_ips": ["1.2.3.4", "3.4.5.6"]
}
}Inputs: name (required).
get_transactionsA
Load transaction history from DIDLogic
Args: transaction_type: Type of transaction to search where: adjustment = Adjustments made by DIDLogic finances activation = Activation payments for DID month = Monthly payments for DID paypal_in = Paypal TopUps call = Per minute charges for inbound calls call_fix_fee = Per minute charges for PSTN DID destinations sms = SMS charges inbound_sms = Inbound SMS charges cc_in = Credit card TopUps stripe_in = Stripe express payments TopUps porting = Porting Fees start_date: Search start date in format YYYY-MM-DD end_date: Search end date in format YYYY-MM-DD
Returns a CSV table of transactions where: Date: Date of transaction Time: Time of transaction Transaction type: Type of transaction Comment: Comment for transaction Amount: Transaction Amount Balance: Balance after transaction creation Status: Transaction status where: Confirmed = transaction confirmed but not commited yet Committed = transaction settled Rejected = transaction reverted back
Example:
Date,Time,Transaction type,Comment,Amount,Balance,Status
01/05/25,06:00 am,Monthly fees,Monthly fee for 18565999999,$-0.9900,$16.1273,CommittedInputs: end_date (required), start_date (required), transaction_type.
list_countriesB
List available countries with DID for purchase on DIDLogic
Args: sms_enabled: search for DID with SMS functionality
Returns a JSON object with available countries for purchase. Returned countries list have following fields: id: ID of country name: Name of country in DIDLogic short_name: ISO code of country has_provinces_or_states: do country have provinces or states which can be queried by list_country_regions tool.
403 error indicates disabled API calls for purchase.
Example:
{
"countries": [
{
"id": 8669,
"name": "Argentina",
"short_name": "AR",
"has_provinces_or_states": false
}
]
}Inputs: sms_enabled.
list_country_citiesB
List of Cities with available DID for purchase in a country
Args: country_id: ID of country for search sms_enabled: search for DID with SMS functionality
Returns a JSON object with available cities for purchase DIDs. Returned cities list have following fields: id: ID of city name: Name of city in DIDLogic area_code: Area code within country count: count of available DIDs for purchasing
403 error indicates disabled API calls for purchase.
Example:
{
"cities": [
{
"id": 118557,
"name": "Ottawa-Hull, ON",
"area_code": "613800",
"count": 81
}
]
}Inputs: country_id (required), sms_enabled.
list_country_cities_in_regionA
List of Cities with available DID in a region of a country
Args: country_id: ID of country for search region_id: ID of region in a country sms_enabled: search for DID with SMS functionality
Returns a JSON object with available cities for purchase DIDs. Returned cities list have following fields: id: ID of city name: Name of city in DIDLogic area_code: Area code within country count: count of available DIDs for purchasing
403 error indicates disabled API calls for purchase.
Example:
{
"cities": [
{
"id": 118557,
"name": "Ottawa-Hull, ON",
"area_code": "613800",
"count": 81
}
]
}Inputs: country_id (required), region_id (required), sms_enabled.
list_country_regionsA
List country regions with available DIDs for purchase
Args: country_id: ID of country for search sms_enabled: search for DID with SMS functionality
Returns a JSON object with available regions for purchase. Returned countries list have following fields: id: ID of region name: Name of region in DIDLogic short_name: short code for region
403 error indicates disabled API calls for purchase.
Example:
{
"regions": [
{
"id": 1,
"name": "Alberta",
"short_name": "AB"
}
}Inputs: country_id (required), sms_enabled.
list_destinationsC
List DID destination.
Args: number: DID number in DIDLogic
Returns a JSON object with all did destinations where: id: ID of destination destination: destination priority: priority of selection callhunt: flag indicates do destination is part of ring all group active: flag indicates is destination enabled or not transport: transport of destination where: 1 = SIP address destination (ex: 123@example.com) 4 = PSTN (phone number) destination (ex: 15551231233) 5 = SIP account destination (ex: 12345)
Example:
{
"destination": [
{
"id": 1234455,
"destination": "12345",
"priority": 1,
"callhunt": false,
"active": true,
"transport": 5
}
]
}Inputs: number (required).
list_dids_in_country_cityA
List of available DID in a city of a country
Args: country_id: ID of country for search city_id: ID of city in a country sms_enabled: search for DID with SMS functionality page: page of result starting with 1 per_page: how many results should be on per page
Returns a JSON object with available DIDs where: dids: Array of DID available for purchasing where: id: ID of DID country: Country name city: City name sms_enabled: Is number capable of receiving SMS channels: How many parallel channels have DID free_min: How many free minutes per month DID have activation: Activation cost for DID in USD monthly: Monthly fee for DID per_minute: Per minute cost for DID origination_per_min: per minute cost if origin based rate applied required_documents: required documents for activating number, where: 1 = Any form of ID 2 = Proof of address 3 = Proof of local address number: DID Number in E164 format pagination: Pagination details for results page: current page of results total_pages: total pages results total: total query records
403 error indicates disabled API calls for purchase.
Example:
{
"dids": {
"pagination": {
"total": 52,
"total_pages": 1,
"current_page": 1
},
"dids": [
{
"id": 112370,
"country": "Canada",
"city": "Edmonton, AB",
"sms_enabled": false,
"no_local_cli": false,
"channels": 4,
"free_min": 0,
"cnam": null,
"activation": 1.0,
"monthly": 1.0,
"per_minute": 0.01,
"origination_per_min": null,
"required_documents": [],
"state": "Alberta",
"country_short_name": "CA",
"number": "17806999999"
}
]
}
}Inputs: city_id (required), country_id (required), page, per_page, +1 more.
list_purchasesB
List purchased DIDs in DIDLogic
Args: page: page of result starting with 1 per_page: how many results should be on per page
Returns a JSON object with a call history results where: purchases: List of purchased DIDs number: Number of DID channels: How many parallel channels DID have country: Country name area: City name free_minutes: How many free minutes per month DID have activation: Activation cost for DID in USD monthly_fee: Monthly fee for DID per_minute: Per minute cost for DID codec: what SIP codec is preferred for this number check_state: DID state
pagination: Pagination details for results
page: current page of results
per_page: results per page
total_pages: total pages results
total_records: total query records (maximum 5000)Example response:
{
"purchases": [
{
"number": "441172999999",
"channels": 2,
"country": "United Kingdom",
"area": "Bristol",
"codec": "G711",
"activation": 0.0,
"monthly_fee": 0.99,
"per_minute": 0.001,
"check_state": "checked",
"free_minutes": 0
}
],
"pagination": {
"pages": 1,
"page": 1,
"per_page": 100,
"total_records": 50
}
}Inputs: page, per_page.
list_sip_accountsB
List all SIP accounts
Returns a JSON object with all SIP accounts where: id: ID of SIP account name: SIP account name (login) callerid: CallerID associated with this SIP account label: label fot this SIP account charge: charge for calls on this month talk_time: total talk time for this month rewrite_enabled: do SIP account have calling number rewriting rule rewrite_cond: prefix to be rewrited (ex: 00) rewrite_prefix: prefix to what should be rewritten (ex: 44) didinfo_enabled: do DIDLogic will attempt send DID number as TO when receiving calls to this account ip_restrict: do we need to allowlist IP addresses for this account allowed_ips: IP addresses allowed for this SIP account call_restrict: flag indicates what SIP account should have maximum call time call_limit: maximum call duration in seconds channels_restrict: flag indicates what SIP account should have maximum channels limit max_channels: maximum sip channels cost_limit: flag indicates what SIP account should have maximum call cost max_call_cost: maximum call cost for this SIP account created_at: date of creation this SIP account
Example:
{
"sipaccounts": [
{
"id": 61,
"name": "12345",
"callerid": "17254999999",
"label": "TEST DEVICE",
"host": "dynamic",
"charge": "0.0",
"talk_time": 0,
"rewrite_enabled": false,
"rewrite_cond": "8",
"rewrite_prefix": "7",
"didinfo_enabled": false,
"ip_restrict": false,
"call_restrict": true,
"call_limit": 2800,
"channels_restrict": false,
"max_channels": 1,
"cost_limit": false,
"max_call_cost": "5.0",
"created_at": "2024-06-03 06:06:47 UTC",
"allowed_ips": ["1.2.3.4", "3.4.5.6"]
}
]
}Inputs: no named parameters.
purchase_didB
Purchase DID from DIDLogic
Args: number: DID number for purchase in E164 format
Returns a JSON object with purchased DID details where: errors: Errors what happened in purchase process purchases: Array of purchased dids where: id: ID of purchased DID number: number of DID country: Country name area: City name sms_enabled: Is number capable of receiving SMS channels: How many parallel channels have DID free_minutes: How many free minutes per month DID have activation: Activation cost for DID in USD monthly_fee: Monthly fee for DID per_minute: Per minute cost for DID origination_per_min: per minute cost if origin based rate applied requir_docs: required documents for activating number, where: 1 = Any form of ID 2 = Proof of address 3 = Proof of local address codec: what SIP codec is preferred for this number
Example:
{
"purchase": {
"errors": {},
"purchases": [
{
"id": 728070,
"number": "17806999999",
"sms_enabled": false,
"no_local_cli": false,
"channels": 4,
"country": "Canada",
"area": "Edmonton, AB",
"free_minutes": 0,
"codec": "G711",
"require_docs": "",
"activation": 1.0,
"monthly_fee": 1.0,
"per_minute": 0.01,
"origination_per_min": 0.0
}
]
}
}Inputs: number (required).
remove_purchased_didA
Remove DID from DIDLogic account
Args: number: DID number for removing in E164 format
Returns a JSON object with removed DID details where: dids: Array of removed dids where: id: ID of purchased DID number: number of DID country: Country name area: City name sms_enabled: Is number capable of receiving SMS channels: How many parallel channels have DID free_minutes: How many free minutes per month DID have activation: Activation cost for DID in USD monthly_fee: Monthly fee for DID per_minute: Per minute cost for DID origination_per_min: per minute cost if origin based rate applied requir_docs: required documents for activating number, where: 1 = Any form of ID 2 = Proof of address 3 = Proof of local address codec: what SIP codec is preferred for this number
Example:
{
"dids": [
{
"id": 728070,
"number": "17806999999",
"sms_enabled": false,
"no_local_cli": false,
"channels": 4,
"country": "Canada",
"area": "Edmonton, AB",
"free_minutes": 0,
"codec": "G711",
"require_docs": "",
"activation": 1.0,
"monthly_fee": 1.0,
"per_minute": 0.01,
"origination_per_min": 0.0
}
]
}Inputs: number (required).
update_sip_accountC
Creates a SIP account
Args: name: SIP account name password: Password to be used for this SIP account callerid: CallerID associated with this SIP account label: label fot this SIP account rewrite_enabled: do SIP account have calling number rewriting rule rewrite_cond: prefix to be rewrited (ex: 00) rewrite_prefix: prefix to what should be rewritten (ex: 44) didinfo_enabled: do DIDLogic will attempt send DID number as TO when receiving calls to this account ip_restrict: do we need to allowlist IP addresses for this account call_restrict: flag indicates what SIP account should have maximum call time call_limit: maximum call duration in seconds channels_restrict: flag indicates what SIP account should have maximum channels limit max_channels: maximum sip channels cost_limit: flag indicates what SIP account should have maximum call cost max_call_cost: maximum call cost for this SIP account
Returns a JSON object with SIP account details where: id: ID of SIP account name: SIP account name (login) callerid: CallerID associated with this SIP account label: label fot this SIP account charge: charge for calls on this month talk_time: total talk time for this month rewrite_enabled: do SIP account have calling number rewriting rule rewrite_cond: prefix to be rewrited (ex: 00) rewrite_prefix: prefix to what should be rewritten (ex: 44) didinfo_enabled: do DIDLogic will attempt send DID number as TO when receiving calls to this account ip_restrict: do we need to allowlist IP addresses for this account allowed_ips: IP addresses allowed for this SIP account call_restrict: flag indicates what SIP account should have maximum call time call_limit: maximum call duration in seconds channels_restrict: flag indicates what SIP account should have maximum channels limit max_channels: maximum sip channels cost_limit: flag indicates what SIP account should have maximum call cost max_call_cost: maximum call cost for this SIP account created_at: date of creation this SIP account
Example:
{
"sipaccount": {
"id": 61,
"name": "12345",
"callerid": "17254999999",
"label": "TEST DEVICE",
"host": "dynamic",
"charge": "0.0",
"talk_time": 0,
"rewrite_enabled": false,
"rewrite_cond": "8",
"rewrite_prefix": "7",
"didinfo_enabled": false,
"ip_restrict": false,
"call_restrict": true,
"call_limit": 2800,
"channels_restrict": false,
"max_channels": 1,
"cost_limit": false,
"max_call_cost": "5.0",
"created_at": "2024-06-03 06:06:47 UTC",
"allowed_ips": ["1.2.3.4", "3.4.5.6"]
}
}Inputs: name (required), call_limit, call_restrict, callerid, +11 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 22 tools
The tools are mostly distinct in their target resources (DIDs, SIP accounts, destinations, countries). However, 'get_sip_account' vs 'list_sip_accounts' and 'create_sip_account' vs 'update_sip_account' could be confused since both have similar parameter sets. The 'list_country_cities' and 'list_country_cities_in_region' are clearly separate but their descriptions are similar, requiring careful reading to distinguish.
Most tools follow a consistent 'verb_noun' pattern (e.g., list_countries, get_sip_account, remove_purchased_did). There are minor deviations: 'get_allowed_ips' vs 'add_allowed_ip' and 'delete_allowed_ip' are consistent, but 'list_dids_in_country_city' is a bit long and awkward. Overall, the naming is predictable and readable.
With 22 tools, the count is slightly high but still within a reasonable range for a comprehensive DID management server. The tools cover multiple domains (DID purchase, SIP accounts, destinations, transactions), so the count is justified. It does not feel bloated, but it is on the heavier side.
The tool surface covers the primary lifecycle for DIDs (list, purchase, remove), SIP accounts (create, get, update, delete), destinations (list, add, delete), and transactions. There are minor gaps: no direct 'update_did' or 'change_did_forwarding' tool, but these are handled through destination management. Also, there is no 'get_purchase' by ID, but list_purchases covers the need. Overall, the domain is well-covered.
Maintenance
Related MCP Connectors
Model Context Protocol server for the Apideck Unified API. Connect any MCP-compatible agent framework to 100+ accounting systems, HRIS platforms, file storage providers, and more through one integration. More information https://www.apideck.com/mcp-server
An MCP server that provides an API to LLMs to manage their JumpCloud resources.
A Model Context Protocol server for Wix AI tools
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
Related MCP Servers
- AlicenseBqualityDmaintenanceAn educational implementation of a Model Context Protocol server that demonstrates how to build a functional MCP server for integrating with various LLM clients like Claude Desktop.1162MIT
- AlicenseNot gradedqualityDmaintenanceAn implementation of the Model Context Protocol (MCP) server that exposes Twilio APIs to AI assistants and tools, allowing them to interact with Twilio services through the MCP protocol.114MIT
- AlicenseBqualityDmaintenanceAn educational implementation of a Model Context Protocol server that demonstrates how to build a functional MCP server integrating with various LLM clients.2MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server that supports STDIO, SSE and Streamable HTTP protocols for AI model interactions.1MIT