Ink MCP
Manage Ink deployments—apps, databases, domains, and git repos—from your coding agent instead of juggling separate hosting dashboards.
Overview
ink.ml/ink is an MCP server for the Operate phase that lets agents deploy and manage Ink applications, databases, domains, and git repositories.
What is this MCP server?
- Ink MCP remote at https://mcp.ml.ink/ (streamable-http)
- Tools described for deploying and managing applications, databases, domains, and git repos
- Server version 1.0.1 with open-source MCP package on GitHub (mldotink/mcp)
- Title branded Ink MCP for PaaS-style agent operations
- Reduces context switching between IDE agents and hosting control panels
- Remote https://mcp.ml.ink/ (streamable-http)
- Open-source MCP package at github.com/mldotink/mcp
What problem does it solve?
Solo builders lose flow toggling between the IDE agent and separate hosting panels whenever they ship schema changes, domains, or new app revisions.
Who is it for?
Indie devs already on or evaluating Ink hosting who want infra control via MCP during ship-and-operate loops.
Skip if: Teams standardized on unrelated clouds with no Ink account, or builders who only need local docker compose without remote deploy tools.
What do I get? / Deliverables
After adding the Ink MCP remote, your agent can drive deploy and resource management actions on ml.ink from the same session where you edit code.
- Agent-triggered application deploys on Ink
- Managed database and domain configuration changes
- Git repository linkage operations without leaving the agent session
Recommended MCP Servers
Journey fit
Operate is canonical because the server’s stated job is ongoing deploy and lifecycle management of live resources, not ideation or copywriting. Infra matches application hosting, databases, domains, and repository linkage—the daily production substrate solo builders iterate on.
How it compares
PaaS control-plane MCP server, not a brainstorming methodology skill or vet directory.
Common Questions / FAQ
Who is ink.ml/ink for?
Solo builders using Ink (ml.ink) who want Claude Code, Cursor, or Codex to manage deploys, databases, domains, and git repos over MCP.
When should I use ink.ml/ink?
Use it in Operate (and late Ship) when you promote builds, attach databases, configure domains, or sync repos—after your app exists and needs live infrastructure changes.
How do I add ink.ml/ink to my agent?
Configure streamable-http remote https://mcp.ml.ink/ in your MCP client, authenticate per Ink’s requirements, then list tools before granting production deploy permissions.