Well MCP supports two authentication methods: API Key for simple setups and OAuth for production use.
API Key (Simple)
Best for: personal use, testing, development
How to Get an API Key
- Log into Well Dashboard
- Go to Settings > API Keys
- Click Generate New Key
- Copy the key immediately (it won’t be shown again)
Usage
Include the API key in the Authorization header:
Authorization: Bearer YOUR_API_KEY
Or set it as an environment variable for stdio transport:
WELL_API_KEY=your_api_key_here
Never commit API keys to version control. Use environment variables or secure secret management.
OAuth (Recommended)
Best for: production, multi-user, shared access
OAuth provides secure, token-based authentication with automatic refresh.
How It Works
Most MCP clients (Claude, Cursor, Windsurf, ChatGPT) support adding custom MCP servers with just a URL. Simply enter:
https://api.wellapp.ai/v1/mcp
The client handles everything automatically:
- Redirects you to Well’s authorization page
- You log in and authorize access
- Redirects back to your client with tokens
- Handles token refresh automatically
That’s it - no manual configuration required.
Which Should I Use?
| Use Case | Recommended |
|---|
| Personal testing | API Key |
| Development | API Key |
| Production app | OAuth |
| Multi-user access | OAuth |
| Shared workspaces | OAuth |
Start with an API key for testing, then switch to OAuth for production deployments.