```
7. **Gauzy API** returns projects data
8. **MCP Server** formats response:
```json
{
"jsonrpc": "2.0",
"id": 1,
"result": {
"content": [
{
"type": "text",
"text": "Found 5 active projects:\n1. Mobile App (Due: 2025-03-15)\n..."
}
]
}
}
```
9. **Session Updated** in Redis: `lastActivity` โ current timestamp
10. **AI Assistant** receives formatted response and presents to user
---
## ๐ Connecting to the Remote MCP Server {#-connecting-to-the-remote-mcp-server}
### Connection Methods {#connection-methods}
The production Gauzy MCP server supports three connection methods to accommodate different use cases:
#### 1. Claude Desktop Integration (Stdio via NPM) {#1-claude-desktop-integration-stdio-via-npm}
The easiest way to connect Claude Desktop to the remote Gauzy MCP Server:
**Configuration** (`~/.claude_desktop_config.json`):
```json
{
"mcpServers": {
"gauzy": {
"command": "npx",
"args": ["-y", "@gauzy/mcp-server"],
"env": {
"API_BASE_URL": "https://api.gauzy.co",
"GAUZY_AUTH_EMAIL": "your-email@example.com",
"GAUZY_AUTH_PASSWORD": "your-password"
}
}
}
}
```
**How it works:**
- NPX downloads and runs the latest `@gauzy/mcp-server` package
- Package connects to your Gauzy API endpoint
- Authenticates with your credentials
- Establishes stdio communication with Claude Desktop
- Automatically manages tokens and sessions
**Demo Environment:**
```json
{
"mcpServers": {
"gauzy-demo": {
"command": "npx",
"args": ["-y", "@gauzy/mcp-server"],
"env": {
"API_BASE_URL": "https://apidemo.gauzy.co",
"GAUZY_AUTH_EMAIL": "demo@gauzy.co",
"GAUZY_AUTH_PASSWORD": "demo123"
}
}
}
}
```
#### 2. HTTP/REST API Integration {#2-httprest-api-integration}
For web applications, mobile apps, or any HTTP client:
**Endpoint**: `https://mcp.gauzy.co/sse`
**Example - List Available Tools:**
```bash
curl -X POST https://mcp.gauzy.co/sse \
-H "Content-Type: application/json" \
-H "Authorization: Bearer YOUR_OAUTH_TOKEN" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/list",
"params": {}
}'
```
**Example - Execute Tool:**
```bash
curl -X POST https://mcp.gauzy.co/sse \
-H "Content-Type: application/json" \
-H "Authorization: Bearer YOUR_OAUTH_TOKEN" \
-d '{
"jsonrpc": "2.0",
"id": 2,
"method": "tools/call",
"params": {
"name": "list_projects",
"arguments": {
"filter": { "active": true }
}
}
}'
```
**Available Endpoints:**
- `POST /sse` - MCP JSON-RPC 2.0 requests
- `GET /sse/events` - Server-Sent Events stream
- `GET /health` - Health check
- `GET /.well-known/oauth-protected-resource` - OAuth metadata
**Features:**
- JSON-RPC 2.0 over HTTPS
- OAuth 2.0 Bearer token authentication
- CORS-enabled for web applications
- Session cookies for state management
- Rate limiting: 100 requests per 15 minutes
#### 3. WebSocket Real-Time Connection {#3-websocket-real-time-connection}
For real-time bidirectional communication:
**Endpoint**: `wss://mcp.gauzy.co/sse`
**Example with wscat:**
```bash
# Install wscat
npm install -g wscat
# Connect to WebSocket server
wscat -c wss://mcp.gauzy.co/sse \
-H "Authorization: Bearer YOUR_OAUTH_TOKEN"
# Send initialization
{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"my-client","version":"1.0.0"}}}
# List tools
{"jsonrpc":"2.0","id":2,"method":"tools/list","params":{}}
# Execute tool
{"jsonrpc":"2.0","id":3,"method":"tools/call","params":{"name":"list_projects","arguments":{}}}
```
**Features:**
- Persistent connection with automatic reconnection
- Compression enabled (per-message deflate)
- 16MB max payload size
- Server-initiated notifications
- Sub-second latency
- Perfect for dashboards and live monitoring
---
## ๐ OAuth 2.0 Authentication {#-oauth-20-authentication}
For HTTP and WebSocket connections, the remote MCP server requires OAuth 2.0 Bearer tokens.
### Get an Access Token {#get-an-access-token}
#### Step 1: Discover OAuth Metadata {#step-1-discover-oauth-metadata}
```bash
curl https://mcpauth.gauzy.co/.well-known/oauth-authorization-server
```
Response includes:
- `authorization_endpoint` - Where to send users for authorization
- `token_endpoint` - Where to exchange codes for tokens
- `introspection_endpoint` - Token validation
- `jwks_uri` - Public keys for JWT verification
- `grant_types_supported` - Available OAuth flows
- `scopes_supported` - Available permission scopes
#### Step 2: Register OAuth Client {#step-2-register-oauth-client}
```bash
curl -X POST https://mcpauth.gauzy.co/oauth2/register \
-H "Content-Type: application/json" \
-d '{
"client_name": "My Application",
"redirect_uris": ["https://myapp.com/callback"],
"grant_types": ["authorization_code", "refresh_token"],
"response_types": ["code"],
"scope": "mcp.read mcp.write",
"token_endpoint_auth_method": "none"
}'
```
Response:
```json
{
"client_id": "client_abc123xyz",
"client_name": "My Application",
"redirect_uris": ["https://myapp.com/callback"],
"grant_types": ["authorization_code", "refresh_token"],
"response_types": ["code"],
"scope": "mcp.read mcp.write"
}
```
#### Step 3: Authorization Code Flow (with PKCE) {#step-3-authorization-code-flow-with-pkce}
**Generate PKCE verifier and challenge:**
```javascript
// Generate code verifier (43-128 characters)
const codeVerifier = generateRandomString(128);
// Generate code challenge (SHA256 hash, base64url encoded)
const codeChallenge = base64urlEncode(sha256(codeVerifier));
```
**Redirect user to authorization endpoint:**
```
https://mcpauth.gauzy.co/oauth2/authorize?
response_type=code&
client_id=client_abc123xyz&
redirect_uri=https://myapp.com/callback&
scope=mcp.read%20mcp.write&
state=random_state_string&
code_challenge=CODE_CHALLENGE_HERE&
code_challenge_method=S256
```
**User authenticates** with Gauzy credentials and grants permission.
**Receive authorization code** at your redirect URI:
```
https://myapp.com/callback?code=auth_code_here&state=random_state_string
```
#### Step 4: Exchange Code for Token {#step-4-exchange-code-for-token}
```bash
curl -X POST https://mcpauth.gauzy.co/oauth2/token \
-H "Content-Type: application/x-www-form-urlencoded" \
-d "grant_type=authorization_code" \
-d "code=auth_code_here" \
-d "redirect_uri=https://myapp.com/callback" \
-d "client_id=client_abc123xyz" \
-d "code_verifier=CODE_VERIFIER_HERE"
```
Response:
```json
{
"access_token": "eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCJ9...",
"token_type": "Bearer",
"expires_in": 900,
"refresh_token": "eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCJ9...",
"scope": "mcp.read mcp.write"
}
```
#### Step 5: Use Access Token {#step-5-use-access-token}
```bash
curl -X POST https://mcp.gauzy.co/sse \
-H "Authorization: Bearer eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCJ9..." \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/list",
"params": {}
}'
```
#### Step 6: Refresh Token (when expired) {#step-6-refresh-token-when-expired}
```bash
curl -X POST https://mcpauth.gauzy.co/oauth2/token \
-H "Content-Type: application/x-www-form-urlencoded" \
-d "grant_type=refresh_token" \
-d "refresh_token=eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCJ9..." \
-d "client_id=client_abc123xyz"
```
### OAuth Scopes {#oauth-scopes}
The remote MCP server supports the following scopes:
| Scope | Description | Tools Enabled |
| ----------- | --------------------- | ------------------------------------------------- |
| `mcp.read` | Read-only access | All GET/list operations (150+ tools) |
| `mcp.write` | Write access | All POST/PUT/PATCH/DELETE operations (173+ tools) |
| `mcp.admin` | Administrative access | All tools including admin operations (323 tools) |
**Recommended:** Request `mcp.read mcp.write` for full functionality.
### Token Validation {#token-validation}
**Introspect Token:**
```bash
curl -X POST https://mcpauth.gauzy.co/oauth2/introspect \
-H "Content-Type: application/x-www-form-urlencoded" \
-d "token=YOUR_ACCESS_TOKEN"
```
Response:
```json
{
"active": true,
"scope": "mcp.read mcp.write",
"client_id": "client_abc123xyz",
"username": "user@example.com",
"token_type": "Bearer",
"exp": 1735654800,
"iat": 1735654000,
"sub": "user-id-123",
"aud": "https://mcp.gauzy.co/sse"
}
```
**Verify JWT Signature:**
```bash
# Get public keys
curl https://mcpauth.gauzy.co/.well-known/jwks.json
# Use keys to verify JWT signature locally
# Libraries: jsonwebtoken (Node.js), PyJWT (Python), etc.
```
---
## ๐ Complete Tool Reference {#-complete-tool-reference}
The remote Gauzy MCP server exposes **323 production-ready tools** organized into **22 categories**. All tools are available via the `tools/list` method.
### Tool Discovery {#tool-discovery}
**List all available tools:**
```bash
curl -X POST https://mcp.gauzy.co/sse \
-H "Authorization: Bearer YOUR_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/list",
"params": {}
}'
```
**Get tool schema:**
Each tool includes:
- `name` - Tool identifier
- `description` - What the tool does
- `inputSchema` - JSON Schema for parameters (Zod-validated)
### Tool Categories Summary {#tool-categories-summary}
| Category | Tools | Key Capabilities |
| ------------------------- | ----- | --------------------------------------------------- |
| **Authentication** | 5 | Login, logout, token management, session handling |
| **Employee Management** | 15 | CRUD operations, bulk updates, statistics, profiles |
| **Task Management** | 16 | Task lifecycle, assignments, bulk ops, analytics |
| **Project Management** | 14 | Project CRUD, team assignments, reporting |
| **Daily Planning** | 17 | Personal/team plans, task integration, analytics |
| **Organization Contacts** | 17 | Contact management, bulk operations, assignments |
| **Time Tracking** | 3 | Start/stop timers, status monitoring |
| **Payments** | 14 | Payment processing, records, reporting |
| **Expenses** | 9 | Expense tracking, approval workflows |
| **Invoices** | 14 | Invoice generation, management, reporting |
| **Candidate Management** | 15 | Recruitment workflows, tracking, evaluations |
| **Sales & CRM** | 23 | Deals, pipelines, opportunity management |
| **Goal Management** | 24 | OKR system, objectives, key results |
| **Inventory & Equipment** | 21 | Asset tracking, warehouse management |
| **Product Management** | 18 | Product catalog, categories, organization |
| **Time Off** | 20 | Leave requests, PTO tracking, approvals |
| **Skills** | 10 | Competency tracking, development plans |
| **Merchants** | 14 | Vendor management, supplier relationships |
| **Income** | 13 | Revenue tracking, analysis, reporting |
| **Activity Logging** | 12 | Audit trails, user actions, events |
| **Communication** | 15 | Comments, discussions, collaboration |
| **Reporting** | 4 | Analytics, custom reports, insights |
| **HR & Awards** | 7 | Recognition programs, achievements |
**Total: 323 Tools**
### Example Tools {#example-tools}
**Project Management:**
- `list_projects` - Get all projects with filtering
- `create_project` - Create new project
- `update_project` - Update project details
- `delete_project` - Remove project
- `bulk_create_projects` - Create multiple projects
- `get_project_by_id` - Get specific project
- `get_my_team_projects` - Get team's projects
- `assign_project_to_employee` - Assign project
**Time Tracking:**
- `start_timer` - Start time tracking
- `stop_timer` - Stop active timer
- `timer_status` - Get current timer state
**Task Management:**
- `list_tasks` - Get all tasks with filters
- `create_task` - Create new task
- `bulk_create_tasks` - Create multiple tasks
- `update_task` - Update task details
- `delete_task` - Remove task
- `get_task_by_id` - Get specific task
- `get_my_tasks` - Get user's tasks
- `get_team_tasks` - Get team's tasks
**Employee Management:**
- `list_employees` - Get all employees
- `create_employee` - Add new employee
- `update_employee` - Update employee details
- `get_employee_by_id` - Get specific employee
- `get_employee_statistics` - Employee analytics
**Financial Operations:**
- `list_invoices` - Get all invoices
- `create_invoice` - Generate new invoice
- `list_payments` - Get payment records
- `create_payment` - Process payment
- `list_expenses` - Get expense records
- `create_expense` - Submit expense
---
## ๐จ Use Cases & Examples {#-use-cases--examples}
### Use Case 1: Project Setup Automation {#use-case-1-project-setup-automation}
**Scenario:** New client project needs setup with team, tasks, and time tracking.
**Natural Language Request:**
> "Set up a new project called 'Acme Corp Website' for Q1 2025, assign 3 developers and 1 designer, create 20 tasks from the requirements doc, and start tracking time."
**Behind the Scenes (Tools Used):**
1. `create_project` - Creates the project with timeline
2. `list_employees` - Finds team members by skills
3. `bulk_assign_project_to_employees` - Assigns team
4. `bulk_create_tasks` - Creates all tasks at once
5. `start_timer` - Begins time tracking
**Result:** Complete project setup in seconds instead of hours of manual work.
### Use Case 2: Weekly Team Report {#use-case-2-weekly-team-report}
**Scenario:** Manager needs weekly progress report for stakeholders.
**Natural Language Request:**
> "Generate a weekly report showing all completed tasks, time logged per project, and employees who worked overtime."
**Behind the Scenes (Tools Used):**
1. `list_tasks` - Filtered by date range and completed status
2. `get_time_logs` - Grouped by project
3. `list_employees` - With hours worked filter
4. `generate_report` - Formats data for presentation
**Result:** Comprehensive report ready for stakeholders in seconds.
### Use Case 3: Expense Processing {#use-case-3-expense-processing}
**Scenario:** Month-end expense approval and invoice generation.
**Natural Language Request:**
> "Show all pending expense claims for January, approve those under $500, and generate invoices for approved expenses."
**Behind the Scenes (Tools Used):**
1. `list_expenses` - Filtered by status and date
2. `bulk_update_expenses` - Batch approval
3. `bulk_create_invoices` - Generate invoices
4. `send_notifications` - Notify employees
**Result:** Month-end expense processing automated completely.
### Use Case 4: Recruitment Pipeline {#use-case-4-recruitment-pipeline}
**Scenario:** Hiring manager tracking multiple candidates through interview process.
**Natural Language Request:**
> "Show all candidates in 'Technical Interview' stage, schedule next round for top 3 candidates, and send rejection emails to others."
**Behind the Scenes (Tools Used):**
1. `list_candidates` - Filtered by stage
2. `get_candidate_evaluations` - Ranking data
3. `update_candidate_stage` - Move top candidates forward
4. `send_bulk_emails` - Automated communications
**Result:** Recruitment workflow streamlined with AI assistance.
### Use Case 5: Real-Time Dashboard {#use-case-5-real-time-dashboard}
**Scenario:** Operations dashboard showing live project metrics.
**Implementation:**
- WebSocket connection to `wss://mcp.gauzy.co/sse`
- Subscribe to real-time updates
- Tools called periodically: `get_active_timers`, `get_project_progress`, `get_team_availability`
- Dashboard updates automatically as data changes
**Result:** Live operational visibility without manual refreshes.
---
## ๐ป Self-Hosting & Development {#-self-hosting--development}
While we provide production-ready remote servers, you can also self-host the Gauzy MCP Server for development or on-premise deployments.
### Quick Reference {#quick-reference}
**Repository:** https://github.com/ever-co/ever-gauzy
**Package Locations:**
- MCP Server: `packages/mcp-server`
- MCP App (Stdio): `apps/mcp`
- Auth Server: `apps/mcp-auth`
**Build Commands:**
```bash
yarn build:mcp-server # Build MCP server package
yarn build:mcp # Build stdio app
yarn build:mcp-auth # Build auth server
```
**Documentation:**
For complete self-hosting instructions, environment variables, and configuration options, see the repository README:
- **Main README**: `README.md`
- **MCP Server Package**: `packages/mcp-server/README.md`
- **MCP App**: `apps/mcp/README.md`
- **Auth Server**: `apps/mcp-auth/README.md`
**Docker Images:**
```bash
docker pull gauzy/mcp-server:latest
docker pull gauzy/mcp-auth-server:latest
```
---
## ๐ง Troubleshooting {#-troubleshooting}
### Connection Issues {#connection-issues}
**Problem:** Cannot connect to remote MCP server
**Solutions:**
1. **Check server status**:
```bash
curl https://mcp.gauzy.co/health
```
Response should return `200 OK` with health status.
2. **Verify API endpoint**: Ensure `API_BASE_URL` points to correct Gauzy API
- Production: `https://api.gauzy.co`
- Demo: `https://apidemo.gauzy.co`
3. **Test credentials**: Verify login works through Gauzy web interface first
### Authentication Errors {#authentication-errors}
**Problem:** `401 Unauthorized` or authentication failures
**Solutions:**
1. **Verify credentials** are correct for the specified API endpoint
2. **Check account status**: Ensure account is active in Gauzy
3. **OAuth token expired**: Use refresh token to get new access token
4. **Check token scopes**: Ensure token has `mcp.read mcp.write` scopes
**Debug command:**
```bash
curl -X POST https://mcpauth.gauzy.co/oauth2/introspect \
-d "token=YOUR_TOKEN"
```
### Rate Limiting {#rate-limiting}
**Problem:** `429 Too Many Requests`
**Solutions:**
- Default limit: 100 requests per 15 minutes
- Wait for rate limit window to reset
- For higher limits, contact support for enterprise plan
- Check `X-RateLimit-Remaining` header in responses
### Tool Execution Errors {#tool-execution-errors}
**Problem:** Tool returns validation or execution errors
**Solutions:**
1. **Check tool schema**: Use `tools/list` to get correct parameter schema
2. **Validate parameters**: Ensure all required fields are provided
3. **Check permissions**: User may lack permissions for specific operations
4. **Review error message**: Provides specific field validation failures
Example:
```bash
# Get tool schema
curl -X POST https://mcp.gauzy.co/sse \
-H "Authorization: Bearer YOUR_TOKEN" \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
```
### Claude Desktop Integration Issues {#claude-desktop-integration-issues}
**Problem:** MCP server not showing in Claude Desktop
**Solutions:**
1. **Verify config location**: `~/.claude_desktop_config.json`
2. **Check JSON syntax**: Validate JSON is properly formatted
3. **Restart Claude Desktop**: Required after config changes
4. **Check logs**: Claude Desktop logs show MCP connection status
5. **Test NPM package**: `npx @gauzy/mcp-server --help`
### WebSocket Connection Failures {#websocket-connection-failures}
**Problem:** WebSocket disconnects or fails to connect
**Solutions:**
1. **Check firewall**: Ensure outbound WebSocket (WSS) connections allowed
2. **Verify endpoint**: Use `wss://mcp.gauzy.co/sse` (not `ws://`)
3. **Check Authorization header**: Must include valid Bearer token
4. **Network proxy**: Some corporate proxies block WebSocket connections
### Common Error Codes {#common-error-codes}
| Code | Meaning | Solution |
| ----- | ------------------- | ------------------------------------- |
| `401` | Unauthorized | Check token or credentials |
| `403` | Forbidden | User lacks permissions |
| `404` | Not Found | Verify endpoint URL or resource ID |
| `422` | Validation Error | Check parameter schema |
| `429` | Rate Limited | Wait or request higher limit |
| `500` | Server Error | Check server status, retry |
| `503` | Service Unavailable | Server maintenance, check status page |
### Getting Help {#getting-help}
- **Server Status**: https://status.gauzy.co
- **GitHub Issues**: https://github.com/ever-co/ever-gauzy/issues
- **Community Discord**: https://discord.gg/ever
- **Email Support**: support@ever.co
---
## ๐ Performance & Limits {#-performance--limits}
### Rate Limits {#rate-limits}
| Operation | Limit | Window |
| ----------------------- | ----- | ---------- |
| HTTP/WebSocket Requests | 100 | 15 minutes |
| OAuth Token Requests | 10 | 1 hour |
| Tool Executions | 100 | 15 minutes |
**Enterprise plans** available with higher limits and SLA.
### Request Limits {#request-limits}
- **Max payload size**: 1MB (production), 10MB (development)
- **Max WebSocket message**: 16MB
- **Session TTL**: 30 minutes (sliding window)
- **Token expiry**: 15 minutes (access), 7 days (refresh)
### Performance Metrics {#performance-metrics}
**Production Server Performance:**
- **Latency**: < 100ms (p50), < 500ms (p99)
- **Uptime**: 99.9% SLA
- **Throughput**: 10,000+ requests/second
- **Concurrent connections**: 50,000+ (WebSocket)
---
## ๐ API Versioning & Compatibility {#-api-versioning--compatibility}
### MCP Protocol Version {#mcp-protocol-version}
**Current**: `2025-06-18`
The Gauzy MCP Server fully implements the Model Context Protocol specification version 2025-06-18.
### API Versioning {#api-versioning}
The remote MCP server maintains backward compatibility:
- **Tool names**: Stable, no breaking changes
- **Parameters**: New optional parameters added, existing parameters unchanged
- **Responses**: New fields added, existing fields unchanged
### Breaking Changes Policy {#breaking-changes-policy}
- Announced 90 days in advance
- Deprecated features supported for 6 months
- Version parameter in requests (future enhancement)
### Changelog {#changelog}
See https://github.com/ever-co/ever-gauzy/releases for release notes and changelogs.
---
## ๐ Security & Compliance {#-security--compliance}
### Security Features {#security-features}
**Transport Layer:**
- TLS 1.3 encryption for all connections
- Perfect Forward Secrecy (PFS)
- HSTS headers enforced
- Certificate pinning support
**Authentication & Authorization:**
- OAuth 2.0 with PKCE (RFC 7636)
- JWT tokens with RS256/ES256 signatures
- Token introspection (RFC 7662)
- Automatic token rotation
- Scope-based access control
**Data Protection:**
- No storage of Gauzy passwords
- Tokens encrypted at rest (Redis)
- Session hijacking protection
- CSRF protection for state-changing operations
- XSS prevention with HTML escaping
**Audit & Monitoring:**
- Complete request/response logging
- User action tracking
- Failed authentication alerting
- Anomaly detection
- Compliance reporting
### Compliance {#compliance}
**Standards:**
- SOC 2 Type II (in progress)
- GDPR compliant
- CCPA compliant
- OAuth 2.0 (RFC 6749, 6750)
- OpenID Connect compatible
**Data Residency:**
- Production: US East (configurable)
- Data never leaves your specified region
- On-premise deployment available
---
## ๐ Enterprise Features {#-enterprise-features}
Contact us for enterprise features:
- **Higher Rate Limits**: Custom limits for high-volume usage
- **SLA Guarantees**: 99.99% uptime with credits
- **Priority Support**: 24/7 dedicated support team
- **Custom Deployment**: On-premise or private cloud
- **SSO Integration**: SAML 2.0, LDAP, Active Directory
- **Advanced Analytics**: Usage metrics and insights
- **Dedicated Infrastructure**: Isolated servers
- **Custom Integrations**: Tailored tool development
- **Training & Onboarding**: Team training sessions
**Contact**: enterprise@ever.co
---
## ๐ Additional Resources {#-additional-resources}
### Documentation {#documentation}
- **MCP Protocol Specification**: https://modelcontextprotocol.io
- **Gauzy Platform Docs**: https://docs.gauzy.co
- **API Documentation**: https://api.gauzy.co/docs
- **GitHub Repository**: https://github.com/ever-co/ever-gauzy
### Community & Support {#community--support}
- **Discord Community**: https://discord.gg/ever
- **GitHub Discussions**: https://github.com/ever-co/ever-gauzy/discussions
- **Stack Overflow**: Tag `gauzy`
- **Twitter**: @gauzyapp
### OAuth 2.0 Standards {#oauth-20-standards}
- **RFC 6749**: OAuth 2.0 Authorization Framework
- **RFC 6750**: OAuth 2.0 Bearer Token Usage
- **RFC 7591**: OAuth 2.0 Dynamic Client Registration
- **RFC 7662**: OAuth 2.0 Token Introspection
- **RFC 7636**: PKCE (Proof Key for Code Exchange)
- **RFC 8414**: OAuth 2.0 Authorization Server Metadata
- **RFC 9728**: OAuth 2.0 Protected Resource Metadata
---
## ๐ License {#-license}
The Gauzy MCP Server is part of the Gauzy Platform.
**License**: AGPLv3 with commercial licensing available
See https://github.com/ever-co/ever-gauzy/blob/develop/LICENSE for details.
For commercial licensing inquiries: licenses@ever.co
---
**Last Updated**: 2025-01-30
**MCP Protocol Version**: 2025-06-18
**Server Version**: Latest
**Production Status**: โ
Live
---
Built with โค๏ธ by Ever Co. LTD
Transform your business operations with AI-powered workspace management