Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/TheLobbi/claudeWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/thelobbi/claude/mcp)<a href="https://agentmods.dev/commands/thelobbi/claude/mcp"><img src="https://agentmods.dev/badge/commands/thelobbi/claude/mcp/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/thelobbi/claude/mcp"><img src="https://agentmods.dev/badge/commands/thelobbi/claude/mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00023 | $0.04583 |
| Opus 5.5 | $0.00009 | $0.01833 |
| Sonnet 5.5 | $0.00005 | $0.00917 |
| Haiku 4.5 | $0.00002 | $0.00458 |
Grade A, and why
lg:mcp scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 797 lines — stays where its author put it; the contents beside it link to each section on GitHub.
lg:mcp - Model Context Protocol Integration
Integrate LangGraph agents with MCP to expose agents as servers or consume external MCP tools.
Workflow Steps
Expose Agent as MCP Server
-
Validate Project
- Check project structure
- Verify agent is functional
- Validate configuration
-
Generate MCP Server Code
- Create server wrapper
- Define tool schemas
- Setup transport layer
- Configure authentication (if enabled)
-
Generate Tool Definitions
- Extract agent capabilities
- Create MCP tool schemas
- Document parameters
- Define return types
-
Setup Transport
- Configure stdio/SSE/WebSocket
- Setup request handling
- Configure streaming (if enabled)
- Add error handling
-
Generate Claude Config
- Create claude_desktop_config.json
- Add server configuration
- Document setup instructions
-
Create Tests
- Add MCP server tests
- Test tool invocation
- Test streaming (if enabled)
- Test error handling
-
Update Documentation
- Add MCP server docs
- Document available tools
- Add integration examples
Consume MCP Tools
-
Connect to MCP Server
- Load server configuration
- Establish connection
- Validate server availability
-
Discover Tools
- Query available tools
- Parse tool schemas
- Validate compatibility
-
Generate Tool Wrappers
- Create LangChain tool wrappers
- Map MCP schemas to LangChain
- Add type validation
-
Integrate with Agent
- Add tools to agent
- Update tool list
- Configure tool binding
-
Update Tests
- Add tool usage tests
- Test MCP connection
- Test tool execution
-
Update Documentation
- Document available MCP tools
- Add usage examples
MCP Server Patterns
Stdio Transport (Default)
Best for Claude Desktop integration.
# mcp_server.py
import asyncio
from mcp.server import Server
from mcp.server.stdio import stdio_server
from mcp.types import Tool, TextContent
from src.graph import app
# Create MCP server
server = Server("langgraph-agent")
@server.list_tools()
async def list_tools() -> list[Tool]:
"""List available tools."""
return [
Tool(
name="run_agent",
description="Run the LangGraph agent",
inputSchema={
"type": "object",
"properties": {
"message": {
"type": "string",
"description": "Input message"
},
"thread_id": {
"type": "string",
"description": "Thread ID for conversation"
}
},
"required": ["message"]
}
)
]
@server.call_tool()
async def call_tool(name: str, arguments: dict) -> list[TextContent]:
"""Execute tool."""
if name == "run_agent":
message = arguments["message"]
thread_id = arguments.get("thread_id", "default")
config = {"configurable": {"thread_id": thread_id}}
result = app.invoke({"messages": [message]}, config)
return [
TextContent(
type="text",
text=result["messages"][-1].content
)
]
raise ValueError(f"Unknown tool: {name}")
async def main():
"""Run MCP server."""
async with stdio_server() as (read_stream, write_stream):
await server.run(
read_stream,
write_stream,
server.create_initialization_options()
)
if __name__ == "__main__":
asyncio.run(main())
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 797 lines · 23 tokens per session scan A f0ef7cea0251
lg:mcp is a command published in the GitHub repository TheLobbi/claude (21 stars, last pushed 6d ago), licensed MIT. It adds 23 tokens to every session and 4,583 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-05.
Other commands, from other repositories
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
api-contract-review
Review an API contract (shapes, errors, auth model) BEFORE implementation for naming, versioning, pagination, idempotency, and fit with existing endpoints. Use when designing or changing endpoints. Do not use when the API is already implemented (use review-hard or repo-consistency-sweep).
build
Discover an AI Gateway's models and MCP tools, retrieve a credential, and integrate them into your app — call a model, connect MCP tools, or scaffold a runnable agent.
start-10-1
A guided lesson on setting up clasp, a command-line tool for managing Google Apps Script projects, and connecting it to Google’s Apps Script API.
fastapi
FastAPI application design and implementation conventions. Use this skill when building, updating, or reviewing FastAPI services, routers, dependencies, request/response schemas, streaming endpoints, or API tests. Trigger on FastAPI-specific work such as path operation design, dependency injection, response models…
dare-llm-integration
Integração segura e eficiente com LLMs (Gemini, Claude, OpenAI, Ollama) em projetos DARE.