# BizCrush API and MCP

## BizCrush MCP

- Endpoint: https://extapi.bizcrush.ai/mcp
- Transport: Streamable HTTP (stateless)
- Authentication: OAuth 2.1 Authorization Code with S256 PKCE
- Connect the endpoint in an OAuth-capable MCP client. The browser opens https://bizcru.sh for normal BizCrush sign-in and consent.
- Do not ask the user to create, paste, or share an API key for OAuth.
- Static X-API-Key authentication is only a fallback for developer clients that securely support custom headers.
- OAuth metadata: https://extapi.bizcrush.ai/.well-known/oauth-authorization-server
- Guide: https://extapi.bizcrush.ai/developer/mcp

The MCP server provides 22 tools for meetings, transcripts, summaries, contacts, Slack delivery, and Notion upload.

## Standalone APIs

- POST /v1/translate-text — translate plain text into target_languages
- POST /v1/denoise — clean audio from a URL
- POST /v1/stt — file Speech-to-Text API
- WebSocket /v1/stt/stream — live Speech-to-Text API
- POST /v1/tts — protobuf text-to-speech returning a signed URL