Profile

What profile MCP server does

The profile MCP server makes structured information about Jaroslav Kazejev available to MCP-compatible clients. Its source content covers a professional biography, technical and professional skills, projects and work, education, location, work status, current focus, public contact details, and profile links.

Responses are read-only. The server does not provide operations for editing, publishing, or deleting profile information. A separate kazejev://profile resource contains the same profile content as a single JSON document, so clients can retrieve the complete data through either the resource or the summary tool.

How it works

The hosted endpoint is https://mcp.kazejev.com/mcp. MCP clients send requests to that URL and receive structured tool results. The server supports both the modern protocol revision 2026-07-28 and the legacy revisions 2025-11-25, 2025-06-18, and 2025-03-26, selecting the protocol behavior for each request.

Modern requests are stateless and carry the protocol version, client identity, and capabilities in request metadata and HTTP headers. Older clients use the MCP initialization handshake. The endpoint also exposes server/discover for the modern protocol revision.

This design makes the profile MCP server suitable for clients that can connect to a remote HTTP MCP endpoint. It does not require a local process, runtime package installation, or credentials.

Setup and configuration

With Claude Code, add the remote server using the HTTP transport:

claude mcp add --transport http kazejev https://mcp.kazejev.com/mcp

Clients that accept JSON MCP configuration can use an entry with the server name kazejev, type http, and the endpoint URL above:

{
  "mcpServers": {
    "kazejev": {
      "type": "http",
      "url": "https://mcp.kazejev.com/mcp"
    }
  }
}

No authentication settings or environment variables are required. The README states that the server has no runtime dependencies.

Tools and capabilities

• get_profile_summary returns the full profile in one response, including the headline, location, work status, focus, strongest work, principal skills, education, and links.
• query_profile accepts a topic argument and returns matching projects, skills, and education with supporting detail.
• get_bio returns the short professional biography.
• list_skills returns the technical and professional skills.
• list_projects returns projects and work.
• get_contact_info returns public contact details and profile links.

Use the summary for a broad answer, the topic query for targeted research, and the narrower tools when an agent only needs one part of the profile.

Limitations and notes

The data is limited to the profile content supplied by the server. The tools are read-only and do not expose authenticated or private contact information; the contact tool returns public details and links. HTTP GET and DELETE requests return status 405 because the modern protocol no longer uses the GET stream or session teardown. Requests with conflicting protocol information in the body and headers are rejected, as are unsupported protocol versions and unknown methods.

Most clients still use the legacy protocol revisions, which is why both protocol eras remain available on the same endpoint. Client compatibility may therefore depend on whether the client supports remote HTTP MCP connections and one of the advertised protocol versions.