About profile
profile is a read-only MCP server for Jaroslav Kazejev’s professional profile. It lets MCP clients retrieve his biography, skills, projects, education, and public contact links.
Key features
- 01Complete profile summary
- 02Topic-based profile queries
- 03Biography and skills lookup
- 04Project and education listings
- 05Public contact details
- 06Profile JSON resource
Use cases
- 01Answer questions about Jaroslav Kazejev’s background
- 02Find skills or projects related to a topic
- 03Retrieve public profile and contact links
MCP support
Exposes profile lookup tools and the `kazejev://profile` resource to MCP clients. The hosted endpoint supports modern and legacy protocol versions.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://mcp.kazejev.com/mcpclaude mcp add --transport http com-kazejev-profile https://mcp.kazejev.com/mcp{"mcpServers":{"com-kazejev-profile":{"type":"http","url":"https://mcp.kazejev.com/mcp"}}}Open in Cursor{"servers":{"com-kazejev-profile":{"type":"http","url":"https://mcp.kazejev.com/mcp"}}}Open in VS Code{"mcpServers":{"com-kazejev-profile":{"type":"http","url":"https://mcp.kazejev.com/mcp"}}}{"mcpServers":{"com-kazejev-profile":{"serverUrl":"https://mcp.kazejev.com/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
6This tool takes no parameters.
Details
From the project READMEprofile-mcp
An MCP server that answers questions about Jaroslav Kazejev: biography, skills, projects and education. It is read-only, it needs no authentication, and it has no runtime dependencies.
Endpoint: https://mcp.kazejev.com/mcp
Connect
With the Claude Code CLI:
claude mcp add --transport http kazejev https://mcp.kazejev.com/mcp
With a client that reads a JSON configuration:
{
"mcpServers": {
"kazejev": {
"type": "http",
"url": "https://mcp.kazejev.com/mcp"
}
}
}
Tools
| Tool | Arguments | Returns |
|---|---|---|
get_profile_summary | none | The complete profile in one response: headline, location, work status, focus, the strongest work, the main skills, education and links |
query_profile | topic | The projects, skills and education that match the topic, with the detail behind each one |
get_bio | none | The short professional biography |
list_skills | none | The technical and professional skills |
list_projects | none | The projects and the work |
get_contact_info | none | The public contact details and profile links |
One resource, kazejev://profile, holds the same content as one JSON
document.
Protocol support
The server answers two protocol eras on the same endpoint, and selects the era for each request.
| Era | Versions | Description |
|---|---|---|
| Modern | 2026-07-28 | The server keeps no state. Each request carries its version, identity and capabilities in _meta and in HTTP headers, which the server examines. server/discover is available. |
| Legacy | 2025-11-25, 2025-06-18, 2025-03-26 | The client and the server do the initialize handshake. |
The 2026-07-28 revision removed the initialize handshake and the
protocol-level sessions. Most clients still use the older revisions, thus the
server keeps both.
Notable behaviour in the modern era:
GETandDELETEreturn 405. The GET stream and the session teardown are no longer in the protocol.- A header that disagrees with the body returns 400 and
-32020. - An unsupported version returns 400 and
-32022with the supported list. - An unknown method returns 404 and
-32601.
Where else this server appears
- Registry entry:
com.kazejev/profilein the official MCP Registry - Server card: https://kazejev.com/.well-known/mcp/server-card.json
- Site: https://kazejev.com
Development and maintenance
See docs/maintenance.md.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.