MCP server configuration

Download the example configuration file

The MCP (Model Context Protocol) server connects AI assistants and agents to flip. The service is published on a separate domain (mcp.example.flip-chart.ru); clients are authorized via OAuth on the backend side.

The configuration file is mounted into the container at /flip/cfg/config.yaml.

Backend setup

McpAgentTokens.Enable: true must be set in the backend configuration. The flipApi.clientId value corresponds to the built-in OAuth client flip-mcp.

Configuration fields

server

• name: Server name reported to MCP clients.
  Example: flip-mcp-server
• version: Version reported to MCP clients.
  Example: "0.1.0"
• transport: Transport. Value: http.
• httpAddr: HTTP server address and port.
  Example: ":8090"

logLevel

• logLevel: Logging level: debug, info, warn, error.
  Example: info

flipApi

• serverUrl: External address of the application (without the /app path). Used in the OAuth metadata; must be reachable by MCP clients.
  Example: https://example.flip-chart.ru
• frontendUrl: External address of the flip interface.
  Example: https://example.flip-chart.ru
• clientId: ID of the OAuth client registered in the backend.
  Example: flip-mcp
• publicUrl: Public address of the MCP server.
  Example: https://mcp.example.flip-chart.ru
• internalUrl: Internal backend address for requests within the network. If not set, serverUrl is used.
  Example: http://flip-backend:9000

RedisClient (Valkey)

Important

The service must be connected to the same Valkey instance as the backend.

• Address: Valkey server address.
  Example: flip-valkey:6379
• Username: Username. Leave empty if ACLs are not used.
• Password: Password. Leave empty if not used.
• DB: Database number.
  Example: 0