Skip to content
Vinkius

DevDocs Connector for AI agents.

3 live capabilities

Get real-time API documentation and SDK references directly in your workspace.

Live agent request DevDocs / Connector

Waiting for input…

AI Agent

Why people use DevDocs

DevDocs for Accurate API Documentation Research

With this Connector, you just ask your agent to find the command for you. It queries the DevDocs registry, finds the right page, and pulls the Markdown right into your chat. You get the correct code immediately without the tab-switching headache.

  • Claude
  • ChatGPT
  • Gemini
  • Cursor
  • Visual Studio Code
  • Windsurf

What Vinkius changes

Your AI agent gets instant access to the latest technical manuals without you having to leave your workspace.

Use it from Claude, ChatGPT, Cursor or another AI client you already have.

One account · 5,900+ Connectors

  1. Real-world use case 01

    Debugging a complex AWS call

    A developer needs the specific 'cp' command for S3.

  2. Real-world use case 02

    Setting up a Vue 3 component

    A developer wants to see the props for a specific component.

  3. Real-world use case 03

    Checking SDK availability

    An engineer uses `list_libraries` to see which frameworks are supported before they decide which capabilities to use for a new project.

Complete set · 3capabilities

The complete DevDocs capability set.

These are the exact actions your AI can choose when you ask it to work with DevDocs.

Capability set01 / 01

01—03

3 capabilities in this set.

Part of 3 available through DevDocs.

  1. 01 Capability

    List libraries

    This capability shows every programming language, framework, and SDK currently supported by DevDocs. You can use it to see what's available before you start searching.

  2. 02 Capability

    Search docs

    This capability finds the exact manual page path for a specific component or class within a library. It's great for pinpointing obscure API details quickly.

  3. 03 Capability

    Read page

    This capability fetches the content of a specific documentation page and returns it as clean Markdown. It makes the data easy for your agent to read and use.

Set up in minutes

One URL. Then ask DevDocs to work.

Claude and ChatGPT only need the Connector URL. Copy it once, add it in settings, and use DevDocs from the conversation.

Choose your client

Live preview
Advanced clients IDE · CLI

Claude · Web + desktop

Official guide ↗

Connector URL · ready to paste

Streamable HTTP
https://edge.vinkius.com/vk_preview_gtakRsXSjvJKMPo5mT3ZHr5dIo7MUph0terDEOB9/mcp
  1. Step 01

    Open Connectors

    In Claude Web or Claude Desktop, open Settings and choose Connectors.

  2. Step 02

    Add the URL

    Choose Add custom connector, name it DevDocs, and paste the URL above.

  3. Step 03

    Turn it on in chat

    Select +, open Connectors, and enable DevDocs for the conversation.

Where the request belongs

Work DevDocs can move forward.

Built around the request

This is for the developer who is tired of tab-switching between their IDE and the official docs for every new library. It's for engineers who need to ground their agents in real-time, accurate technical specs to prevent code hallucinations.

01

Software Developer

The dev who needs to find a specific API method without leaving their IDE to search through layers of menus.

02

AI Engineer

The engineer building agents who needs to ground those agents in real-time, accurate technical specs.

03

Technical Writer

The writer who needs to cross-reference API signatures and documentation blocks across multiple frameworks.

04

Polyglot Programmer

The programmer jumping between Rust, Vue, and AWS who needs a unified way to find docs for everything.

Build the capability set

Add more capabilities.

Each Connector adds new actions and data without changing how you work.

Browse Connectors
ReadMe logo
01 10 capabilities

ReadMe

Equip your AI to directly search, read, and manage developer documentation stored in your ReadMe project.

View Connector
DocBreach logo
02 5 capabilities

DocBreach

Real-time documentation discovery for AI agents. Discover, read, and extract any API documentation without browser rendering or API keys.

View Connector
Archbee logo
03 19 capabilities

Archbee

Manage documentation spaces, sync OpenAPI specs, and organize technical knowledge directly from your AI agent.

View Connector
DeveloperHub logo
04 10 capabilities

DeveloperHub

Equip your AI agent to manage documentation projects, track pages, and monitor changelogs via the DeveloperHub API.

View Connector
Fern logo
05 6 capabilities

Fern

Manage and interact with Fern documentation platforms. generate access tokens, index websites for AI, and query analytics directly from your agent.

View Connector
GitBook logo
06 8 capabilities

GitBook

Manage technical documentation via GitBook. list organizations and spaces, handle document pages, search content, and audit collections directly from any AI agent.

View Connector

Bring your own AI

Change the model, client or framework. Keep DevDocs 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 DevDocs.

The practical details behind the request, access and result.

How does the DevDocs MCP help my coding workflow?

It allows your AI agent to fetch real-time documentation for libraries like AWS, Vue, and Rust. This means your agent can provide accurate code snippets and parameter details without you having to search through multiple tabs.

Can I use this for AWS and Vue 3 documentation?

Yes, the Connector connects to a large registry that includes some of the most popular frameworks and SDKs, including AWS and Vue 3.

Does it work with Cursor and Claude?

Yes, it works with any MCP-compatible client, including Claude, Cursor, and Windsurf.

Do I need to provide any API keys for DevDocs?

No, this Connector uses the public DevDocs.io registry, so you don't need to manage any extra credentials or API keys.

How does it handle Markdown conversion?

It automatically pulls the documentation and converts the static content into clean Markdown. This makes it easy for your AI agent to read and reference in your chat.

Can it search for specific classes in a library?

Yes, you can ask your agent to search for specific components, classes, or manual page paths within the supported documentation libraries.

Does this server require a DevDocs.io account or API key?

No. This server uses the public DevDocs.io registry and documentation indices, which do not require authentication. You can start querying technical documentation immediately without any setup.

Can my agent search within a specific library like 'react' or 'tailwindcss'?

Yes. Use the 'search_docs' capability. Provide the library slug (e.g., 'react') and your search query. The agent will directly attack the internal search index, rapidly filtering available paths matching your keyword.

How do I get the actual documentation content in Markdown format?

Use the 'read_page' capability. Provide the library slug and the exact page path (which you can find using search_docs). Your agent will translate the native DevDocs static HTML blobs directly into clean, human-readable Markdown payloads.

One connection away

Give your agent a direct line to DevDocs.

Connect DevDocs once. Keep it beside 5,900+ managed Connectors when the next task needs more.

Explore every Connector No credit card required · Free tier available