Connect your AI app
There are two ways to connect. Use our hosted server from any AI app, or run the server on your own computer so your VoIP.ms credentials never leave it. Either way you sign in here, choose exactly what your assistant can access, and keep the same plan and daily cap.
Paste one URL into your AI app and sign in when it opens a browser. We hold your VoIP.ms API credentials, encrypted, so it works from web and mobile apps too.
Your MCP server URL
https://voipms-mcp.ecliptical.io/mcp- Your VoIP.ms credentials
- Encrypted on our server. You enter them once, in the dashboard.
- Works with
- Any MCP app, including web and mobile: Claude, ChatGPT, Cursor, VS Code, and more.
- VoIP.ms allowed IP
- Add our hostname, once.
- Runs on and updates
- Anything with a browser. Updates are automatic.
Want your VoIP.ms credentials to stay on your own computer? instead. Sign-in, scopes, plan, and daily cap are the same either way, and you can use both.
Install a small program on your Mac or PC and point a desktop AI app at it. Your VoIP.ms API credentials stay in your computer's secure store and never reach our servers.
Install
macOS
brew install ecliptical/voipms-mcp/voipms-mcpWindows
scoop install voipms-mcp- Your VoIP.ms credentials
- In your computer's secure store. You never enter them on this site.
- Works with
- Desktop apps that can start a program: Claude Desktop, Claude Code, ChatGPT desktop, Cursor, VS Code.
- VoIP.ms allowed IP
- Your own public address. A dynamic-DNS hostname makes it one-time if your ISP changes it.
- Runs on and updates
- macOS and Windows. Update with
brew upgradeorscoop update.
Need ChatGPT on the web, a phone, or another browser-only app? Use the instead. Sign-in, scopes, plan, and daily cap are the same either way, and you can use both.
What to expect on first connect
Sign in
Your AI app opens a browser to sign in. New here? You'll create an account in the same step.
Choose access
Review what the app is asking for and approve any subset — read-only or full, resource by resource.
Add your VoIP.ms credentials
Save your VoIP.ms API username and password once in the dashboard. They stay encrypted on the server and are never shared with the AI app.
Before you connect
This server acts on your own VoIP.ms account, so you need two things in place first. Both are set in the VoIP.ms API settings.
- A VoIP.ms account with API access enabled. Under API → Enable/Disable API, turn the API on and set an API password. That username and password are the credentials you save in the dashboard — not your portal login.
- Source-IP access for the server. Under API → Allowed IP Addresses, add
voipms-proxy.ecliptical.ioso the server can reach the API on your behalf. Keep any entries already there — this only adds ours.
See the full scope catalog for everything you can grant.
App setup
Pick your app. Each uses the same server URL above — substitute your own if you are reading this off a different deployment.
Claude Desktop
Claude Desktop connects to remote MCP servers as connectors.
- Open Settings → Connectors.
- Click Add custom connector.
- Give it a name (e.g. VoIP.ms) and paste the server URL:
https://voipms-mcp.ecliptical.io/mcp- Save, then click Connect — a browser opens to sign in and choose access.
- Once connected, the VoIP.ms tools appear in the connector list.
Claude Code
Add the server from the CLI as an HTTP transport:
claude mcp add --transport http voipms https://voipms-mcp.ecliptical.io/mcp- Run /mcp inside Claude Code and authenticate when prompted — a browser opens for sign-in and to choose access.
- After approval the VoIP.ms tools are available in the session.
ChatGPT
ChatGPT reaches remote MCP servers through connectors (developer mode / connectors, where available on your plan).
- In Settings → Connectors, choose to add a custom / remote MCP server.
- Paste the server URL:
https://voipms-mcp.ecliptical.io/mcp- Complete the sign-in and access prompts in the browser, then enable the connector in your chat.
Cursor
Add the server to Cursor's MCP config — ~/.cursor/mcp.json (global) or .cursor/mcp.json (per-project):
{
"mcpServers": {
"voipms": {
"url": "https://voipms-mcp.ecliptical.io/mcp"
}
}
}- Reload Cursor. Open Settings → MCP and sign in when prompted to authorize the connection.
Visual Studio Code
VS Code (Copilot agent mode) reads MCP servers from .vscode/mcp.json in your workspace:
{
"servers": {
"voipms": {
"type": "http",
"url": "https://voipms-mcp.ecliptical.io/mcp"
}
}
}- Save the file, then click Start on the server in the editor and sign in when prompted.
- The VoIP.ms tools become available to Copilot in agent mode.
Any other MCP client
Any client that supports a remote MCP server over the streamable HTTP transport with OAuth can connect. Configure it with:
- Transport: Streamable HTTP (POST). Server-Sent Events are not used.
- URL:
https://voipms-mcp.ecliptical.io/mcp - Auth: OAuth 2.1. The client discovers the authorization server automatically from the protected-resource metadata; no manual client registration is needed.
Set up in three commands
Sign in
voipms-mcp loginPrints a link and a short code. Open the link, sign in, and approve. New here? You create an account and choose a plan in the same step.
Store your VoIP.ms credentials
voipms-mcp set-credentialsAsks for your VoIP.ms API username and password and keeps them in your computer's secure store (Keychain on macOS, Credential Manager on Windows). Don't enter them in the dashboard; that form is for the hosted server.
Check it
voipms-mcp doctorChecks the login, the stored credentials, and whether VoIP.ms accepts a call from this machine. Run it whenever something stops working.
Before you connect on your device
This server acts on your own VoIP.ms account, so you need two things in place first. Both are set in the VoIP.ms API settings.
- A VoIP.ms account with API access enabled. Under API → Enable/Disable API, turn the API on and set an API password. That username and password are what you give
voipms-mcp set-credentials— not your portal login. - Source-IP access for your computer. Under API → Allowed IP Addresses, add your own public IP address. The field accepts a hostname, so if your ISP changes your address, a dynamic-DNS hostname makes this a one-time step. Keep any entries already there. If calls start failing,
voipms-mcp doctorreports the address VoIP.ms sees and whether it accepts a call from this machine.
See the full scope catalog for everything you can grant.
App setup on your device
Pick your app. Each starts voipms-mcp for you; there is nothing else to configure.
voipms-mcp: apps started from the Dock or Start menu don't always see your shell's PATH. Run which voipms-mcp (macOS) or where voipms-mcp (Windows) and paste the full path in place of the command.Claude Desktop
Claude Desktop starts local MCP servers from its config file. Open it with Settings → Developer → Edit Config and add:
{
"mcpServers": {
"voipms": {
"command": "voipms-mcp"
}
}
}- Save and restart Claude Desktop. The VoIP.ms tools appear under the tools menu.
- No sign-in prompt here: you already signed in with
voipms-mcp login.
Claude Code
Add the server from the CLI as a local command:
claude mcp add voipms -- voipms-mcp- The VoIP.ms tools are available in the next session. There is nothing to authorize: you already signed in with
voipms-mcp login.
ChatGPT (desktop app)
The ChatGPT desktop app starts local MCP servers through its Codex settings, shared with Codex CLI. ChatGPT on the web can't start a program on your computer; use the there.
- Open Settings → MCP servers → Add server.
- Name it voipms, choose STDIO, and enter the command
voipms-mcp. - Save, then Restart.
Or add it to ~/.codex/config.toml, which the desktop app, Codex CLI, and the IDE extension all read:
[mcp_servers.voipms]
command = "voipms-mcp"Cursor
In ~/.cursor/mcp.json (global) or .cursor/mcp.json (per-project):
{
"mcpServers": {
"voipms": { "command": "voipms-mcp" }
}
}- Reload Cursor. The VoIP.ms tools appear under Settings → MCP with no sign-in prompt.
Visual Studio Code
VS Code (Copilot agent mode) reads MCP servers from .vscode/mcp.json in your workspace:
{
"servers": {
"voipms": { "type": "stdio", "command": "voipms-mcp" }
}
}- Save the file, then click Start on the server in the editor.
- The VoIP.ms tools become available to Copilot in agent mode.
Any other MCP client
Any client that can start a local stdio MCP server can connect. Configure it with:
- Transport: stdio.
- Command:
voipms-mcp, with no arguments and no environment variables. - Auth: none. The client does no OAuth; you already signed in with
voipms-mcp login.
To disconnect this computer, run voipms-mcp logout. It revokes the sign-in here as well as removing it from your machine.