# DeveloperHub MCP for AI Agents MCP

> DeveloperHub equips your AI agent to manage complex documentation projects. It lets you list all existing technical portals, retrieve specific page content in Markdown format, and track product changelogs across multiple versions automatically.

## Overview
- **Category:** developer-tools
- **Price:** Free
- **Tags:** documentation-portals, changelogs, technical-writing, api-docs, project-management, version-control

## Description

Managing a company's knowledge base is a huge headache. Documentation changes constantly—pages get updated, new versions drop, and the project structure shifts. Instead of manually jumping between portals to figure out what changed or where a specific piece of code lives, you talk to your AI client. This MCP connects your agent directly to DeveloperHub’s API, giving it deep knowledge of all your technical documentation projects.

Your agent can list every portal you own and pull the full metadata for each one. Need to know what's new? The system tracks product release notes (changelogs) automatically. It even lets you see a structural map of an entire project or pinpoint exactly which pages were modified recently. Whether you use your AI client through Claude, Cursor, or another compatible platform in the Vinkius catalog, you can orchestrate your developer experience and documentation oversight with simple conversation.

## Tools

### get_account_metadata
Retrieves usage limits and general metadata for your DeveloperHub account.

### get_documentation_page_content
Pulls the complete text and associated metadata from a specific documentation page.

### get_documentation_sitemap
Generates a structural map showing all pages within an entire project.

### get_documentation_project_details
Fetches detailed information about a single, specific documentation project or portal.

### list_product_changelogs
Lists all historical product release notes and updates linked to your projects.

### list_documentation_pages
Lists every single page and sub-page contained within a specific documentation project.

### list_documentation_projects
Provides a list of all unique documentation projects housed in your account.

### list_recently_updated_pages
Identifies and lists pages that have been modified or updated within a specific timeframe.

### list_documentation_versions
Shows all available versions, such as v1.0 or v2.5, for any given documentation project.

### search_documentation_portal
Searches for specific keywords across every single page in a designated documentation project.

## Prompt Examples

**Prompt:** 
```
Can you list all our API projects and tell me which ones have been updated in the last month?
```

**Response:** 
```
**Project Status Report**

*   **Authentication Service:** Updated 3 days ago. (Check: `list_recently_updated_pages`)
*   **Billing Endpoints:** No updates this cycle.
*   **User Management Portal:** Minor changes found in the 'Rate Limiting' section. **(Action Needed)**

We also found these recent changelog entries for Authentication Service:
- v2.1.0: Added OAuth 2.0 support.
- v2.0.5: Improved token refresh rates.
```

**Prompt:** 
```
I need the full markdown content and sitemap for our new Reporting API.
```

**Response:** 
```
**Reporting API Documentation Structure**

*   **Project Name:** Reporting API
*   **Status:** Ready for review.
*   **Sitemap Summary (12 Pages):** Authentication, Endpoints Overview, Data Filters, Error Codes, Usage Guide, v2.0 Changelog, etc.

The full content and metadata are available here: [Link to Content]. Let me know if you want the detailed Markdown for any specific section.
```

**Prompt:** 
```
What were the key architectural changes in our documentation recently?
```

**Response:** 
```
I checked the changelogs and recent updates. Two major shifts stand out:

1. **v2.2.0 (Major):** The entire data filtering section was moved into a dedicated sub-portal, requiring an update to the main index page.
2. **User Auth:** The process shifted from basic tokens to OAuth 2.0 flow, detailed in the Authentication Guide and listed as active on v2.1.0.

I recommend reviewing both the changelog entries and the 'Authentication' pages for full details.
```

## Capabilities

### Project Oversight
Lists all existing technical documentation portals and retrieves detailed metadata for each one.

### Page Content Retrieval
Gets the full text, structure, and metadata for any specific page within a project.

### Documentation Mapping
Builds structural maps of all pages and sub-pages in an entire documentation portfolio.

### Version History Tracking
Identifies which documentation versions are available for a project, including the current active one.

### Changelog Monitoring
Lists all product release notes and updates associated with specific documentation projects.

### Content Search
Searches for specific keywords across every page in a targeted documentation project.

## Use Cases

### A Product Manager needs to prep for a launch.
The PM asks the agent: 'What's new in API-Reference and what versions are available?' The agent uses `list_product_changelogs` and `list_documentation_versions`, providing the PM with a clear status report detailing all release notes and confirming that version 2.5 is ready to go.

### A Technical Writer needs a content audit.
The writer asks: 'List every page in our Billing Guide project.' The agent uses `list_documentation_pages` followed by `get_documentation_sitemap`, giving the writer a full, hierarchical map of all pages and sub-sections to check for outdated links.

### A Developer Advocate needs specific API syntax.
The advocate asks: 'How do I configure webhooks in our services?' The agent uses `search_documentation_portal` with the keyword 'webhooks', immediately pulling up the relevant guide and reference page content.

### A Team Lead needs to assess project scope.
The team lead asks: 'Show me all documentation projects we manage.' The agent calls `list_documentation_projects`, giving an immediate overview of every portal the company maintains, helping prioritize content audits.

## Benefits

- Stop manually compiling release reports. Use `list_product_changelogs` to get a consolidated list of all product updates instantly.
- Never lose track of content versions again. The MCP can use `list_documentation_versions` to tell you exactly what version is currently active and which ones exist.
- Build better search workflows. Instead of simple keyword searches, use `search_documentation_portal` to find specific technical details across a huge project.
- Get the full scope at a glance. Use `list_documentation_projects` to see every documentation portal your company maintains from one place.
- Improve content accuracy by using `list_recently_updated_pages` to flag any sections that need immediate review before a major release.

## How It Works

The bottom line is you get a single conversational interface for managing scattered documentation assets across multiple portals.

1. You connect the DeveloperHub integration to your AI client and authorize it using your API Key.
2. Your agent uses natural language prompts—like asking for 'all pages in Project X' or 'the latest changelog entries'—to call the necessary tools.
3. The MCP sends back structured data, allowing your AI client to summarize complex documentation structures, content, and version histories conversationally.

## Frequently Asked Questions

**How does DeveloperHub MCP help me track documentation versions?**
It automatically identifies every version (like v1.0 or v3.2) available for a project, so you always know if the content you're looking at is the latest release or an older draft. This prevents publishing outdated guides.

**Can DeveloperHub MCP help me find specific technical details across all my projects?**
Yes. You can query every single documentation portal, letting your agent search for a keyword like 'webhooks' and pulling results from multiple different project types simultaneously.

**What if I need to know what changed since the last release?**
The MCP tracks product changelogs. You simply ask about updates, and it will list all historical releases, showing exactly which features were added or fixed in previous versions.

**Is DeveloperHub MCP better than just using Google Search for documentation?**
Yes, because it understands the structure. Instead of just keyword matching, your agent sees the entire project map and can pull specific content sections and metadata—something a simple search engine can't do.

**Do I need to use DeveloperHub MCP for every single document?**
No. But if you manage documentation across multiple interconnected portals or care about version control, using this MCP ensures your AI agent has a complete and accurate view of your entire technical knowledge base.

**What kind of projects can I list with DeveloperHub MCP?**
It lists all types of documentation portals—from API reference guides to user onboarding tutorials. It gives you an inventory of every structured project the company maintains.