forked from walkerpauldavid/oauth_mcp_server
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy path.env.example
More file actions
60 lines (53 loc) · 2.77 KB
/
.env.example
File metadata and controls
60 lines (53 loc) · 2.77 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
# =============================================================================
# OAuth MCP Server Configuration
# =============================================================================
# This server provides both OAuth 2.0 Device Code Flow and Client Credentials Flow
# Logging Configuration
LOG_LEVEL=INFO
LOG_FILE=oauth_mcp_server.log
# =============================================================================
# Azure OAuth2 Authentication Configuration
# =============================================================================
# Tenant and Client Configuration
TENANT_ID=your-tenant-id-here
CLIENT_ID=your-client-id-here
CLIENT_SECRET=your-client-secret-here
ACCESS_TOKEN_URL=https://login.microsoftonline.com/your-tenant-id-here/oauth2/v2.0/token
# OAuth2 Scope
OAUTH2_SCOPE=api://your-app-id/.default
# =============================================================================
# Authentication Method Configuration
# =============================================================================
# Options:
# - DEVICE_CODE: User delegated authentication via Device Code flow (RECOMMENDED)
# Automatic token acquisition is DISABLED - must pass bearer_token parameter
# Best for: Interactive use in Claude Desktop with user authentication
# Provides user-delegated permissions for API operations
#
# - CLIENT_CREDENTIALS: Automatic OAuth 2.0 Client Credentials flow (app-only, requires CLIENT_SECRET)
# Best for: Server-to-server automation, no user interaction required
# Note: Still accepts bearer_token parameter if provided
#
# Default: DEVICE_CODE (recommended for interactive use with Claude Desktop)
AUTH_METHOD=DEVICE_CODE
#AUTH_METHOD=CLIENT_CREDENTIALS
# ==============================================================================
# HOW TO USE DEVICE CODE AUTHENTICATION:
# ==============================================================================
# With AUTH_METHOD=DEVICE_CODE, all functions require bearer_token parameter.
# Token comes from conversation context - NO FILE STORAGE!
#
# Workflow:
# 1. Call start_device_auth() to get user code
# 2. Complete authentication at microsoft.com/devicelogin with the provided code
# 3. Call complete_device_auth() to retrieve the bearer token
# 4. Pass token to any function that needs authentication
#
# Example: Pass bearer_token="eyJ0..." as parameter to functions
#
# The bearer token stays in the conversation context throughout your session!
# =============================================================================
# API Endpoints (Optional - used by dependent services)
# =============================================================================
OMADA_BASE_URL=https://your-instance.omada.cloud
GRAPHQL_ENDPOINT_VERSION=3.0