DevFoundry MCP

DevFoundry MCP exposes registered capabilities to AI-native editors and assistants. Implement once, register in the DevFoundry Registry — your agent gets the same capabilities as DevFoundry CLI, DevFoundry API, and the DevFoundry Website.

What is MCP?

The Model Context Protocol lets AI clients discover and invoke external tools over a standard interface. DevFoundry MCP (@devfoundry-dev/mcp) registers all built-in tools automatically — tool names follow tool.action (for example slugify.run, image.optimize).

Cursor & Claude

Add one config entry and every DevFoundry tool appears in your agent's tool list.

Structured results

Responses use the DevFoundry result envelope: success, message, data, warnings, durationMs.

No duplicate logic

MCP is a thin stdio adapter — the same engines and registry as CLI and web.

Installation

Install the MCP server globally (includes the full tool registry as a dependency):

npm install -g @devfoundry-dev/mcp

Verify the binary:

devfoundry-mcp --help 2>&1 || true   # stdio server — exits when stdin closes

Screenshots: run npx playwright install chromium once for web.screenshot support in local MCP sessions.

Cursor

Create or edit .cursor/mcp.json in your project (or global Cursor MCP settings):

{
  "mcpServers": {
    "devfoundry": {
      "command": "devfoundry-mcp",
      "args": []
    }
  }
}

For development from a monorepo checkout, use npm run mcp with cwd set to the repo root instead. See examples/mcp/cursor.json.

Claude Desktop

Add to claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/claude_desktop_config.json):

{
  "mcpServers": {
    "devfoundry": {
      "command": "devfoundry-mcp",
      "args": []
    }
  }
}

Restart Claude Desktop after saving. DevFoundry tools appear under the MCP tools panel.

VS Code

VS Code supports MCP through extensions such as the official MCP extension or Copilot MCP integration (availability varies by release channel). Use the same devfoundry-mcp command in your MCP server configuration:

{
  "servers": {
    "devfoundry": {
      "command": "devfoundry-mcp",
      "args": []
    }
  }
}

Refer to your extension's documentation for the exact config file location and schema.

Tool invocation

Once connected, your client lists tools automatically. Example tool names:

slugify.run — generate URL slugs
json.format — pretty-print JSON
image.optimize — resize and compress images
web.metadata — fetch and summarize page metadata
web.screenshot — capture a PNG screenshot
html.markdown — convert HTML to Markdown

Run devfoundry tools from the CLI for the complete list. MCP tool inputs match each action's JSON Schema.

More examples: examples/mcp/

Roadmap

MCP progress notifications (tool execution streaming)
Resource providers for file and URL inputs
Remote HTTP transport for hosted MCP
OAuth and scoped tool access for team deployments

Alpha status

The MCP server is in public alpha alongside the CLI. Tool schemas and response shapes align with the registry today but may change before stable release. Progress messages go to stderr; MCP responses contain only the final structured result.

Also available: CLI for scripts and CI · website for browser workflows