Dialogflow MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOST | No | Bind address of the remote server. | 0.0.0.0 |
| PORT | No | Bind port of the remote server. | 8000 |
| DB_POOL_MAX | No | Maximum psycopg pool size. | 5 |
| DB_POOL_MIN | No | Minimum psycopg pool size. | 0 |
| DF_AGENT_ID | No | Dialogflow CX agent id (CX server only). | |
| DF_LOCATION | No | Dialogflow region, e.g. europe-west2. | global |
| GCP_PROJECT | No | GCP project that hosts the Dialogflow agent. | |
| DATABASE_URL | No | Postgres connection string. Required by the remote server. The stdio servers fall back to postgresql://mcp:mcp_local_dev@127.0.0.1:5433/dialogflow_mcp when unset. | |
| DB_POOL_CHECK | No | Ping each pooled connection when it is handed out; 'on' or 'off'. | on |
| MCP_TRANSPORT | No | Remote transport: 'streamable-http' (/mcp) or 'sse' (/sse). | streamable-http |
| POSTGRES_PORT | No | Host port for the docker compose Postgres service (docker compose only). | 5433 |
| DF_ENVIRONMENT | No | Dialogflow ES environment name. | draft |
| MCP_AUTH_TOKEN | No | User Bearer token, at least 16 characters. Required by the remote server. | |
| DB_POOL_TIMEOUT | No | psycopg pool wait timeout in seconds. | 10 |
| MCP_ADMIN_TOKEN | No | Optional admin Bearer token, at least 16 characters and different from MCP_AUTH_TOKEN. Enables the admin tools for this token only. | |
| MCP_ADMIN_TOOLS | No | Register the admin tools. Defaults to 'on' for stdio and 'off' for remote. A blank value counts as unset; explicitly falsy together with MCP_ADMIN_TOKEN is a startup error. In remote mode only 1/true/yes/on mean on. | |
| MCP_ALLOWED_HOSTS | No | Extra allowed Host headers, comma-separated. Needed for a public remote hostname; otherwise requests get 421. Defaults to localhost only. | |
| POSTGRES_PASSWORD | No | Password for the docker compose Postgres service (docker compose only). | mcp_local_dev |
| MCP_ALLOWED_ORIGINS | No | Extra allowed Origin headers for browser clients, comma-separated. Defaults to localhost only; otherwise requests get 403. | |
| GOOGLE_APPLICATION_CREDENTIALS | No | Path to a service-account key file. Used when GOOGLE_APPLICATION_CREDENTIALS_JSON is not set; otherwise Application Default Credentials are used. | |
| GOOGLE_APPLICATION_CREDENTIALS_JSON | No | Service-account key content (JSON), for hosts without file mounts. Wins over GOOGLE_APPLICATION_CREDENTIALS. The remote server refuses to start if it is set but invalid. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| detect_intentA | Send a user message to the Dialogflow CX agent and return the agent's reply, matched intent, active page, and extracted parameters. Pass the returned session_id back on subsequent calls to maintain conversational context. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
There is only one tool, so there is no possibility of selecting the wrong one or confusing overlapping purposes. Its scope (send a message to a Dialogflow CX agent and receive a reply) is unambiguous.
The single name, detect_intent, follows a clean snake_case verb_noun convention with a clear domain term. With only one tool there is no broader pattern to confirm consistency against, which keeps it just short of a 5.
One tool is borderline thin for a server branded as a general Dialogflow MCP server, since nothing else about the platform is exposed. It is defensible if the intended scope is strictly runtime conversation, but it feels under-scoped for the name.
The single call covers the conversational turn, but there is no way to discover agents, manage sessions beyond passing a session_id back, or reset/end a conversation. An agent can only use this if the agent ID and session context are supplied entirely out of band, creating dead ends.