SkipCalls MCP server (legacy SSE)

Other

This is the legacy SSE transport variant of the SkipCalls connection, kept available for setups still wired to that endpoint. It provides the same underlying link into SkipCalls' AI phone receptionist for teams that haven't moved to the newer endpoint.

• Provides the legacy SSE transport path into SkipCalls
• Keeps older SkipCalls integrations working without a forced migration
• Connects agent workflows to the same underlying SkipCalls receptionist

What you can automate

SkipCalls MCP server (legacy SSE)

SkipCalls MCP server (legacy SSE) integration for connecting agents to SkipCalls MCP server (legacy SSE).

Real workflows

Keep an existing SSE setup running

If your SkipCalls integration is already wired to the legacy SSE endpoint, this connection keeps that path working while you decide whether and when to move to the standard endpoint.

Frequently asked questions

Should I use this or the standard SkipCalls connection?

Use this only if your setup specifically depends on the legacy SSE transport; otherwise the standard SkipCalls MCP server connection is the current path.

Does it do anything different from the standard connection?

No — it's the same SkipCalls receptionist integration, just reachable over the older SSE transport.