DU

dust-mcp-server

Create and register new MCP servers in Dust to connect remote platforms, using a structured step-by-step development process.

Install

mkdir -p .claude/skills/dust-mcp-server && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/4233" && unzip -o skill.zip -d .claude/skills/dust-mcp-server && rm skill.zip

Installs to .claude/skills/dust-mcp-server

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Step-by-step guide for creating new internal MCP server integrations in Dust that connect to remote platforms (Jira, HubSpot, Salesforce, etc.). Use when adding a new MCP server, implementing a platform integration, or connecting Dust to a new external service.
261 chars✓ has a “when” triggerlonger than Claude Code's old 250-char listing cap (fine on current versions)
Advanced

Key capabilities

  • →Create internal MCP server metadata
  • →Implement tool handlers for remote platforms
  • →Register servers in the Dust ecosystem
  • →Configure OAuth providers for external services

How it works

The process involves creating metadata and handler files within the Dust repository structure, then registering the server in the central constants and index files.

Inputs & outputs

You give it
Platform API documentation and tool definitions
You get back
Registered internal MCP server integration

When to use dust-mcp-server

  • →Add new platform integration
  • →Register internal MCP server
  • →Define tool metadata for external services

About dust-mcp-server

Provides a framework for building internal MCP server integrations. It outlines the file structure for tool metadata, handlers, and client registration within the Dust ecosystem.

Step-by-step guide for creating new internal MCP server integrations in Dust that connect to remote platforms (Jira, HubSpot, Salesforce, etc.). Use when adding a new MCP server, implementing a platform integration, or connecting Dust to a new external service.

When not to use it

  • →Developing external-facing public MCP servers
  • →General platform integration without Dust ecosystem requirements

Prerequisites

OAuth provider implementation in core and frontDust development environment

Limitations

  • →Server IDs must be stable and unique once deployed
  • →Requires manual registration in multiple configuration files
  • →OAuth token refresh must follow the withAuth pattern

How it compares

This workflow enforces a specific file structure and type-checked tool definition pattern compared to generic MCP server development.

Compared to similar skills

dust-mcp-server side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
dust-mcp-server (this skill)14moReviewAdvanced
mcporter76moNo flagsIntermediate
calcom-api27moNo flagsIntermediate
developing-genkit-tooling29moNo flagsIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

You might also like

mcporter

openclaw

Use the mcporter CLI to list, configure, auth, and call MCP servers/tools directly (HTTP or stdio), including ad-hoc servers, config edits, and CLI/type generation.

726

calcom-api

calcom

Interact with the Cal.com API v2 to manage scheduling, bookings, event types, availability, and calendars. Use this skill when building integrations that need to create or manage bookings, check availability, configure event types, or sync calendars with Cal.com's scheduling infrastructure.

216

developing-genkit-tooling

firebase

Best practices for authoring Genkit tooling, including CLI commands and MCP server tools. Covers naming conventions, architectural patterns, and consistency guidelines.

27

juicebox-rate-limits

jeremylongshore

Implement Juicebox rate limiting and backoff. Use when handling API quotas, implementing retry logic, or optimizing request throughput. Trigger with phrases like "juicebox rate limit", "juicebox quota", "juicebox throttling", "juicebox backoff".

23

clay-sdk-patterns

jeremylongshore

Apply production-ready Clay SDK patterns for TypeScript and Python. Use when implementing Clay integrations, refactoring SDK usage, or establishing team coding standards for Clay. Trigger with phrases like "clay SDK patterns", "clay best practices", "clay code patterns", "idiomatic clay".

04

vercel-sdk-patterns

jeremylongshore

Execute apply production-ready Vercel SDK patterns for TypeScript and Python. Use when implementing Vercel integrations, refactoring SDK usage, or establishing team coding standards for Vercel. Trigger with phrases like "vercel SDK patterns", "vercel best practices", "vercel code patterns", "idiomatic vercel".

13

Search skills

Search the agent skills registry