Server Details
Driven Intent Negotiation — Contract-Oriented Deterministic Executable Runtime DinCoder brings the…
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- flight505/MCP_DinCoder
- GitHub Stars
- 2
- Server Listing
- DinCoder
Available Tools
34 toolsartifacts_analyzeTry in Inspector
Analyze consistency across spec, plan, and tasks artifacts. Verifies that all artifacts are aligned and complete.
| Name | Required | Description | Default |
|---|---|---|---|
| artifacts | No | Which artifacts to analyze (default: all) | |
| workspacePath | No | Workspace directory path |
artifacts_readTry in Inspector
Read and return the current state of spec.json, plan.json, or tasks.json files. Use to retrieve project artifacts in normalized JSON format.
| Name | Required | Description | Default |
|---|---|---|---|
| artifactType | Yes | Type of artifact to read | |
| workspacePath | No | Workspace directory path |
clarify_addTry in Inspector
Flag ambiguities or questions in specifications that need clarification. Creates a tracked clarification with unique ID.
| Name | Required | Description | Default |
|---|---|---|---|
| context | No | Context or section where clarification is needed | |
| options | No | Possible options or approaches to consider | |
| question | Yes | The clarification question to ask | |
| specPath | No | Path to specific spec file (optional) | |
| workspacePath | No | Workspace directory path |
clarify_listTry in Inspector
List all clarifications with optional status filter (pending/resolved/all). Useful for tracking progress.
| Name | Required | Description | Default |
|---|---|---|---|
| status | No | Filter by status | |
| workspacePath | No | Workspace directory path |
clarify_resolveTry in Inspector
Resolve a pending clarification with an answer. Updates spec.md and logs resolution in research.md.
| Name | Required | Description | Default |
|---|---|---|---|
| rationale | No | Reasoning behind the resolution | |
| resolution | Yes | The answer/resolution to the clarification | |
| workspacePath | No | Workspace directory path | |
| clarificationId | Yes | ID of the clarification to resolve (e.g., CLARIFY-001) |
constitution_createTry in Inspector
Define project principles, constraints, and preferences that guide all AI-generated artifacts. Use this before specify_start to establish project guardrails.
| Name | Required | Description | Default |
|---|---|---|---|
| principles | Yes | Project principles (e.g., "Prefer functional patterns") | |
| constraints | Yes | Technical constraints (e.g., "Max bundle size: 500KB") | |
| preferences | No | Optional preferences for libraries, patterns, and style | |
| projectName | Yes | Name of the project | |
| workspacePath | No | Workspace directory path |
contracts_generateTry in Inspector
Generate OpenAPI 3.1, GraphQL, or JSON Schema contracts from specifications. Supports automatic extraction from spec.md or TypeScript code using tsoa.
| Name | Required | Description | Default |
|---|---|---|---|
| format | No | Contract format to generate | openapi |
| specPath | No | Path to specification file (auto-detect if not provided) | |
| outputPath | No | Output path for generated contract (default: contracts/ in spec directory) | |
| workspacePath | No | Workspace directory path | |
| includeExamples | No | Include example values in generated contract |
git_create_branchTry in Inspector
Create a new Git branch for implementing a specific feature or fix. Follows naming conventions and ensures clean branch creation from main/master.
| Name | Required | Description | Default |
|---|---|---|---|
| branchName | Yes | Name of the branch to create | |
| fromBranch | No | Base branch to create from (default: current branch) | |
| workspacePath | No | Workspace directory path |
metrics_exportTry in Inspector
Export metrics to CSV or JSON format for external analysis. Includes DORA metrics, cycle time, quality metrics, and custom date ranges.
| Name | Required | Description | Default |
|---|---|---|---|
| format | Yes | Export format | |
| endDate | No | End date (ISO 8601 format, defaults to now) | |
| startDate | No | Start date (ISO 8601 format, defaults to 30 days ago) | |
| outputPath | Yes | Output file path for export (e.g., metrics.csv or metrics.json) | |
| workspacePath | No | Workspace directory path |
metrics_reportTry in Inspector
Generate comprehensive metrics report with DORA and SPACE metrics. Tracks development velocity, cycle time, quality, and trends using Git history for timestamps.
| Name | Required | Description | Default |
|---|---|---|---|
| format | No | Output format | json |
| endDate | No | End date (ISO 8601 format, defaults to now) | |
| startDate | No | Start date (ISO 8601 format, defaults to 30 days ago) | |
| workspacePath | No | Workspace directory path |
plan_createTry in Inspector
Generate technical implementation plan from the project specification. Creates a step-by-step technical approach with milestones and architecture decisions.
| Name | Required | Description | Default |
|---|---|---|---|
| specPath | No | Path to specification file | |
| workspacePath | No | Workspace directory path | |
| constraintsText | Yes | Technical constraints and requirements |
prereqs_checkTry in Inspector
Check environment prerequisites before project setup. Verifies Node.js version, npm, git, and custom commands are available.
| Name | Required | Description | Default |
|---|---|---|---|
| checkFor | No | What to check for (default: node, npm, git) | |
| workspacePath | No | Workspace directory path |
quality_deps_updateTry in Inspector
Check for available updates to project dependencies. Lists outdated packages and their latest versions for potential upgrades.
| Name | Required | Description | Default |
|---|---|---|---|
| check | No | Only check for updates without installing | |
| workspacePath | No | Workspace directory path |
quality_formatTry in Inspector
Run Prettier code formatter to ensure consistent code style. Automatically formats JavaScript, TypeScript, JSON, and other supported files.
| Name | Required | Description | Default |
|---|---|---|---|
| fix | No | Apply fixes automatically | |
| workspacePath | No | Workspace directory path |
quality_license_checkTry in Inspector
Analyze licenses of all dependencies to ensure compatibility with project requirements. Identifies potential licensing conflicts or restrictions.
| Name | Required | Description | Default |
|---|---|---|---|
| workspacePath | No | Workspace directory path | |
| allowedLicenses | No | List of allowed license types |
quality_lintTry in Inspector
Run ESLint to check for code quality issues, potential bugs, and style violations. Helps maintain code standards and catch errors early.
| Name | Required | Description | Default |
|---|---|---|---|
| fix | No | Apply fixes automatically | |
| workspacePath | No | Workspace directory path |
quality_security_auditTry in Inspector
Run npm/yarn security audit to check for known vulnerabilities in dependencies. Identifies and reports security issues that need attention.
| Name | Required | Description | Default |
|---|---|---|---|
| fix | No | Apply fixes automatically | |
| workspacePath | No | Workspace directory path |
quality_testTry in Inspector
Run test suite with optional code coverage reporting. Executes all unit and integration tests to ensure code correctness.
| Name | Required | Description | Default |
|---|---|---|---|
| coverage | No | Include coverage report | |
| workspacePath | No | Workspace directory path |
research_appendTry in Inspector
Append technical decisions, trade-offs, and research findings to the research.md document. Maintains a record of architectural choices and reasoning.
| Name | Required | Description | Default |
|---|---|---|---|
| topic | Yes | Research topic or decision area | |
| content | Yes | Research content or decision rationale | |
| workspacePath | No | Workspace directory path |
specify_describeTry in Inspector
Create or update project specification with detailed requirements, goals, and constraints. Use after specify_start to define what the project should do.
| Name | Required | Description | Default |
|---|---|---|---|
| description | Yes | Project specification description | |
| workspacePath | No | Workspace directory path |
specify_startTry in Inspector
Initialize a new spec-driven project. Creates .dincoder directory with spec.json template. Use this as the first step when starting a new project.
| Name | Required | Description | Default |
|---|---|---|---|
| agent | Yes | AI agent to use | |
| projectName | Yes | Name of the project to initialize | |
| workspacePath | No | Workspace directory path |
spec_lintTry in Inspector
Automated spec quality checking with markdownlint, spec-specific rules, and prose quality analysis. Checks for required sections, acceptance criteria format, passive voice, vague language, and more. Supports auto-fix for simple issues.
| Name | Required | Description | Default |
|---|---|---|---|
| config | No | Custom lint configuration (overrides defaults) | |
| format | No | Output format | markdown |
| autoFix | No | Automatically fix issues when possible | |
| specPath | No | Path to spec file (defaults to .dincoder/spec.md or auto-detect) | |
| workspacePath | No | Workspace directory path |
spec_refineTry in Inspector
Refine/update an existing specification. Supports updating specific sections (goals, requirements, acceptance, edge-cases) or the full spec. Changes are logged to research.md.
| Name | Required | Description | Default |
|---|---|---|---|
| reason | Yes | Why this refinement is needed | |
| changes | Yes | Markdown describing the refinements to make | |
| section | Yes | Section to refine (goals | requirements | acceptance | edge-cases | full) | |
| specPath | No | Path to specific spec file (auto-detect if not provided) | |
| workspacePath | No | Workspace directory path |
spec_validateTry in Inspector
Check specification quality and completeness. Validates required sections, acceptance criteria, clarifications, and checks for premature implementation details.
| Name | Required | Description | Default |
|---|---|---|---|
| checks | No | Which checks to run (default: all) | |
| specPath | No | Path to specific spec file (auto-detect if not provided) | |
| workspacePath | No | Workspace directory path |
tasks_filterTry in Inspector
Filter tasks by status, phase, type, priority, blockers, or tags. Includes smart presets (next, frontend, backend, ready, cleanup) for common workflows. Returns markdown-formatted task list.
| Name | Required | Description | Default |
|---|---|---|---|
| tags | No | Filter by tags (AND logic - task must have all tags) | |
| type | No | Filter by type (e.g., "frontend", "backend", "test", "docs") | |
| limit | No | Limit number of results | |
| phase | No | Filter by phase (e.g., "setup", "core", "polish") | |
| preset | No | Use a smart preset filter | none |
| sortBy | No | Sort results by field | id |
| status | No | Filter by task status | all |
| blocker | No | Filter by blocker status | all |
| priority | No | Filter by priority | all |
| tasksPath | No | Direct path to tasks.md file (overrides workspacePath) | |
| workspacePath | No | Path to workspace directory containing .dincoder folder |
tasks_generateTry in Inspector
Generate granular, actionable tasks from the technical plan. Creates a task list with specific implementation steps that can be executed sequentially.
| Name | Required | Description | Default |
|---|---|---|---|
| scope | Yes | Scope or context for task generation | |
| planPath | No | Path to plan file | |
| workspacePath | No | Workspace directory path |
tasks_searchTry in Inspector
Full-text search across task descriptions and metadata. Supports plain text, regex patterns, and fuzzy matching for typo tolerance. Returns ranked results with relevance scores.
| Name | Required | Description | Default |
|---|---|---|---|
| fuzzy | No | Enable fuzzy matching for typo tolerance | |
| limit | No | Limit number of results (default: 10, max: 100) | |
| query | Yes | Search query (plain text or regex pattern) | |
| useRegex | No | Treat query as regex pattern | |
| tasksPath | No | Direct path to tasks.md file (overrides workspacePath) | |
| searchFields | No | Fields to search in | |
| caseSensitive | No | Case-sensitive search | |
| workspacePath | No | Path to workspace directory containing .dincoder folder | |
| fuzzyThreshold | No | Fuzzy match similarity threshold (0-100%) |
tasks_statsTry in Inspector
Generate comprehensive task statistics and progress metrics. Provides insights on completion rates, phase/type distribution, priority breakdown, blocker analysis, and ASCII progress charts.
| Name | Required | Description | Default |
|---|---|---|---|
| groupBy | No | Group statistics by dimension | all |
| tasksPath | No | Direct path to tasks.md file (overrides workspacePath) | |
| showBlockers | No | Show blocker analysis | |
| showVelocity | No | Show velocity metrics (requires task completion timestamps) | |
| includeCharts | No | Include ASCII progress charts | |
| workspacePath | No | Path to workspace directory containing .dincoder folder |
tasks_tickTry in Inspector
Mark a specific task as complete by its ID. Updates the task status and tracks progress through the implementation.
| Name | Required | Description | Default |
|---|---|---|---|
| taskId | Yes | Task ID to mark as complete | |
| tasksPath | No | Path to tasks file | |
| workspacePath | No | Workspace directory path |
tasks_tick_rangeTry in Inspector
Mark multiple tasks as complete at once. Supports array format ["T001", "T003"], range format "T001-T005", or mixed format. Includes strict mode for all-or-nothing completion.
| Name | Required | Description | Default |
|---|---|---|---|
| notes | No | Optional completion notes | |
| strict | No | If true, fail all if any task is invalid. If false, skip invalid tasks and continue. | |
| taskIds | Yes | Task IDs to complete. Supports array ["T001", "T003"], range "T001-T005", or mixed ["T001-T005", "T010"] | |
| tasksPath | No | Direct path to tasks.md file (overrides workspacePath) | |
| workspacePath | No | Path to workspace directory containing .dincoder folder |
tasks_visualizeTry in Inspector
Generate visual dependency graphs from tasks.md. Supports Mermaid flowcharts, Graphviz DOT, and ASCII tree formats. Shows task dependencies, status colors, and optional phase grouping.
| Name | Required | Description | Default |
|---|---|---|---|
| format | No | Output format | mermaid |
| tasksPath | No | Direct path to tasks.md file (overrides workspacePath) | |
| groupByPhase | No | Group tasks by phase using subgraphs | |
| workspacePath | No | Path to workspace directory containing .dincoder folder | |
| includeCompleted | No | Include completed tasks in visualization | |
| highlightCriticalPath | No | Highlight the critical path |
templates_customizeTry in Inspector
Create or update template customization with hooks, variable substitution, and inheritance. Supports before/after/transform/validate hooks.
| Name | Required | Description | Default |
|---|---|---|---|
| hooks | No | Template hooks for customization | |
| extends | No | Parent template ID for inheritance | |
| variables | No | Variable substitutions | |
| templateId | Yes | ID of the template to customize (e.g., "web-app", "api-service") | |
| overridePath | No | Path to custom template file (overrides built-in template) | |
| workspacePath | No | Workspace directory path | |
| customizationPath | Yes | Path to save customization config (relative to workspace) |
templates_listTry in Inspector
List all available templates (built-in and custom). Filter by category and discover customization points.
| Name | Required | Description | Default |
|---|---|---|---|
| category | No | Filter by template category | all |
| includeCustom | No | Include custom templates | |
| workspacePath | No | Workspace directory path |
test_echoTry in Inspector
Simple echo tool for testing MCP server connectivity. Returns the input message prefixed with "Echo:". Use for debugging and connection verification.
| Name | Required | Description | Default |
|---|---|---|---|
| message | Yes | Message to echo |
FAQ
How do I claim this server?
To claim this server, publish a /.well-known/glama.json file on your server's domain with the following structure:
The email address must match the email associated with your Glama account. Once verified, the server will appear as claimed by you.
What are the benefits of claiming a server?
- Control your server's listing on Glama, including description and metadata
- Receive usage reports showing how your server is being used
- Get monitoring and health status updates for your server
Your Connectors
Sign in to create a connector for this server.