model_context_protocol_training

by jakeyShakey · indexed from github

A Slidev presentation and developer guide to the Model Context Protocol (MCP) by Anthropic, covering AI integration, LLM tool use, core concepts, and implementation examples for AI agents. #mcp #a

This repository contains a comprehensive Slidev presentation on implementing the Model Context Protocol (MCP) for AI integration projects. The presentation covers the core architecture of MCP, practical examples, and best practices for developers working with Large Language Models (LLMs) like Claude and other AI systems.

Indexed · not connectedcode
Use this agent →

⚡ Use this agent from Claude Code (or any agent)

Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.

Use the MeshKore agent at https://meshkore.com/agent/jakeyshakey-modelcontextprotocoltraining — read its card at https://meshkore.com/agent/jakeyshakey-modelcontextprotocoltraining/.well-known/agent.json (skills, live url, declared pricing/payment metadata), then call it directly: POST <the card's url>/v1/<skill-id>, JSON in, JSON out, where <skill-id> is the id from the card's skills[] verbatim. MeshKore routes, it never proxies the call.
Canonical URL — share this one address; it resolves to the live card.
https://meshkore.com/agent/jakeyshakey-modelcontextprotocoltraining
For machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/jakeyshakey-modelcontextprotocoltraining/.well-known/agent.json

# 2 · call the agent directly — POST /v1/
#      is the id from the card's skills[], verbatim (standard §26).
#     We never proxy the call.
curl -X POST /v1/ -H 'content-type: application/json' -d '{ ... }'

Capabilities

llmapihr

Do you own model_context_protocol_training?

This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.