Index / MCP servers / Bootify

Bootify MCP server

Connect Bootify and your agent gets 57 tools, among them addAppModule, addBreakpoint, addDataObject. It answers at https://bootify.io/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 4 of 4 times since 29 September 2026; the last check, on 15 November 2026, succeeded.

Status
Answering
Tools
57
Official
yes, served from bootify.io
Reliability
4 of 4 checks
Response time
80 ms
Transport
streamable HTTP
Last checked
15 November 2026

Build Spring Boot applications, ready for coding agents, including best practices.

Description as the publisher wrote it.

The 57 tools Bootify offers

ToolWhat it does
addAppModuleAvailable with Bootify Professional. Add a custom application module. References name the modules this module depends on. The same graph defines package boundaries for MODULITH and physical build modules for MULTI_MODULE; select either with
Inputs: projectId, name, references
addBreakpointAvailable with Bootify Professional. Snapshot the current database schema so subsequent schema changes generate a new Flyway, Liquibase or Mongock changelog. Available only when getProject BREAKPOINTS reports AVAILABLE. Generated changelogs
Inputs: projectId
addDataObjectAdd a custom data object by name. Entity-generated DTOs are returned by getProject with generated=true and must be changed through their entity fields or REST/frontend options. Background information: https://bootify.io/spring-data/hibernat
Inputs: projectId, name, appModule, featurePackage, fields
addDependencyAdd an extra application dependency to the generated Maven or Gradle build. Bootify already adds dependencies required by selected project features. Call listAvailableDependencies to find supported coordinates, then pass the returned groupI
Inputs: dependency, projectId
addEntityAdd an entity to an existing Bootify project. Entity, field, module, inheritance and custom field-type references use names.
Inputs: appModule, featurePackage, superclass, inherits, restEnabled, frontendEnabled
addEnumAdd an enum to an existing Bootify project, identified by name.
Inputs: projectId, name, appModule, featurePackage, values
addFrontendControllerAvailable with Bootify Professional. Add a custom frontend controller by name. Entity-generated controllers are returned by the matching getProject details option with generated=true and must be changed through their entity options.
Inputs: projectId, name, appModule, featurePackage, path, parameters
addIndexAdd a normal or unique index over ordered entity fields or owning-side relations. Many-to-many relations are excluded. The response returns its name selector as Entity.field1-field2.
Inputs: entity, unique, fields, projectId
addRelationAdd a relation whose type describes the cardinality from fromEntity to toEntity. For MANY_TO_ONE, ONE_TO_ONE and MANY_TO_MANY the owning field is fromEntity.fromField; for ONE_TO_MANY it is toEntity.toField. The response includes that canon
Inputs: type, fromEntity, fromField, toEntity, toField, tableName
addRestControllerAvailable with Bootify Professional. Add a custom REST controller by name. Entity-generated controllers are returned by the matching getProject details option with generated=true and must be changed through their entity options.
Inputs: projectId, name, appModule, featurePackage, path, parameters
addSecurityConfigCreate a config with safe defaults. Configure roles, login and an optional user source through their dedicated tools.
Inputs: projectId, name, type, appModule, featurePackage
configureSecurityLoginConfigure only login, JWT, Keycloak and session behavior. Provide just the fields that should change.
Inputs: projectId, name, loginMethods, loginClientIds, jwtAlgorithm, keycloakRealmId
configureSecurityUserSourceConfigure the user entity and its credential, OAuth mapping, password reset and token fields. Provide just the fields that should change.
Inputs: projectId, name, sourceEntity, usernameField, hashField, externalIdField
copyProjectCopy a project owned by the bearer-authenticated user. Projects with an active one-time upgrade cannot be copied.
Inputs: projectId
deleteAppModuleDelete a custom application module by name. The implicit base and web modules cannot be deleted. Bootify applies its consistency rules to references and assigned project elements. Available with Bootify Professional.
Inputs: name, projectId
deleteDataObjectDelete a custom data object by name. Entity-generated DTOs are returned by getProject with generated=true and must be changed through their entity fields or REST/frontend options. Background information: https://bootify.io/spring-data/hiber
Inputs: projectId, name
deleteEntityDelete an entity identified by name. Bootify applies its consistency rules to dependent project data.
Inputs: name, projectId
deleteEnumDelete an enum identified by name. Referencing fields are changed to String by Bootify's consistency rules.
Inputs: name, projectId
deleteFrontendControllerAvailable with Bootify Professional. Delete a custom frontend controller by name. Entity-generated controllers are returned by the matching getProject details option with generated=true and must be changed through their entity options.
Inputs: projectId, name
deleteIndexDelete an index by its current name.
Inputs: name, projectId
deleteProjectClose a project owned by the bearer-authenticated user.
Inputs: projectId
deleteRelationDelete a relation using the current identifier returned by addRelation, updateRelation or getProject with RELATIONS details. The identifier is the owning entity and owning field joined with a dot; copy it verbatim because ONE_TO_MANY owners
Inputs: projectId, identifier
deleteRestControllerAvailable with Bootify Professional. Delete a custom REST controller by name. Entity-generated controllers are returned by the matching getProject details option with generated=true and must be changed through their entity options.
Inputs: projectId, name
deleteSecurityConfigDelete a security configuration by name.
Inputs: projectId, name
exportProjectReturn a ZIP download URL for an existing Bootify project. This tool should be called after all project details and the schema have been configured with the user and the current setup has been presented. Ask for approval before exporting un
Inputs: projectId
exportProjectToGitAvailable with Bootify Professional. Generate, commit and push to the saved repository and target branch. Replaces the target branch's file contents with the generated project, including deleting other files. Use only when the user has auth
Inputs: message, projectId
getGitExportStatusAvailable with Bootify Professional. Return the saved repository URL, target branch and defaultCommitMessage derived from current changes using the builder's commit message generator. This does not contact the remote or preview a Git diff.
Inputs: projectId
getOpenApiPreviewAvailable with Bootify Professional. Generate and return the OpenAPI document for the current project configuration. Use it to inspect resolved paths, parameters, request and response schemas, status codes and security schemes before export
Inputs: projectId
getProjectReturn the current basic configuration and plan information of an existing Bootify project. Entity, relation, index and other object lists are returned only when explicitly selected through details. Successful calls record MCP usage and act
Inputs: projectId, details
getProjectFileReturn one generated project file. The path may exactly match a value returned by listProjectFiles, with or without the project root directory, such as pom.xml. Text is returned as UTF-8 and binary content as Base64. Successful calls record
Inputs: projectId, path
importSqlSchemaParse SQL DDL and reconcile its tables, fields and relations with an existing Bootify project. Matching entities are updated and new entities are added.
Inputs: sql, projectId
linkProjectLink an existing Bootify project to the bearer-authenticated user. Accepts either the project URL or its 12-character project ID and updates the project's plan.
Inputs: projectUrl
listAvailableDependenciesList dependencies that can be added to the generated Maven or Gradle build. These dependencies are managed by the project's Spring Boot version and therefore do not require a dependency version. Use the optional query to narrow the result.
Inputs: projectId, query
listProjectFilesReturn every file path that would be present in the ZIP export of an existing Bootify project, without generating or returning file contents. Listing fails when the project plan has expired. Successful calls record MCP usage and activity fo
Inputs: projectId
listSecurityPathsReturn the canonical METHOD /path values that may be assigned to security roles. Pass securityConfigName while editing so that its current paths remain available. Frontend paths can only be protected by BASIC_AUTH, FORM_SESSION or KEYCLOAK_
Inputs: projectId, securityConfigName
removeBreakpointAvailable with Bootify Professional. Permanently remove one breakpoint. This changes generated changelogs and cannot be undone. Copy its epoch-second ID from getProject BREAKPOINTS. Use this tool only after the user has explicitly confirmed
Inputs: projectId, breakpointId
removeDependencyRemove a dependency from the generated Maven or Gradle build using groupId:artifactId. A version may be supplied but is not used for matching.
Inputs: dependency, projectId
setSecurityRolesReplace the role setup. Call listSecurityPaths first and use its exact METHOD /path values.
Inputs: projectId, name, roleSource, roles, roleEnum, roleFieldEnumPath
startProjectCreate a new Bootify project and return its project ID, URL, current setup and plan information. This changes server state and should only be called when the user wants a new project. Basic settings, developer preferences and database setti
Inputs: name, group, buildType, language, lombokEnabled, developerPreferences
updateAdvancedOptionsAvailable with Bootify Professional. Update one or more advanced project options. MODULITH generates package-based application modules, while MULTI_MODULE generates physical Gradle or Maven modules. Select either before defining an applicat
Inputs: projectId, modularization, multiModulePrefix, testSetup, springSession, actuatorEnabled
17 more tools

updateAppModule, updateDataObject, updateDatabase, updateDatabaseNaming, updateDateFields, updateDeveloperPreferences, updateEntity, updateEnum, updateFrontend, updateFrontendController, updateIndex, updateMailSettings, updateRelation, updateRestController, updateSecurityConfig, updateSettings, updateUtilities

Add Bootify to your AI client

Every block below points at https://bootify.io/mcp. Pick your client and copy.

Claude Code: one command in your terminal
claude mcp add --transport http bootify https://bootify.io/mcp
Claude Desktop: claude_desktop_config.json
{
  "mcpServers": {
    "bootify": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://bootify.io/mcp"]
    }
  }
}
Cursor: ~/.cursor/mcp.json, or .cursor/mcp.json in a project
{
  "mcpServers": {
    "bootify": {
      "url": "https://bootify.io/mcp"
    }
  }
}
VS Code and GitHub Copilot: .vscode/mcp.json
{
  "servers": {
    "bootify": {
      "type": "http",
      "url": "https://bootify.io/mcp"
    }
  }
}
Zed: Zed settings.json
{
  "context_servers": {
    "bootify": {
      "url": "https://bootify.io/mcp"
    }
  }
}
Windsurf: ~/.codeium/mcp_config.json
{
  "mcpServers": {
    "bootify": {
      "serverUrl": "https://bootify.io/mcp"
    }
  }
}
JetBrains AI Assistant: Settings, Tools, AI Assistant, MCP, New MCP Server, as JSON
{
  "mcpServers": {
    "bootify": {
      "url": "https://bootify.io/mcp"
    }
  }
}
Continue: .continue/mcpServers/neuronto.yaml
name: Bootify
version: 0.0.1
schema: v1
mcpServers:
  - name: Bootify
    type: streamable-http
    url: https://bootify.io/mcp
Gemini CLI: ~/.gemini/settings.json
{
  "mcpServers": {
    "bootify": {
      "httpUrl": "https://bootify.io/mcp"
    }
  }
}
Codex CLI: MCP server config
{
  "mcpServers": {
    "bootify": {
      "type": "http",
      "url": "https://bootify.io/mcp"
    }
  }
}
Warp: MCP servers, + Add, paste JSON
{
  "mcpServers": {
    "bootify": {
      "url": "https://bootify.io/mcp"
    }
  }
}
Goose: a one-click extension link
goose://extension?url=https%3A%2F%2Fbootify.io%2Fmcp&type=streamable_http&id=bootify&name=Bootify

Is Bootify up right now?

It answered our last check on 15 November 2026 in 80 ms. Over 4 checks since 29 September 2026 it answered 4. Status here comes from Neuronto's own probes, not from the publisher.

MCP servers similar to Bootify

Questions about Bootify

Is there an official Bootify MCP server?

Yes. It is published by bootify.io and served from bootify.io, the vendor's own domain: https://bootify.io/mcp.

How many tools does Bootify have?

57, as returned by the server's own tools/list on 18 November 2026: addAppModule, addBreakpoint, addDataObject, addDependency, addEntity, addEnum, addFrontendController, addIndex, and 49 more.

Is Bootify down?

It answered our last check on 15 November 2026 in 80 ms. Over 4 checks since 29 September 2026 it answered 4.

How do I add Bootify to Cursor?

Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://bootify.io/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.

Does Bootify need an API key?

It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.

Where this comes from

Publisher: io.bootify. Endpoint host: bootify.io. ARD identifier: urn:air:io.bootify:mcp:mcp. First indexed 29 September 2026. The tools are exactly what the server returned; nothing on this page is inferred from its name. Ranking in Neuronto search is never for sale.

Is this your server? Get a message the day it stops answering or its tools change: monitoring, 14 days free. Or claim the domain to manage how it is listed.