DocBreach Connector for AI agents.
5 live capabilities
Get real-time API documentation and OpenAPI specs for your agent.
Waiting for input…
Why people use DocBreach
DocBreach API Documentation Discovery for Faster Development
DocBreach cuts out the middleman. Your agent just asks for the info, and the Connector grabs the clean Markdown for you. It handles the heavy lifting of parsing OpenAPI specs and Postman collections so you can get straight to writing code.
What Vinkius changes
That your agent gets instant, clean access to any API documentation without any manual setup or browser hurdles.
Use it from Claude, ChatGPT, Cursor or another AI client you already have.
One account · 5,900+ Connectors
- Real-world use case 01
Integrating a new SDK
An agent doesn't know how to use a new library.
- Real-world use case 02
Handling massive API specs
An OpenAPI file is too big to fit in a prompt.
- Real-world use case 03
Mapping out a competitor's API
You need to know the full scope of a service.
Complete set · 5capabilities
The complete DocBreach capability set.
These are the exact actions your AI can choose when you ask it to work with DocBreach.
01—03
3 capabilities in this set.
Part of 5 available through DocBreach.
- 01 Capability
Docs discover
Find the correct documentation links for any service or library using specific search queries. This helps your agent locate the right source material without you providing a URL.
- 02 Capability
Docs extract
Pull structured endpoint information from OpenAPI, Swagger, or Postman specification files. It turns complex specs into organized lists that are much easier for your agent to parse.
- 03 Capability
Docs map
Get a complete table of contents for any documentation domain by scanning its sitemap. This lets your agent see the full scope of a library before diving into specific pages.
04—05
2 capabilities in this set.
Part of 5 available through DocBreach.
- 04 Capability
Docs read
Convert URLs, OpenAPI specs, and Postman collections into clean Markdown for your agent. It removes the noise so your AI client can focus on the actual instructions.
- 05 Capability
Docs search
Search for specific technical topics or keywords within a known documentation domain. Use this to find specific details like rate limits or auth headers quickly.
Set up in minutes
One URL. Then ask DocBreach to work.
Claude and ChatGPT only need the Connector URL. Copy it once, add it in settings, and use DocBreach from the conversation.
Choose your client
Live previewAdvanced clients IDE · CLI
Claude · Web + desktop
Connector URL · ready to paste
Streamable HTTPhttps://edge.vinkius.com/vk_preview_irgtI6t1CMNMo7SoPiRQBNgk7Rz1GQFQBkyR1OUW/mcp - Step 01
Open Connectors
In Claude Web or Claude Desktop, open Settings and choose Connectors.
- Step 02
Add the URL
Choose Add custom connector, name it DocBreach, and paste the URL above.
- Step 03
Turn it on in chat
Select +, open Connectors, and enable DocBreach for the conversation.
ChatGPT · Web + desktop
Connector URL · ready to paste
Streamable HTTPhttps://edge.vinkius.com/vk_preview_irgtI6t1CMNMo7SoPiRQBNgk7Rz1GQFQBkyR1OUW/mcp - Step 01
Open MCP settings
On desktop, open Settings and MCP servers. On web, open your workspace app or connector settings.
- Step 02
Add the URL
Choose Add server with Streamable HTTP, or create a custom MCP app, then paste the DocBreach URL.
- Step 03
Save and start
Save the connection and enable DocBreach in your conversation. Desktop may ask you to restart once.
Cursor · IDE configuration
Advanced setup
{
"mcpServers": {
"docbreach": {
"url": "https://edge.vinkius.com/vk_preview_irgtI6t1CMNMo7SoPiRQBNgk7Rz1GQFQBkyR1OUW/mcp"
}
}
} - Step 01
Open MCP Settings
Press Cmd+Shift+P (macOS) or Ctrl+Shift+P (Windows/Linux) → search "MCP Settings"
- Step 02
Add the server config
Paste the JSON configuration above into the mcp.json file that opens
- Step 03
Save the file
Cursor will automatically detect the new Connector
- Step 04
Start using DocBreach
Open Agent mode in chat and ask: "Using DocBreach, help me...". 5 tools available
VS Code Copilot · IDE configuration
Advanced setup
{
"mcpServers": {
"docbreach": {
"url": "https://edge.vinkius.com/vk_preview_irgtI6t1CMNMo7SoPiRQBNgk7Rz1GQFQBkyR1OUW/mcp"
}
}
} - Step 01
Create MCP config
Create a .vscode/mcp.json file in your project root
- Step 02
Add the server config
Paste the JSON configuration above
- Step 03
Enable Agent mode
Open GitHub Copilot Chat and switch to Agent mode using the dropdown
- Step 04
Start using DocBreach
Ask Copilot: "Using DocBreach, help me...". 5 tools available
Windsurf · IDE configuration
Advanced setup
{
"mcpServers": {
"docbreach": {
"url": "https://edge.vinkius.com/vk_preview_irgtI6t1CMNMo7SoPiRQBNgk7Rz1GQFQBkyR1OUW/mcp"
}
}
} - Step 01
Open MCP Settings
Go to Settings → MCP Configuration or press Cmd+Shift+P and search "MCP"
- Step 02
Add the server
Paste the JSON configuration above into mcp_config.json
- Step 03
Save and reload
Windsurf will detect the new server automatically
- Step 04
Start using DocBreach
Open Cascade and ask: "Using DocBreach, help me...". 5 tools available
Cline · IDE configuration
Advanced setup
{
"mcpServers": {
"docbreach": {
"url": "https://edge.vinkius.com/vk_preview_irgtI6t1CMNMo7SoPiRQBNgk7Rz1GQFQBkyR1OUW/mcp"
}
}
} - Step 01
Open Cline MCP Settings
Click the Connectors icon in the Cline sidebar panel
- Step 02
Add remote server
Click "Add Connector" and paste the configuration above
- Step 03
Enable the server
Toggle the server switch to ON
- Step 04
Start using DocBreach
Ask Cline: "Using DocBreach, help me...". 5 tools available
Claude Code · Terminal command
Advanced setup
claude mcp add docbreach --transport http "https://edge.vinkius.com/vk_preview_irgtI6t1CMNMo7SoPiRQBNgk7Rz1GQFQBkyR1OUW/mcp" - Step 01
Install Claude Code
Run npm install -g @anthropic-ai/claude-code if not already installed
- Step 02
Add the Connector
Run the command above in your terminal
- Step 03
Verify the connection
Run claude mcp to list connected servers, or type /mcp inside a session
- Step 04
Start using DocBreach
Ask Claude: "Using DocBreach, show me...". 5 tools are ready
Where the request belongs
Work DocBreach can move forward.
Developers who are tired of copy-pasting API docs into prompts and AI engineers building agents that need to interact with external software.
Software Engineer
Uses it on a Tuesday afternoon to quickly grab the correct auth headers for a new library integration without leaving the IDE.
AI Agent Developer
Uses it to automatically map out a competitor's API for a research project or to build a capability that learns new SDKs on the fly.
Technical Writer
Uses it to verify if an API endpoint matches the published documentation by quickly extracting the spec.
Build the capability set
Add more capabilities.
Each Connector adds new actions and data without changing how you work.
Browse ConnectorsDevDocs
Search and read developer documentation via DevDocs.io. list libraries, find specific API pages, and retrieve Markdown docs directly from any AI agent.
Archbee
Manage documentation spaces, sync OpenAPI specs, and organize technical knowledge directly from your AI agent.
SwaggerHub
Connect your AI to SwaggerHub. Read OpenAPI specifications, explore domains, and manage your API design lifecycle natively from the terminal.
Apiary
Manage your API design-first workflows via Apiary. read blueprints, publish docs, and run tests directly from your AI agent.
Postman
Design, test, and document APIs collaboratively with the world most popular API development platform used by millions of developers.
Fern
Manage and interact with Fern documentation platforms. generate access tokens, index websites for AI, and query analytics directly from your agent.
Bring your own AI
Change the model, client or framework. Keep DocBreach connected.
-
Claude -
ChatGPT -
Gemini -
Cursor -
VS Code -
Windsurf -
ZCode -
Cline -
Zed -
Continue -
Kiro -
Roo Code -
Zencoder -
Goose -
Void -
Augment Code -
Amp -
Qodo -
Tabnine -
Pieces -
Sourcegraph Cody -
JetBrains -
Warp -
Amazon Q -
Antigravity -
BoltAI -
Raycast -
Jan -
LM Studio -
AnythingLLM -
Open WebUI -
Msty -
Cherry Studio -
LibreChat -
TypingMind -
Chorus -
5ire -
n8n -
LangChain -
LlamaIndex -
CrewAI -
Vercel AI SDK
Before you connect
Questions about DocBreach.
The practical details behind the request, access and result.
Can DocBreach find documentation for any API?
Yes, it can find documentation sources for any service, library, or API using specific search queries.
Does DocBreach work with Swagger files?
Yes, it can extract structured endpoint information from Swagger specs just like it does for OpenAPI.
Do I need to provide my own API keys for DocBreach?
No, DocBreach does not require any authentication or API keys to read documentation.
Can DocBreach read PDF documentation?
It can read PDFs as long as they are under 5MB in size.
How does DocBreach help my AI agent write better code?
It provides the agent with clean, LLM-ready Markdown instead of messy HTML. This helps the agent stay focused on the correct logic and reduces hallucinations.
Does DocBreach work with Postman collections?
Yes, it can parse Postman collections and convert them into clean Markdown for your agent to use.
Can I use DocBreach to map out a whole documentation site?
Yes, you can use it to scan sitemaps and get a complete table of contents for any domain.
How does DocBreach bypass modern Single Page Application (SPA) barriers?
DocBreach features a built-in hydration engine. Rather than relying on a heavy headless browser, it intercepts and evaluates underlying framework payloads (like __NEXT_DATA__ for Next.js or Docusaurus state) to extract the raw documentation text directly. This makes it blisteringly fast and resource-efficient.
What documentation formats and frameworks are officially supported?
It natively parses OpenAPI/Swagger specifications, Postman Collections, and standard llms.txt files. For web-based docs, it surgically cleans noise from 12+ major frameworks including Docusaurus, Nextra, VitePress, Mintlify, GitBook, and ReadMe, returning LLM-optimized Markdown.
Do I need any third-party API keys or paid scraping subscriptions?
Absolutely not. DocBreach is designed to operate completely independently. It accesses public documentation directly via optimized HTTP clients using smart resolution strategies, eliminating the need for proxy services, SaaS subscriptions, or scraping API keys.
How does this Connector improve my AI Agent's performance?
AI Agents typically hallucinate when APIs are updated or when facing undocumented endpoints. By equipping your agent with DocBreach, it can autonomously search, map, and read the definitive, up-to-date source of truth before writing a single line of code, ensuring deterministic integrations.
Can it extract specific endpoints from massive OpenAPI specifications?
Yes! The docs.extract capability is built precisely for this. Instead of loading a 5MB JSON spec into your agent's context window (which wastes tokens and ruins attention), DocBreach parses the spec server-side and allows your agent to query exactly the endpoints and methods it needs.
How does this MCP server improve my AI Agent's performance?
AI Agents typically hallucinate when APIs are updated or when facing undocumented endpoints. By equipping your agent with DocBreach, it can autonomously search, map, and read the definitive, up-to-date source of truth before writing a single line of code, ensuring deterministic integrations.
One connection away
Give your agent a direct line to DocBreach.
Connect DocBreach once. Keep it beside 5,900+ managed Connectors when the next task needs more.
Explore every Connector No credit card required · Free tier available