Dify 1.13 HTTP MCP Meeting Room Reservation Mockup

This project validates the meeting room reservation MCP using Dify 1.13's static Authorization header without an authentication server.

Dify 1.13 ── Bearer <고정 JWT> ──> MCP 서버 ── 내부 API 키 ──> 회의실 API

In the current scope, JWT's name=dify serves only as a fixed service identifier, not the actual user name. You must issue tokens directly in each environment and register the same token in both the Dify header and the MCP server's MCP_STATIC_TOKEN.

For detailed procedures, refer to the Static Token Integration Guide.

Provided Features

• Meeting room list lookup

• Meeting room reservation and time overlap prevention

• Reservation list lookup for the fixed service

• HTTP 401 on missing, mismatched, expired tokens, or missing name

• Returns dify님 예약이 완료되었습니다. on successful reservation

Related MCP server: Boma MCP

Quick Start

The Docker installation process is not covered in this document.

cp .env.example .env

docker compose run --rm --no-deps mcp-server \
  python scripts/mint_dev_token.py

Register the output JWT in .env.

MCP_STATIC_TOKEN=eyJ...

Run the server.

docker compose up -d --build --force-recreate
docker compose ps

Service addresses:

• MCP: http://localhost:8001/mcp

• Meeting room API status: http://localhost:8000/health

If Dify is on a different server, register an HTTPS URL accessible from Dify instead of localhost in both MCP_PUBLIC_URL and the Dify MCP settings.

Dify 1.13 Settings

Since this is a static header, the JWT and name=dify do not change even if the Dify user changes.

Key Files

Tests

PYTHONPATH=. uv run --isolated --extra test pytest -q

Docker E2E:

docker compose up -d --build --force-recreate
docker compose exec -T mcp-server python scripts/e2e_dify_legacy_client.py

Mockup Limitations

• JWT signatures are not verified against the authentication server's public key.

• Only one fixed token string in the MCP server's .env is allowed.

• User-specific identities cannot be distinguished.

• Reservation data is reset when the container is recreated.

• For production migration, an authentication server, signature verification, short expiration, key rotation, and per-user token delivery are required.