How to Use the DocBreach MCP in LangChain

Q: How does DocBreach prevent token bloat in LangChain chains?

The server uses docs.map to resolve the site layout first. Your LangChain agent then reads only the specific pages it needs via docs.read instead of dumping whole directories into the prompt context. This keeps your token payload small and predictable.

Q: What happens if a documentation site requires JavaScript rendering?

The docs.read tool extracts the underlying content directly from HTML, PDF, or Markdown files without running heavy browser engines. It parses the DOM structure directly inside the secure sandbox to output clean Markdown.

Feed clean, raw API specs directly into your LangChain reasoning loops without dealing with broken web scrapers.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect DocBreach MCP to LangChain

Create your Vinkius account to connect DocBreach to LangChain and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup DocBreach with LangChain

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Map API docs directly into your LangChain agent state

`docs.map` builds a complete index of any target domain's documentation structure before your agent starts guessing paths. Your agent reads this map to identify exactly which endpoints it needs to target, bypassing the usual trial-and-error approach. Once the map is in memory, the LangChain agent feeds these direct links into subsequent chain steps. This keeps your token usage low by avoiding massive, blind crawls of entire documentation sites.

Extract clean specs for multi-step reasoning chains

`docs.extract` parses OpenAPI, Swagger, or Postman collections to pull structured endpoint details without spinning up a headless browser. Your agent gets clean Markdown payloads containing only the specific API groups or tags relevant to the current chain step. This structural parsing happens inside the Vinkius MCP sandbox, stripping away heavy scripts and navigation junk. LangChain handles this clean string output directly, passing parsed specs to code-generation steps with zero formatting overhead.

Discover undocumented endpoints during active execution

`docs.discover` runs targeted queries to find external developer portals, API references, or setup guides on the fly. When a LangChain run hits an unknown service, the agent triggers this tool to fetch the exact URL it needs. The tool returns precise paths instead of generic search engine clutter. Your agent immediately feeds these discovered URLs into `docs.read` to keep the execution pipeline moving forward.

Setup guide

Set up DocBreach MCP in LangChain

Prerequisites

Python 3.10+ installed
langchain-mcp-adapters + langgraph packages
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install langchain-mcp-adapters langgraph langchain-openai. The MCP adapters package converts MCP tools into native LangChain BaseTool objects.
2

Connect via HTTP transport
Use MultiServerMCPClient with "transport": "http" pointing to your Vinkius endpoint. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com.
3

Create a ReAct agent
Pass the discovered tools to create_react_agent() from LangGraph. The agent automatically routes DocBreach tool calls through the MCP protocol.
4

Run with any LLM
Swap ChatOpenAI for ChatAnthropic, ChatGoogleGenerativeAI, or any LangChain-compatible model. The MCP tools work identically across all providers.

agent.py

from langchain_mcp_adapters.client import MultiServerMCPClient
from langgraph.prebuilt import create_react_agent
from langchain_openai import ChatOpenAI

async with MultiServerMCPClient({
    "docbreach-mcp": {
        "transport": "http",
        "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp",
    }
}) as client:
    tools = client.get_tools()

    agent = create_react_agent(
        ChatOpenAI(model="gpt-4o"),
        tools,
    )
    result = await agent.ainvoke({
        "messages": "List recent DocBreach transactions"
    })
    print(result["messages"][-1].content)

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by DocBreach. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect DocBreach now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about DocBreach MCP in LangChain

The server uses `docs.map` to resolve the site layout first. Your LangChain agent then reads only the specific pages it needs via `docs.read` instead of dumping whole directories into the prompt context. This keeps your token payload small and predictable.

Yes, every call made by this MCP server registers as a distinct tool run in your LangSmith dashboard. You get full visibility into the exact latency, input parameters, and raw Markdown payloads returned by tools like `docs.extract`.

Install the required adapter and configure the HTTP transport client with your Vinkius endpoint. Call `get_tools()` on the client and pass the resulting tool list directly to your LangChain agent constructor.

The `docs.read` tool extracts the underlying content directly from HTML, PDF, or Markdown files without running heavy browser engines. It parses the DOM structure directly inside the secure sandbox to output clean Markdown.

No, all fetched documentation data is processed in memory within your isolated Vinkius runtime. The server never logs or caches the API specs or target URLs your agent requests, keeping your proprietary documentation lookups completely private.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript