home / mcp / advocu mcp server

Advocu MCP Server

Provides unified activity reporting for MVP and GDE via Claude with optional local or remote execution.

Installation

Add the following to your MCP client configuration file.

Configuration

{
  "mcpServers": {
    "carlosazaustre-advocu-mcp-server": {
      "command": "node",
      "args": [
        "/absolute/path/to/advocu-mcp-server/dist/index.js"
      ],
      "env": {
        "DOCS_DIR": "/absolute/path/to/advocu-mcp-server/docs",
        "MVP_ACCESS_TOKEN": "your_mvp_bearer_token",
        "ADVOCU_ACCESS_TOKEN": "your_gde_token",
        "MVP_USER_PROFILE_ID": "your_mvp_profile_id"
      }
    }
  }
}

You can report your MVP and GDE activities through a unified MCP server that accepts natural language submissions via Claude. It saves you time by letting you describe videos, posts, talks, or mentoring sessions, and it routes the data to the right MVP and/or GDE systems through a simple, configurable local or remote setup.

How to use

Interact with Claude to submit activities in natural language. You can report multiple activity types in one conversation, such as videos, blog posts, conference talks, or mentoring sessions. Depending on what you have access to, the server will push data to the MVP portal, the Advocu GDE API, or both.

How to install

Prerequisites: install Node.js 18 or later and have Claude Desktop installed. You also need at least one token for MVP and/or GDE.

Option 1: Local Development (Recommended)

git clone https://github.com/carlosazaustre/advocu-mcp-server.git
cd advocu-mcp-server
npm install
npm run build

Option 2: Global Install

npm install -g advocu-mcp-server

Configure Claude Desktop to run the MCP server in stdio mode. You will specify the command, arguments, and environment variables for your setup.

Configuration and usage notes

Use the following configuration samples to enable either MVP, GDE, or both in a single place. Replace the absolute paths with your actual installation paths and fill in your tokens.

{
  "mcpServers": {
    "activity-reporting": {
      "command": "node",
      "args": ["/absolute/path/to/advocu-mcp-server/dist/index.js"],
      "env": {
        "MVP_ACCESS_TOKEN": "your_mvp_bearer_token",
        "MVP_USER_PROFILE_ID": "your_mvp_profile_id",
        "ADVOCU_ACCESS_TOKEN": "your_gde_token",
        "DOCS_DIR": "/absolute/path/to/advocu-mcp-server/docs"
      }
    }
  }
}

MVP Only configuration sample shows how to run the MVP portion without the GDE token.

{
  "mcpServers": {
    "activity-reporting": {
      "command": "node",
      "args": ["/absolute/path/to/dist/index.js"],
      "env": {
        "MVP_ACCESS_TOKEN": "your_mvp_bearer_token",
        "MVP_USER_PROFILE_ID": "your_mvp_profile_id",
        "DOCS_DIR": "/absolute/path/to/advocu-mcp-server/docs"
      }
    }
  }
}

GDE Only configuration sample shows how to run the GDE portion without the MVP token.

{
  "mcpServers": {
    "activity-reporting": {
      "command": "node",
      "args": ["/absolute/path/to/dist/index.js"],
      "env": {
        "ADVOCU_ACCESS_TOKEN": "your_gde_token",
        "DOCS_DIR": "/absolute/path/to/advocu-mcp-server/docs"
      }
    }
  }
}

Documentation and startup tips

Restart Claude Desktop after changing the config so the MCP tools load correctly. Look for the hammer icon in Claude Desktop to confirm that tools are loaded.

If you encounter token expiration, use the token capture workflow to refresh tokens and update your local config. Keep your tokens secure and never commit them to version control.

Security and privacy

Tokens are stored locally in your Claude Desktop config. Do not expose tokens in public repositories. Tokens may expire and will require refreshing via the token capture flow.

Available tools and actions

MCP supports a range of tools for submitting MVP and GDE activities. You can use dedicated actions to create or update activity records across both programs.

Troubleshooting

If the tools don’t appear in Claude Desktop, verify the config path, ensure you built the project, check logs on startup, and confirm that at least one token (MVP or GDE) is configured.

Notes

This MCP server is designed to simplify reporting for MVP and GDE programs through natural-language submissions. Use it to batch submissions across multiple activity types in one conversation.

Available tools

list_documentation

List all available documentation resources for MVP and GDE in the MCP tools set.

get_documentation

Retrieve a specific documentation file by name, such as an API reference or error handling guide.

submit_mvp_video

Submit MVP video or livestream activity records with fields like title, date, URL, views, sessions, and target audience.

submit_mvp_blog

Submit MVP blog or article activity with fields such as title, date, URL, views, and audience.

submit_mvp_speaking

Submit MVP conference talks with details like title, date, attendees, and topic area.

submit_gde_content_creation

Submit GDE content creation activities including articles, videos, or podcasts.

submit_gde_public_speaking

Submit GDE talks and presentations with date, location, and audience details.

submit_gde_workshop

Submit GDE training session activities with attendees and format details.

submit_gde_mentoring

Submit mentoring activities with participant count and focus area.

submit_gde_product_feedback

Submit product feedback provided to Google as a GDE.

submit_gde_googler_interaction

Submit interactions with Google employees as a GDE.

submit_gde_story

Submit success stories or impact narratives related to GDE work.