How to Use the DeveloperHub MCP in Windsurf

Q: How does Windsurf use DeveloperHub to write code?

Cascade calls getdocumentationpagecontent to read your live API specs. It then uses that exact schema to write matching TypeScript types or API clients in your editor.

Q: Can Windsurf track multiple documentation versions on DeveloperHub?

Yes, Cascade queries listdocumentationversions to find all active releases. It then targets the specific version you specify to ensure your local code matches that exact documentation release.

Q: Does Windsurf need manual prompting to search DeveloperHub?

No, Cascade chains queries autonomously. It runs searchdocumentationportal to find a keyword, grabs the page list, and fetches the content without requiring step-by-step instructions.

Q: What happens if my developer portal has thousands of pages?

The server handles large portals by using getdocumentationsitemap to map out the structure. Your agent navigates the hierarchy efficiently instead of pulling every single page at once.

Let Cascade in Windsurf read your live DeveloperHub docs to autonomously update your codebases without manual copy-pasting.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect DeveloperHub MCP to Windsurf

Create your Vinkius account to connect DeveloperHub to Windsurf 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 DeveloperHub with Windsurf

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Map DeveloperHub structures instantly in Windsurf

The DeveloperHub MCP Server exposes structural tools like `get_documentation_sitemap` and `list_documentation_pages` directly to your Cascade panel. Cascade uses these tools to build a mental map of your entire doc site in a single run. It doesn't ask you for URLs; it just crawls the hierarchy to find where your API references live. Once Cascade knows the layout, it pulls page contents using `get_documentation_page_content`. You get accurate code generation because your IDE agent works with live, actual documentation instead of stale training data.

Auto-detect docs drift inside Windsurf

This DeveloperHub MCP integration lets Cascade monitor your project updates using the `list_recently_updated_pages` tool. When a technical writer updates an API endpoint description, Cascade spots the change and alerts you. It reads the fresh page structure to see if your local types match the live portal. If a discrepancy exists, Cascade chains a sequence to pull the new details with `get_documentation_project_details`. It then rewrites the affected local files, saving you hours of debugging broken endpoints.

Run deep documentation searches via Cascade

Accessing your developer portal normally requires leaving your IDE, but this MCP Server allows Cascade to query your docs directly. Cascade runs `search_documentation_portal` to find specific keywords across all your projects. It locates the exact parameters you need without you opening a browser tab. After finding the relevant pages, the agent uses `list_documentation_versions` to check that you are reading the correct release. You write code based on the exact version running in production, avoiding deprecated functions.

Setup guide

Set up DeveloperHub MCP in Windsurf

Prerequisites

Windsurf IDE installed (macOS, Windows, or Linux)
Active Vinkius subscription with a valid endpoint token

1

Open MCP configuration

Click the Cascade assistant icon in the sidebar, then click the hammer icon (🔨) at the top of the panel. Select "Configure" to open ~/.codeium/windsurf/mcp_config.json.
2

Add the DeveloperHub MCP

Paste the JSON snippet shown on the right into the mcpServers object. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Refresh MCPs

Go back to the hammer icon (🔨) in Cascade and click "Refresh". Windsurf will detect the new server. No full restart is needed — the connection is hot-reloaded.
4

Verify in Cascade

Start a new Cascade conversation and ask something like "Show my DeveloperHub payment history." If connected, Cascade will call the DeveloperHub tools directly. You will see a green dot next to the server name in the MCP panel.

mcp_config.json

{
  "mcpServers": {
    "developerhub-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

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 DeveloperHub. 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 DeveloperHub 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 DeveloperHub MCP in Windsurf

Cascade calls `get_documentation_page_content` to read your live API specs. It then uses that exact schema to write matching TypeScript types or API clients in your editor.

Yes, Cascade queries `list_documentation_versions` to find all active releases. It then targets the specific version you specify to ensure your local code matches that exact documentation release.

No, Cascade chains queries autonomously. It runs `search_documentation_portal` to find a keyword, grabs the page list, and fetches the content without requiring step-by-step instructions.

The server handles large portals by using `get_documentation_sitemap` to map out the structure. Your agent navigates the hierarchy efficiently instead of pulling every single page at once.

Your documentation content and API metadata never pass through third-party servers. Vinkius runs this MCP Server in an isolated V8 sandbox, passing the raw text directly to your local editor session.

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