SSOJet MCP Server
OfficialClick on "Install 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., "@SSOJet MCP Serveradd 10 and 20"
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.
Model Context Protocol (MCP) Server (SSOJet)
This is a Model Context Protocol (MCP) server powered by SSOJet for authentication. Users must first sign in with SSOJet. Once authenticated, they can access and use secure tools such as the add tool exposed by this server.
Configuration
SSOJet Setup
Go to your SSOJet dashboard.
Create a new Single page web application.
Set the callback URL for local development:
http://localhost:8788/callbackNote the following details from your app:
Client ID
Client Secret
Issuer URL (e.g.
https://<your-tenant>.auth.ssojet.com/v1/)
These will be used to configure your server.
Set up a KV Namespace
This project uses a Cloudflare KV namespace to store token metadata:
wrangler kv:namespace create "OAUTH_KV"Then, add the KV binding to your wrangler.jsonc.
Environment Variables
The following environment variables must be configured to run the server:
Variable | Description |
| The Client ID from your SSOJet application |
| The Client Secret from your SSOJet application |
| The issuer URL (e.g. |
| Scopes to request (e.g. |
| Use |
| Not required in this case (unless your tool makes API calls externally) |
Development
Create a .dev.vars file in the root of your project:
SSOJET_CLIENT_ID=<your_ssojet_client_id>
SSOJET_CLIENT_SECRET=<your_ssojet_client_secret>
SSOJET_ISSUER=https://<your-tenant>.auth.ssojet.com/v1/
SSOJET_SCOPE="openid profile email"
NODE_ENV=developmentThen run the MCP server locally:
npm run devTool Available
The server currently provides a single tool:
Tool | Description |
| Adds two numbers together. Useful for simple math operations. |
Once the user signs in via SSOJet, this tool becomes accessible through compatible MCP clients such as the Workers AI LLM Playground.
Testing with MCP Inspector
You can test your server locally with MCP Inspector:
Set the Transport to
sseSet the URL to:
http://localhost:8788/sseA popup will appear for SSOJet authentication
Once logged in, you’ll see the available tools
Deploying to Cloudflare
Before deploying, set the necessary secrets in your Cloudflare environment:
wrangler secret put SSOJET_CLIENT_ID
wrangler secret put SSOJET_CLIENT_SECRET
wrangler secret put SSOJET_ISSUER
wrangler secret put SSOJET_SCOPEDeploy with:
npm run deployThen, in the SSOJet dashboard, add your deployed callback URL:
https://mcp-ssojet-oidc.<your-subdomain>.workers.dev/callbackTo use the deployed server with MCP Inspector or the LLM Playground, use this endpoint:
https://mcp-ssojet-oidc.<your-subdomain>.workers.dev/sseTroubleshooting
Cloudflare Worker Logs
You can inspect logs and errors using Cloudflare’s observability dashboard:
SSOJet Logs
Visit your SSOJet dashboard and check the Logs section to diagnose authentication issues.
Common Issues
❌ Invalid credentials: Double-check that secrets match your SSOJet application.
❌ Missing callback URL: Ensure all callback URLs are added in your SSOJet dashboard.
❌ Tool not showing: Make sure you're authenticated and using the correct endpoint.
❌ Local connection failed: Ensure the MCP server is running on
http://localhost:8788.
This server cannot be installed
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/ssojet/remote-mcp-ssojet'
If you have feedback or need assistance with the MCP directory API, please join our Discord server