An astronaut overseeing a futuristic data hub

Connect DevDocs to ChatGPT, Claude and Gemini

Set it up once and it works in ChatGPT, Claude, Cursor, and any other client you love. It all runs safely in the background, so you can relax and focus on what really matters. Stop switching tabs to find API references and syntax.

Ask AI about this Connector

Developed, maintained, and hosted by Vinkius.

MCP VERIFIED · PRODUCTION READY · VINKIUS GUARANTEED

Waiting for input…

Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.

ChatGPTClaudeCursorPerplexityGeminiMicrosoft CopilotRaycastMeta AI

Your AI does the work. We keep it safe and sound.

No other AI tool gives you this. Your workflow runs in the client you already love, your account stays protected, and you decide what the agent can and cannot do. It is the whole reason to make the switch.

Each Connector lives inside our infrastructure, the same place where your workflow runs. The three things below are already part of it, working quietly in the background so you never have to think about them. Nothing to add, nothing to set up, nothing to worry about.

A futuristic MCP client docking bay
V8 Isolate01

Each Connector runs inside its own sealed environment.

Each Connector runs inside its own sealed V8 runtime — no access to your files, your system, or other servers. A Connector never sees past its own request.

Kill Switch02

One switch stops every agent. Instantly.

One action deactivates every Connector, revokes every token, and ends every session at once. AI Governance keeps the record.

FinOps per User03

Spending limits that pause instead of surprise.

Every user keeps their own connections and credentials, isolated from everyone else. Anything that would cross your spending limit is held for your approval, not billed.

Three controls, built into the layer your AI connects through.

Curated set · 3 capabilities

We ship only the actions that matter.

Capability set01 / 01

01-03

3 capabilities in this set.

Part of 3 available through DevDocs.

  1. 01

    List libraries

    This capability lists all programming languages, frameworks, and SDKs available in the DevDocs registry. Use it to see what documentation your agent can access.

  2. 02

    Read page

    This capability pulls the content of a specific documentation page. It converts the page into clean Markdown for your agent to read.

  3. 03

    Search docs

    This capability searches the index of a specific library. It helps your agent find the exact path to a manual or API reference.

Real work

What teams actually run

01

API Reference Lookups

Your agent finds the exact syntax for a method while you are writing a function.

02

Framework Onboarding

Quickly pull documentation for a new library like Vue 3 or Rust to get started.

03

Agent Grounding

Provide your agent with the actual manual content to prevent hallucinated code.

04

SDK Verification

Check specific SDK library definitions to ensure compatibility with your current project.

Automate a task

Put DevDocs to work on one thing.

Step-by-step automations your AI runs through this Connector: the workflow, the prompts to start with, and the exact capabilities behind each move.

One connector, every AI

DevDocs works with the most popular AI clients.

These are the most popular clients, each with a step-by-step guide: one link, set up once, with governance and visibility built in. And because everything runs on the MCP standard, the same connection also works in any other compatible client — nothing to rebuild.

Building your own app? The connector is yours to use.

You don't need a client to put DevDocs to work: the same hosted connection plugs into your own applications and agent code, with the same governance on every request. Build with it, chat with it — one connection for both.

Observed, not estimated

888ms average. Fast in production.

DevDocs is checked daily against the live service.

Daily averagePeak 1380ms
Oct 3Today
Fastest day
778ms
Slowest day
1380ms
14-day trend
Slowing+13%

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 3 capabilities arrive ready to run.

Preview access · not provider authentication

The vk_preview_* token belongs to Vinkius preview infrastructure. It lets Claude discover and display the capabilities of DevDocs, so you can see the experience inside your AI.

It does not authenticate your account with DevDocs. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

DevDocs Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_gtakRsXSjvJKMPo5mT3ZHr5dIo7MUph0terDEOB9/mcp

Claude Desktop

Follow the steps below to connect in seconds.

  1. 1In Claude Desktop, open Settings → Connectors.
  2. 2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
  3. 3Click Add and start a new chat — DevDocs capabilities are ready to use.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "devdocs-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_gtakRsXSjvJKMPo5mT3ZHr5dIo7MUph0terDEOB9/mcp"
    }
  }
}
  • Claude
  • ChatGPT
  • Cursor
  • VS Code
  • Windsurf
  • Claude Code
  • JetBrains
  • Cline

Step-by-step instructions for each client are in the guide. How to connect

Guided setup for Claude? Set up DevDocs in Claude and other AIs

See all the AI clients this connector works with ↑

Who it's for

Built for the work DevDocs owners hand off.

This MCP is built for anyone who builds or maintains code and needs instant access to technical references.

  • 01

    Software Developers

    They use it to find API references without leaving their IDE.

  • 02

    AI Engineers

    They ground their coding agents in real-time technical documentation.

  • 03

    Technical Writers

    They verify API signatures and cross-reference documentation across different frameworks.

FAQ

Questions DevDocs owners ask.

  • 01

    Do I need to provide API keys for DevDocs?

    No. This MCP uses the public DevDocs.io registry, so no credentials are required.

  • 02

    Which AI clients can use this MCP?

    You can use this with any MCP-compatible client, including Claude, Cursor, and Windsurf.

  • 03

    What format is the documentation in?

    The MCP converts documentation into clean Markdown, which is easy for your agent to process.

  • 04

    Can I search for specific frameworks?

    Yes. You can use the list_libraries capability to see what is available or search directly for specific SDKs and languages.

  • 05

    How does this help my coding agent?

    It provides the agent with real, version-specific technical context, which helps it generate more accurate code.

  • 06

    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.

  • 07

    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.

  • 08

    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.

Connect DevDocs to Claude, Cursor, ChatGPT & more