> ## Documentation Index
> Fetch the complete documentation index at: https://aipro.placetel.de/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Quickstart

> Connect Claude or Codex to the MCP server and start building a voice agent.

## 1. Connect your client

You need an [API token](https://aipro.placetel.de/docs/en/mcp/authentication.md). The server uses
**Streamable HTTP** on the same host as your dashboard and authenticates with
the token in the `Authorization` header.

```text theme={null}
https://aipro.placetel.de/v1/mcp
Authorization: Bearer <your-api-token>
```

> [tab] Claude Code
>
> ```bash theme={null}
> 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](https://code.claude.com/docs/en/mcp).

> [tab] Claude (web and desktop)
>
> 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](https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp).

> [tab] Codex
>
> Add the server to `~/.codex/config.toml` and keep the token in an environment
> variable instead of the file:
>
> ```toml theme={null}
> [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](https://developers.openai.com/codex/mcp).

## 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:

```text theme={null}
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](https://aipro.placetel.de/docs/en/mcp/guides.md).

## 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](https://aipro.placetel.de/docs/en/mcp/voice-agents.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.