SkyStage MCP Test Server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@SkyStage MCP Test Serverping the server"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
SkyStage MCP Test Server
Minimal MCP server for testing SkyStage's self-auth auto-detection feature.
How auto-detection works
During deployment, SkyStage scans your source code. This server uses mcpAuthRouter
from the MCP SDK — SkyStage detects this and automatically deploys in self-auth mode:
✅ No Okta sidecar deployed
✅ All OAuth routes (
/.well-known/*,/authorize,/token) route to this container✅ Your app's OAuth popup appears when Claude Code first connects
Related MCP server: simple-mcp
Auth
Uses a mock OAuth provider that auto-approves every login — no credentials needed. Replace with a real provider (Atlassian, GitHub, etc.) in production.
Tools
Tool | Description |
| Returns |
| Echoes back any message |
| Returns server metadata and uptime |
| Reads from |
Deploy on SkyStage
Create → Host an MCP Server
GitHub Repo URL:
https://github.com/mediwareinc/skystage-mcp-test-serverContainer Port:
8080Optionally add a test secret: key
TEST_SECRET, valuehello-from-skystageDeploy — SkyStage auto-detects
mcpAuthRouter→ self-auth mode
Run locally
npm install
npm run devAdd to Claude Code:
claude mcp add --transport http --callback-port 9876 mcp-test http://localhost:8080/mcpThe mock OAuth popup auto-approves — no login screen needed.
Auth mode shown in catalog
After deployment, the Application Configuration card on the SkyStage entity page shows Auth: App-managed (custom OAuth) — confirming self-auth was auto-detected.
This server cannot be deployed
Maintenance
Related MCP Connectors
Minimal streamable HTTP MCP server used for owned-account registry connectivity tests.
MCP server for mandates, delegation, policy-gated execution, credential grants, and audit.
Experimental MCP server for current empirical verification of explicit public HTTPS endpoint claims.
- StytchOAuthdev.stytch.mcp
The Stytch MCP server is a reference implementation that demonstrates remote MCP server authentication and authorization using Stytch Connected Apps. It provides OAuth 2.1-compliant authorization (including PKCE), Dynamic Client Registration, and validates Stytch-issued access tokens to enable AI agents to securely interact with external services through permissioned access, supporting scopes like openid, email, profile, and manage:project_data.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceA simple MCP server with OAuth 2.0 authentication for testing OAuth support in mcp-cli.-
- FlicenseNot gradedqualityBmaintenanceA simple HTTP-based MCP server that provides demo tools (get_test_string, echo, check_maintenance), greeting prompts, and test resources, with optional OAuth 2.1 support.-
- FlicenseNot gradedqualityBmaintenanceMinimal MCP server for testing GitHub PR checks pipeline, with deterministic tools echo, add, and server_info.-
- AlicenseNot gradedqualityAmaintenanceA spec-compliant remote MCP server with built-in OAuth 2.1 and Dynamic Client Registration, enabling Notion Custom Agents to connect via 'Sign in with OAuth' without bearer tokens. It supports SSO federation to Google and Microsoft Entra, and includes basic tools like whoami, echo, and slow_task.MIT