Grigoriy Dobryakov

Expert MCP

Home
Live MCP server dobryakov-expert

Query my profile as an MCP server

I run a production MCP server that represents my professional profile. Connect it to your Claude and query my experience directly — a live demonstration of the systems I build.

Claude Codex Cursor Free
Connect Why use it

Why plug it in

A live way to explore my experience from inside your own agent — at your pace, grounded in the same public materials as this site.

  • Map my work to a specific question

    Point it at a role, a JD, or a technical problem and see which of my cases, patterns, and scale actually apply.

  • Dig into the cases

    Ask how a decision was made, what the trade-offs were, and how a pattern would transfer to a different landscape.

  • See how I reason

    Watch how the profile frames questions, cites examples, and flags risks — the same way I'd think through a real problem.

  • Wire it into your pipeline

    An outside angle on task phrasing, a ticket, or an architecture choice — as a tool your agents can call.

How to use it

  1. 1

    Pick a strong model in your client

    Quality comes from your LLM, not the MCP server. Details and model recommendation — in Good to know below.

  2. 2

    Connect the MCP in your agent

    One snippet in .mcp.json — see Connect. Works with Claude, Codex, and other MCP-capable clients.

  3. 3

    Ask in your own words

    In chat — about fit, a case, approach. In a pipeline — pass task context and ask what I'd say in your shoes. You can ask the agent to run screening-em or case-walkthrough.

  4. 4

    Reach out if it's useful

    Questions the profile can't answer, or want to talk to me directly? Reach me on LinkedIn or at grigoriydobryakov@gmail.com.

Connect

Console client — one command. Or a snippet in .mcp.json and restart the agent.

Console (Claude Code, Codex CLI)

claude mcp add --transport http dobryakov-expert https://mcp.dobryakov.net/mcp

.mcp.json file

"dobryakov-expert": {
  "type": "http",
  "url": "https://mcp.dobryakov.net/mcp"
}

After connecting, ask your agent: "use dobryakov-expert and answer…"

Example situations

Not documentation templates — real reasons people show up.

Matching experience to a scale-up context

"Which of Grigoriy's cases map to a PE-backed scale-up with an AI mandate?"

Understanding an approach to legacy

"How would Grigoriy approach AI transformation in an enterprise with legacy? What transfers from a large retailer with an event-driven landscape?"

Getting a view on a task in flow

"What would Grigoriy say about this Jira ticket?"

Hearing the reasoning behind a case

"Walk through the ML platform case — tens of millions of profiles — and explain how you'd reason about production at that scale."

What you can ask about

Answers draw on published materials — the same as on the website: products, cases, segments. No grey area, NDAs, or client internals; the agent pulls only the slice that fits your question.

Roles and products

Engineering Manager · AI Head of Engineering · AI Architect — when and why

Cases with numbers

Enterprise retail · ML platform · SaaS transition · integrator turnaround — context, actions, outcomes (as on the website)

Company types

AI-committed · Enterprise · Scale-up · Traditional — where my experience is closest

Methods and patterns

AI in SDLC · event-driven AI · governance and observability — how the approach holds up

Good to know

Answer quality comes from your LLM, not the server

MCP serves context and tools from the public corpus. Connecting facts, asking follow-ups, and wording the conclusion is the job of the model in your client. My server doesn't think for you and won't fix a weak model.

Cheap or weak models are a waste of time: they'll truncate context, skip tools, and average out the answer — then you'll decide "MCP doesn't work." Recommendation: at least Claude Opus with High effort (or an equivalent reasoning tier in your client).

  • This is a simulation from public materials, not a live conversation with me.
  • Your data does not reach the server and is not logged.
  • No secrets or unpublished content in the corpus — including client internals; only what's already public.

Reach me directly

The MCP server answers from public materials. For anything it can't cover — or just to talk — reach me directly.