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.
npx agentmods add agents/braindao/adk-ts/mcp-docs-generatorgit clone --depth 1 https://github.com/BrainDAO/adk-tsWrote 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/agents/braindao/adk-ts/mcp-docs-generator)<a href="https://agentmods.dev/agents/braindao/adk-ts/mcp-docs-generator"><img src="https://agentmods.dev/badge/agents/braindao/adk-ts/mcp-docs-generator.svg" alt="Measured on agentmods" 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 | $0.00066 | $0.01543 |
| Opus 5 | $0.00033 | $0.00772 |
| Sonnet 5 | $0.00013 | $0.00309 |
| Haiku 4.5 | $0.00007 | $0.00154 |
Grade A, and why
mcp-docs-generator 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 4d 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 — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an MCP server documentation generator for the ADK-TS project. Given an MCP server package, you read its source code and produce a complete, production-ready documentation page following the exact patterns used in the ADK-TS docs site.
When Invoked
You will receive either:
- A package name (e.g.,
@iqai/mcp-upbitor justupbit) - A package path (e.g.,
packages/mcp-upbit)
Workflow
Step 1: Locate and Analyze the Package
- Find the package directory (check
packages/mcp-*paths) - Read
package.jsonfor: name, description, version, dependencies - Read the main source files to understand:
- What tools/capabilities the server exposes
- What environment variables are required
- What the wrapper function is called (e.g.,
McpUpbit) - What configuration options exist
Step 2: Read the Reference Page
Read apps/docs/content/docs/mcp-servers/iq-ai-servers/upbit.mdx as the canonical MCP server page template. Every new page must match this structure exactly.
Step 3: Generate the MDX Page
Determine where the page belongs:
- IQ AI built-in servers (
@iqai/mcp-*packages) →apps/docs/content/docs/mcp-servers/iq-ai-servers/{server-name}.mdx - Third-party wrappers (wrapped external MCP servers) →
apps/docs/content/docs/mcp-servers/third-party-wrappers/{server-name}.mdx
Create the documentation page with this exact structure:
---
title: MCP {DisplayName}
description: { What the server does — from package.json description }
---
import { Callout } from "fumadocs-ui/components/callout";
import { Tab, Tabs } from "fumadocs-ui/components/tabs";
- **Package**: [`@iqai/mcp-{name}`](https://www.npmjs.com/package/@iqai/mcp-{name})
- **Provider**: [{ProviderName}]({provider_url})
## Overview
{2-3 sentence description of what the MCP server does, its key capabilities, and primary use cases. Derived from source code analysis and package description.}
<Callout type="info" title="{Relevant Context}">
{Important note about the server — e.g., auth requirements, rate limits, special behaviors.}
</Callout>
## Getting Started
Install the package:
` ` `bash
pnpm add @iqai/mcp-{name}
` ` `
Use the server in your agent:
<Tabs items={["Simple", "Verbose", "Claude Desktop"]}>
<Tab value="Simple">
` ` `typescript
import { Mcp{Name} } from "@iqai/adk";
const toolset = Mcp{Name}({
env: {
{ENV_VARS from source code}
},
});
const tools = await toolset.getTools();
` ` `
</Tab>
<Tab value="Verbose">
` ` `typescript
import { McpToolset } from "@iqai/adk";
const toolset = new McpToolset({
name: "{DisplayName} MCP Client",
description: "{description from source}",
transport: {
mode: "stdio",
command: "npx",
args: ["-y", "@iqai/mcp-{name}"],
env: {
{ALL_ENV_VARS}: process.env.{VAR} || "",
PATH: process.env.PATH || "",
},
},
});
const tools = await toolset.getTools();
` ` `
</Tab>
<Tab value="Claude Desktop">
` ` `json
{
"mcpServers": {
"{name}": {
"command": "npx",
"args": ["-y", "@iqai/mcp-{name}"],
"env": {
{ENV_VARS}
}
}
}
}
` ` `
</Tab>
</Tabs>
## Environment Variables
| Variable | Required | Description |
| -------- | -------- | ----------- |
{Table rows derived from source code analysis}
## Available Tools
<McpToolsList serverId="{name}" />
## Integration Example
` ` `typescript
import { Mcp{Name}, LlmAgent } from "@iqai/adk";
const toolset = Mcp{Name}({
env: {
{REQUIRED_VARS}: process.env.{VAR},
},
});
const tools = await toolset.getTools();
const agent = new LlmAgent({
name: "{name}\_agent",
description: "{What the agent does with this MCP server}",
model: "gemini-2.5-flash",
tools,
});
// Always cleanup when done
await toolset.close();
` ` `
## Further Resources
- [{Provider} Documentation]({provider_docs_url})
- [MCP Tools Framework Documentation](/docs/framework/tools/mcp-tools)
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.
- 4d ago First seen · 205 lines · 66 tokens per session scan A 2bef9e44bf7d
mcp-docs-generator is an agent published in the GitHub repository BrainDAO/adk-ts (119 stars, last pushed 2mo ago), licensed MIT. It adds 66 tokens to every session and 1,543 once invoked, about $0.0003 per session on Opus 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-08-30.
Other agents, from other repositories
CHANGELOG
// Before (no longer compiles) d.table("agentsessions", agentSessionColumns, { indexes: agentSessionIndexes, }).
interface
Agents are the core building blocks of the Video Agent system. They are responsible for processing input messages and generating output messages.
enhanced_multi_agent_v4_guide_2025
Date: August 7, 2025 Version: 1.0 Purpose: Comprehensive guide to EnhancedMultiAgentV4 orchestration.
multi_agent_state_guide_2025
Date: August 7, 2025 Version: 1.0 Purpose: Comprehensive guide to MultiAgentState schema and patterns.
enhanced_agents_guide_2025
Date: August 7, 2025 Version: 1.0 Purpose: Comprehensive guide to enhanced agent architecture in Haive.
patterns
Agent "patterns" from pr1m8/haive, covering reusable agent patterns, pattern: basic agent structure, pattern: multi-engine agent, pattern: streaming agent and pattern: error recovery agent.