What mymlh-mcp-server MCP server does
The mymlh-mcp-server MCP server gives AI assistants authenticated access to MyMLH account data. It connects to the MyMLH API v4 and acts on behalf of the signed-in user through OAuth. The available functionality is focused on retrieving the current user's profile rather than managing a broad set of MyMLH resources.
The returned profile can include information such as education and employment history, according to the data exposed by MyMLH. An assistant can use that information to answer profile-related questions or help create documents based on the user's own MyMLH record.
How it works
The public deployment is available at https://mymlh-mcp.git.ci/mcp. MCP clients connect to this endpoint using Streamable HTTP and complete the OAuth authentication flow before calling tools. After authentication, mymlh_get_user fetches the profile belonging to the authenticated MyMLH account.
Authentication and token handling are built into the server. The README states that token refresh and secure token storage are handled automatically, so clients do not need to implement those parts of the MyMLH OAuth flow themselves.
For testing, the endpoint can be opened in MCP Inspector or Cloudflare's Workers AI LLM Playground. Both workflows require connecting to the endpoint and completing authentication.
Setup and configuration
The simplest setup is to add the hosted HTTP endpoint to an MCP client. The configuration shape depends on the client: VS Code uses an HTTP server entry, while Cursor, Windsurf, Cline, and other clients use their respective MCP server configuration formats. Claude Code, Gemini CLI, and Codex CLI can add the endpoint from the command line.
If a client does not support Streamable HTTP with OAuth, configure mcp-remote as a local stdio bridge. It runs through npx, accepts the hosted MCP URL, and forwards requests to the remote server over HTTP.
A separate deployment guide is provided for operators who want to run their own instance on Cloudflare. The project is built for Cloudflare Workers and uses TypeScript and Hono, but the supplied material does not specify required deployment variables.
Tools and capabilities
The mymlh-mcp-server MCP server currently exposes one documented tool:
mymlh_get_user: retrieves the current authenticated MyMLH user's profile.
The profile data may include education, employment history, and other information available through the MyMLH API. Example assistant tasks include showing a user's MyMLH profile, generating a resume from that profile, or drafting a GitHub profile README from the user's data.
Limitations and notes
This server documents only one MCP tool, so it should not be selected when an application needs MyMLH write operations or access to resources beyond the current user's profile. Authentication is required before the tool can be used.
Clients must support Streamable HTTP with OAuth to connect directly to the hosted endpoint. A client that returns a 401 because it lacks that support may use the mcp-remote stdio fallback instead. The supplied documentation does not describe local environment variables or additional configuration options.