Sipgate API MCP Server

Created By
BlackMaca year ago
MCP Server for the sipgate API
Overview

What is Sipgate API MCP Server?

Sipgate API MCP Server is an unofficial integration that allows AI assistants to interact with sipgate services, including SMS, calls, and account management, using the public sipgate API.

How to use Sipgate API MCP Server?

To use the Sipgate API MCP Server, you need to have a sipgate account and create a Personal Access Token. Then, you can install the server in various environments like Claude, VS Code, Cursor, and Cline by configuring the respective settings files with your token credentials.

Key features of Sipgate API MCP Server?

  • Access to sipgate services for SMS and calls
  • Account management capabilities
  • Integration with various development environments

Use cases of Sipgate API MCP Server?

  1. Sending SMS messages programmatically.
  2. Initiating phone calls through AI assistants.
  3. Managing sipgate account information and settings.

FAQ from Sipgate API MCP Server?

  • Is this project officially supported by sipgate?

No, this is an unofficial community project and is not affiliated with sipgate GmbH.

  • What do I need to get started?

You need a sipgate account and a Personal Access Token to use the API.

  • What programming environments are supported?

The server can be integrated with Claude, VS Code, Cursor, and Cline.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
BlackMac
Star
0
Language
JavaScript
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago
Crevio

2 days ago