Keycard Hello MCP Server
An MCP server demonstrating OAuth 2.0 authentication with Keycard's Security Token Service, providing tools for displaying the Keycard logo and retrieving authenticated user information.
README
🔐 Keycard Hello MCP Server
A production-ready MCP server demonstrating OAuth 2.0 authentication with Keycard's Security Token Service (STS). This project showcases best practices for building secure, type-safe, and modular MCP servers with enterprise-grade observability.
🎯 What This Demonstrates
- 🔒 OAuth 2.0 Authentication - Secure authentication via Keycard STS
- ✨ Type Safety - Full TypeScript with Zod runtime validation
- 🏗️ Modular Architecture - Clean separation of concerns for easy extension
- 🚀 Production Ready - Error handling, validation, and comprehensive logging
- 📚 Educational - Well-documented code showing MCP best practices
- 🧪 Testing Framework - Jest with coverage, integration tests, and watch modes
- 📊 Observability - OpenTelemetry integration with traces and metrics
🚀 Quick Start
🏗️ Architecture
┌─────────────┐ ┌──────────────┐ ┌─────────────┐
│ Cursor │───▶│ MCP Server │───▶│ Keycard STS │
│ IDE │ │ (localhost: │ │ │
│ │ │ 8888) │ │ │
└─────────────┘ └──────────────┘ └─────────────┘
│ │ │
OAuth Flow JWT Validation Token Issuance
🔄 Authentication Flow
- Cursor discovers OAuth endpoints from MCP server
- User authenticates via Keycard STS (redirected to identity provider)
- Keycard STS issues JWT access tokens
- MCP Server validates tokens and grants access to tools
Prerequisites
- Node.js 18+ and npm
- Cursor IDE (or any MCP-compatible client)
- Keycard account with access to the Console
- Configured Keycard zone (for authentication)
1. Clone & Install
git clone https://github.com/keycardai/hello-mcp-server.git
cd hello-mcp-server
npm install
2. Configure Environment
Create a .env file:
# Required: Your Keycard STS issuer URL
KEYCARD_STS_ISSUER_URL=https://your-zone-id.keycard.cloud
# Optional: Server configuration
PORT=8888
HOST=localhost
💡 Finding your Zone ID:
- Log into the Keycard Console
- Navigate to Zone Settings
- Copy the Zone ID (e.g.,
j434uokph8th1ia1npxiaykh7p) - Replace
your-zone-idin your STS URL
Note: Use the zone ID, not the zone name or label.
3. Start the Server
# Development mode with auto-reload
npm run dev
# Production mode
npm run build && npm start
You should see:
🚀 Keycard Hello MCP Server started!
🔗 MCP Endpoint: http://localhost:8888/mcp
🔐 STS Issuer: https://your-zone-id.keycard.cloud
🛠️ Available Tools: keycard-logo, whoami
4. Configure Cursor IDE
Add to your Cursor MCP settings:
{
"mcpServers": {
"keycard-hello-mcp": {
"url": "http://localhost:8888/mcp"
}
}
}
5. Test Authentication
- Restart Cursor to pick up the new MCP server
- Cursor will show "needs login" for the server
- Click to authenticate → complete OAuth flow
- Use the tools:
keycard-logo,whoami
🛠️ Available Tools
keycard-logo
Displays the official Keycard ASCII art logo.
whoami
Provides detailed information about the authenticated user including:
- Client ID and authentication scopes
- JWT payload with user information
- Token expiration and timing details
- Custom claims and metadata
🔧 Configuration
Environment Variables
| Variable | Description | Default | Required |
|---|---|---|---|
KEYCARD_STS_ISSUER_URL |
Keycard STS issuer URL (single-tenant mode) | - | ✅* |
ISSUER_BASE_DOMAIN |
Base domain for STS (multi-tenant mode) | - | ✅* |
MCP_BASE_DOMAIN |
Base domain for MCP server (multi-tenant mode) | - | ✅* |
PORT |
Server port | 8888 |
|
HOST |
Server host | localhost |
|
LOG_LEVEL |
Logging level | INFO |
|
ENABLE_OTEL |
Enable OpenTelemetry | true |
|
OTEL_SERVICE_NAME |
Service name for telemetry | hello-mcp-server |
|
OTEL_ENVIRONMENT |
Environment for telemetry | development |
*Either KEYCARD_STS_ISSUER_URL (single-tenant) OR ISSUER_BASE_DOMAIN + MCP_BASE_DOMAIN (multi-tenant) is required.
Multi-Tenant Configuration
For multi-tenant deployments (serving multiple organizations/zones), use these environment variables instead:
# Multi-tenant mode
ISSUER_BASE_DOMAIN=keycard.cloud
MCP_BASE_DOMAIN=mcp.example.com
# Other configuration
PORT=8888
ENABLE_OTEL=true
This enables dynamic issuer discovery based on subdomain routing, allowing one deployment to serve multiple Keycard zones.
Observability
The server includes comprehensive observability features:
- Structured Logging: Environment-aware logging with trace correlation
- Request Tracing: Full distributed tracing with OpenTelemetry
- Metrics Collection: Performance and usage metrics
- Health Checks: Available at
/health
In development, logs are formatted for console readability. In production, logs are sent to configured OTLP endpoints.
🏗️ Architecture
src/
├── config.ts # Configuration management
├── index.ts # Application entry point
├── server.ts # Express server setup
├── middleware/ # Express middlewares
│ ├── auth.ts # Authentication middleware
│ └── logging.ts # Request logging and tracing
├── observability/ # Telemetry and logging
│ ├── logger.ts # Structured logger
│ └── telemetry.ts # OpenTelemetry setup
├── tools/ # MCP tools
│ ├── index.ts # Tool registration
│ ├── logo.ts # Keycard logo tool
│ └── whoami.ts # User information tool
└── types/ # Type definitions
├── auth.ts # Authentication types
└── index.ts # Exported types
🧪 Testing
# Run all tests
npm test
# Run tests with coverage
npm run test:coverage
# Run integration tests
npm run test:integration
# Watch mode for development
npm run test:watch
📊 Code Quality
# Lint code
npm run lint
# Fix linting issues
npm run lint:fix
# Format code
npm run format
# Check all (lint + format)
npm run check
# Fix all issues
npm run check:fix
🔗 MCP Integration
Cursor IDE
- Start the server:
npm run dev - In Cursor, go to Settings > MCP Servers
- Add server:
http://localhost:8888/mcp
🚦 Health Checks
The server provides a health check endpoint at /health:
curl http://localhost:8888/health
Response:
{
"status": "healthy",
"timestamp": "2024-01-01T00:00:00.000Z",
"service": "hello-mcp-server",
"version": "1.0.0"
}
🤝 Contributing
- Fork the repository
- Create a feature branch
- Make your changes
- Run tests and quality checks
- Submit a pull request
📄 License
Apache-2.0 License - see LICENSE file for details.
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。