Server facts
kinsta-mcp
Project
- Author
- jacob-hartmann
- Repository
- github.com/jacob-hartmann/kinsta-mcp
- License
- Not specified
- Category
- Cloud & DevOps
Tech
- Runtime / language
- Not specified
- Transports
- stdio
- Remote available
- No
- Authentication
- Not specified
Activity
- GitHub stars
- 3
- Last commit
- Data as of
Tags
- development
- kinsta
Overview
Kinsta hosting workflows span site creation, environment management, and ongoing WordPress maintenance in kinsta-mcp. Assistants can inspect a company's sites, create or clone installations, and push changes between environments. Maintenance tools cover plugin and theme updates, PHP configuration, redirects, and cache clearing across server, edge, and CDN layers. For tasks that run asynchronously, an operation identifier lets the assistant check progress separately. Company-level queries expose users, deployment regions, activity records, and plugin or theme inventories across hosted sites.
Backup workflows include listing available copies, creating manual backups, inspecting downloadable backups, and restoring an environment. Restores overwrite the current environment, while site resets and deletion tools also carry destructive consequences. Access controls include SSH/SFTP settings, password management, IP allowlists, and additional user accounts. Domain tools handle primary-domain selection, verification records, and DNS record changes. For inspection, assistants can retrieve logs and review visits, bandwidth, and disk consumption. Setup requires a Kinsta API key and company ID; configuration examples cover Claude Desktop, Claude Code, and Cursor.
kinsta-mcp setup notes
- kinsta-mcp records stdio only; confirm a network transport upstream before planning remote access.
- kinsta-mcp has no recorded license; confirm reuse terms in its repository.