Skip to main content
Glama
valentil

FeatureBoard MCP Server

by valentil

Deploy the website

deploy_site

Re-render and publish a project site by committing through git integration, with optional push. Works with the project's configured website location.

Instructions

Re-render the project's site and publish it by committing (and optionally pushing) it through the git integration — the MCP equivalent of the old website deploy. The site lives at /site/ by default, or at the project's websiteLocation when set (a shipped site outside the pad, in its own repo — see set_project_config). When websiteLocation / gitTargets.websiteRepo is configured the commit runs in that website repo; otherwise it runs where the pad site lives. Requires git integration enabled (set_git_config); no-ops with a reason otherwise. When push is omitted, the effective push behavior is resolved from gitMode the same way as commit_feature (project override, else account-wide default, else "commit-only"); "ask" never pushes silently. Runs on this machine using its git credentials.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pushNoOverride the resolved gitMode for this deploy (always wins over gitMode).
messageNoCustom deploy commit message.
projectYes
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Discloses non-readOnly mutation (commit/push), details site location logic, git credential usage, and push resolution behavior. Goes well beyond annotations which only indicate open-world and non-destructive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Every sentence adds value; front-loaded with core purpose, then logically expands on location, prerequisites, and behavior. No filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers prerequisites, location, push behavior, and execution context (local git credentials). No output schema, but description is sufficient for correct invocation without missing info.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Adds significant context for 'push' parameter (resolution rules) and 'project' (site location), but does not describe 'message'. Schema coverage 67% is partially compensated by description detail.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states it re-renders and publishes the site via git commit/push, distinguishing it from other tools. References to 'MCP equivalent of old website deploy' and explicit verb+resource make purpose unmistakable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Specifies prerequisite (git integration enabled) and explains push behavior resolution. Does not explicitly contrast with sibling tools, but context is clear; no alternative deploy tool exists among siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/valentil/featureboard-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server