Quickstart

1. Connect your client

You need an API token. The server uses Streamable HTTP on the same host as your dashboard and authenticates with the token in the Authorization header.

https://aipro.placetel.de/v1/mcp
Authorization: Bearer <your-api-token>

Claude Code
Claude (web and desktop)
Codex

claude mcp add --transport http voice-platform https://aipro.placetel.de/v1/mcp \
  --header "Authorization: Bearer <your-api-token>"

Check the connection with /mcp. Treat the local client configuration as confidential. Details: Claude Code MCP documentation.

Open connector settings and add a Custom Web Connector with the endpoint above. Choose No sign in and add a Request header: name Authorization, value Bearer <your-api-token>. Team and Enterprise accounts may require an administrator. A shared token grants access to its account; choose scopes accordingly. Details: Claude custom connectors.

Add the server to ~/.codex/config.toml and keep the token in an environment variable instead of the file:

[mcp_servers.voice-platform]
url = "https://aipro.placetel.de/v1/mcp"
bearer_token_env_var = "VOICE_PLATFORM_TOKEN"

Export VOICE_PLATFORM_TOKEN in the shell that starts Codex, then check the connection with codex mcp list or /mcp. Details: Codex MCP documentation.

2. Start with this prompt

Copy this into your client. It loads the two guides the assistant needs and keeps you in control of every change:

Read these two guides before you do anything else:
- Prompting guide: https://aipro.placetel.de/docs/de/ai-prompts.md
- Settings guide: https://aipro.placetel.de/docs/en/api-reference/voice-agent-settings.md

Then help me build a voice agent with the voice-platform MCP tools.
List my existing voice agents first. Before you create or change anything,
tell me what you plan to do and wait for my confirmation.

Then describe your phone assistant: who calls, what it should handle and how it should sound. Clients that support MCP prompts can load the same guides with prompting-guide and schema-guide instead; see Guides as MCP prompts.

3. Check the connection

The first request, “List my voice agents”, should call list_voice_agents. A successful tool response confirms access; saved connector settings alone do not.

Problem	Check
Unreachable endpoint or `404`	Check the full path and availability for your application address
`401`	Check the Bearer header, token, expiry and revocation
Missing tool or `403`	Check the token’s scopes and any IP restriction on it

Next: Build a voice agent.

Getting started

Build

Reference

1. Connect your client

2. Start with this prompt

3. Check the connection

​1. Connect your client

​2. Start with this prompt

​3. Check the connection

1. Connect your client

2. Start with this prompt

3. Check the connection