mymlh-mcp-server
Health Uyari
- No license — Repository has no license file
- Description — Repository has a description
- Active repo — Last push 0 days ago
- Low visibility — Only 9 GitHub stars
Code Uyari
- network request — Outbound network request in src/mymlh/api.ts
Permissions Gecti
- Permissions — No dangerous permissions requested
This tool is a Model Context Protocol (MCP) server designed to interface with the MyMLH API v4. It allows compatible AI models and LLM hosts to seamlessly query and interact with MyMLH services and user data.
Security Assessment
The server makes outbound network requests specifically within `src/mymlh/api.ts`, which is expected for an API integration tool. No hardcoded secrets were flagged, and the code does not request dangerous system permissions or execute arbitrary shell commands. However, because it handles MyMLH (Major League Hacking) data, it likely processes personally identifiable information (PII) such as user profiles and emails. Developers should ensure they handle this data securely and do not expose their own MyMLH API credentials. Overall risk: Medium.
Quality Assessment
The project appears to be actively maintained, with its last commit pushed just today. However, it suffers from low community visibility, currently sitting at only 9 GitHub stars, meaning it has not been extensively peer-reviewed. More importantly, the repository completely lacks a license file. Without an explicit open-source license, the software remains under exclusive copyright by default, which technically restricts how other developers can legally use, modify, or distribute it.
Verdict
Use with caution — the tool functions as expected without dangerous system exploits, but you should review the code internally and clarify the missing license before adopting it for production.
Model Context Protocol Server for MyMLH API v4
A Model Context Protocol (MCP) server that provides secure, OAuth-authenticated access to MyMLH. This server enables AI assistants and MCP clients to interact with the MyMLH API on behalf of users.
Features
- Secure Authentication: Implements MyMLH API v4 with OAuth for robust and secure user authentication.
- User Data Access: Provides tools to fetch a user's MyMLH profile, education, employment history, and more.
- Automatic Token Management: Handles token refresh and secure storage automatically.
- Cloudflare Workers: Built to run on the edge for low-latency, scalable performance.
- Easy Deployment: Can be deployed to your own Cloudflare account in minutes.
Quick Start
You can connect to our publicly hosted instance using any MCP client that supports the Streamable HTTP transport with OAuth.
Endpoint: https://mymlh-mcp.git.ci/mcp
Add MCP Server
Example configuration snippets for common MCP clients:
VS Code:
{
"servers": {
"mymlh": {
"type": "http",
"url": "https://mymlh-mcp.git.ci/mcp"
}
}
}
Cursor and many clients:
{
"mcpServers": {
"mymlh": {
"url": "https://mymlh-mcp.git.ci/mcp"
}
}
}
Windsurf and many clients:
{
"mcpServers": {
"mymlh": {
"serverUrl": "https://mymlh-mcp.git.ci/mcp"
}
}
}
Augment Code:
{
"mcpServers": {
"mymlh": {
"url": "https://mymlh-mcp.git.ci/mcp",
"type": "http"
}
}
}
Claude Code:
claude mcp add --transport http mymlh https://mymlh-mcp.git.ci/mcp
Gemini CLI:
Gemini currently only supports the deprecated SSE protocol.
{
"mcpServers": {
"mymlh": {
"url": "https://mymlh-mcp.git.ci/sse"
}
}
}
Roo Code, Cline, KiloCode:
Although these clients support Streamable HTTP transport, they do not yet support the OAuth authentication flow. Please use the fallback option below. See open feature requests for Roo Code, Cline.
For other clients, please consult their documentation for connecting to an MCP server. If you see 401 errors, the client likely does not support Streamable HTTP with OAuth and you will need to use the fallback option below.
Fallback Option
For environments where Streamable HTTP with OAuth is not supported, you may fall back to stdio transport with mcp-remote. This wraps the HTTP MCP server into a local stdio interface, forwarding requests over HTTP behind the scenes to ensure compatibility.
Example mcp-remote configuration snippet:
{
"mcpServers": {
"mymlh": {
"command": "npx",
"args": [
"mcp-remote",
"https://mymlh-mcp.git.ci/mcp"
]
}
}
}
See mcp-remote documentation for more details on usage.
Available Tools
Once connected and authenticated, you can use the following tools:
| Tool | Description |
|---|---|
mymlh_get_user |
Fetch current MyMLH user profile |
Test with MCP Inspector
You can test the remote MCP server using the Model Context Protocol Inspector.
- Run the Inspector from your terminal:
npx @modelcontextprotocol/inspector@latest - Enter the server URL:
https://mymlh-mcp.git.ci/mcpand click "Connect". - Follow the authentication flow to connect and test the tools.
Testing with Cloudflare AI Playground
You can also test the server directly using the Cloudflare Workers AI LLM Playground.
- Go to the playground link.
- Enter the server URL:
https://mymlh-mcp.git.ci/mcp - Follow the authentication flow to connect and test the tools.
Example Usage
You can interact with the MyMLH MCP server using natural language in your AI assistant:
- "Get my MyMLH user info."
- "Show me my MyMLH profile."
- "Generate a resume using my MyMLH profile."
- "Create a GitHub profile README using my MyMLH data."
Deploying Your Own Instance
For full control, you can deploy your own instance to Cloudflare. See the Deployment Guide for detailed instructions.
Contributing
We welcome contributions! Whether you're fixing a bug, adding a feature, or improving documentation, your help is appreciated.
For development setup, project structure, how to add tools, and contributing guidelines, see CONTRIBUTING.md.
License
Yorumlar (0)
Yorum birakmak icin giris yap.
Yorum birakSonuc bulunamadi