Bootify

io.bootifyPublished by bootify.ioOfficial publisherv1.0.0Updated Oct 25, 2026

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

VerifiedStreamable HTTPWeb executableDatabasesDeveloper Tools

Overview

AI-generated overview

Bootify lets an assistant create and configure Spring Boot projects on bootify.io, managing entities, relations, indexes, modules, dependencies and REST setup.

What you can do
Create, copy, link and close Bootify projects, and read their configuration and plan details. Update project settings, developer preferences, advanced options, mail, frontend, database and date-field settings. List, add and remove Maven or Gradle dependencies. Add, update and delete application modules, enums, data objects, entities, relations and indexes. Import SQL DDL schemas and reconcile them with existing entities. Add and update REST controllers, and manage schema breakpoints for changelog generation.
When to use it
Useful when scaffolding or evolving a Spring Boot application through an assistant: starting a new project, modeling entities and relations, adjusting build dependencies or database settings, or importing an existing SQL schema.
Requirements
A remote endpoint at bootify.io; no package or environment variables are declared. Several tools act on projects owned by a bearer-authenticated user, and some features (advanced options, mail settings, application modules, breakpoints, REST controllers) require Bootify Professional.
Before you install
Many tools change or delete server-side project state, including deleteProject, deleteEntity, deleteRelation and removeBreakpoint, which cannot be undone. Breakpoint removal should follow explicit user confirmation. Generated changelogs are described as blueprints that must be adapted to production data. Some tools require a bearer-authenticated user.

Installation

In SourceWeft

  1. Open Bootify in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.bootify%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "bootify": {
      "type": "http",
      "url": "https://bootify.io/mcp"
    }
  }
}

Tools

57

startProject

Start a Bootify project

Create 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 settings can be supplied during creation; omitted settings retain their defaults. All subsequent changes made through MCP are reflected live for the user at the returned project URL. Always show that URL to the user immediately after creating the project so they can follow the changes in their browser.

ParametersnamegroupdatabaselanguagebuildTypelombokEnableddeveloperPreferences

getProject

Get a Bootify project

Return 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 activity for this project.

ParametersdetailsprojectIdrequired

linkProject

Link a Bootify project

Link 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.

ParametersprojectUrlrequired

copyProject

Copy a project owned by the bearer-authenticated user. Projects with an active one-time upgrade cannot be copied.

ParametersprojectIdrequired

deleteProject

Close a project owned by the bearer-authenticated user.

ParametersprojectIdrequired

updateSettings

Update project settings

Update one or more basic settings of an existing Bootify project. Background information: https://bootify.io/docs/general-tab.html

ParametersnamegrouplanguagebuildTypeprojectIdrequiredlombokEnabled

updateDeveloperPreferences

Update developer preferences

Update one or more developer preferences of an existing Bootify project. Background information: https://bootify.io/docs/general-tab.html

ParametersprojectIdrequireddeploymentjavaVersionopenApiEnabledpackageStructureapplicationFormatdockerComposeEnabledincludeAgentInstructions

updateAdvancedOptions

Update advanced options

Available 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 application-module graph. Background information: https://bootify.io/docs/modules-tab.html

ParametersprojectIdrequiredtestSetupspringSessionhateoasEnabledmodularizationactuatorEnabledmapStructEnabledactuatorEndpointsmultiModulePrefixserviceInterfaceEnabled

updateUtilities

Update utilities

Include utilities for custom code even when the project does not require them. Required utilities cannot be disabled. They remain included when no longer required, until explicitly disabled. Omitted options retain their values. Inspect utilities in getProject for the current inclusion state.

ParametersprojectIdrequiredincludeInputRowincludeFileHandlingincludeSearchFilterincludePaginationAndSorting

updateMailSettings

Update mail settings

Available with Bootify Professional. Enable or disable mail support and configure the generated application's SMTP connection.

ParametersfromhostenabledusernameprojectIdrequiredconnectiondisplayName

updateFrontend

Update project frontend

Update one or more frontend settings of an existing Bootify project. Background information: https://bootify.io/docs/frontend-settings.html

ParametersbuildToolframeworkprojectIdrequiredhtmxEnabledcssFrameworktypescriptEnabled

updateDatabase

Update project database

Update the database and schema management settings of an existing Bootify project. Background information: https://bootify.io/docs/general-tab.html

ParameterstypeprojectIdrequiredschemaTypemongoSchemaType

updateDatabaseNaming

Update project database naming

Update one or more database naming settings of an existing Bootify project. Background information: https://bootify.io/docs/general-tab.html

ParametersprojectIdrequiredtablePrefixtableSuffixnamingStrategypluralizeTableName

updateDateFields

Update project date fields

Enable or disable generated date fields and configure their names. Background information: https://bootify.io/docs/general-tab.html

ParametersenabledprojectIdrequireddateCreatedNamelastUpdatedName

listAvailableDependencies

List available project dependencies

List 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. Successful calls record MCP usage and activity for this project.

ParametersqueryprojectIdrequired

addDependency

Add a project dependency

Add 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 groupId:artifactId. Spring Boot supplies the compatible dependency version.

ParametersprojectIdrequireddependencyrequired

removeDependency

Remove a project dependency

Remove a dependency from the generated Maven or Gradle build using groupId:artifactId. A version may be supplied but is not used for matching.

ParametersprojectIdrequireddependencyrequired

addAppModule

Add a project application module

Available 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 updateAdvancedOptions first. The implicit base module is the lowest-level shared module and is integrated directly or transitively by every other module. A custom module with no references depends on base. The implicit web module is the highest-level application wrapper and automatically depends on every custom root module; in MULTI_MODULE it assembles the executable application. Neither implicit module can be edited. Dependencies must be acyclic and should point from a feature toward the lower-level modules it uses. Background information: https://bootify.io/docs/modules-tab.html

ParametersnamerequiredprojectIdrequiredreferences

updateAppModule

Update a project application module

Available with Bootify Professional. Update or rename a custom application module identified by its current name. When provided, references replace all current direct dependencies. The same graph defines package boundaries for MODULITH and physical build modules for MULTI_MODULE; select either with updateAdvancedOptions first. The implicit base module is the lowest-level shared module and is integrated directly or transitively by every other module. A custom module with no references depends on base. The implicit web module is the highest-level application wrapper and automatically depends on every custom root module; in MULTI_MODULE it assembles the executable application. Neither implicit module can be edited. Dependencies must be acyclic and should point from a feature toward the lower-level modules it uses. Background information: https://bootify.io/docs/modules-tab.html

ParametersnamerequirednewNameprojectIdrequiredreferences

deleteAppModule

Delete a project application module

Delete 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.

ParametersnamerequiredprojectIdrequired

addEnum

Add a project enum

Add an enum to an existing Bootify project, identified by name.

ParametersnamerequiredvaluesrequiredappModuleprojectIdrequiredfeaturePackage

updateEnum

Update a project enum

Update or rename an enum identified by its current name. Provide newName, values, appModule, featurePackage, or several.

ParametersnamerequiredvaluesnewNameappModuleprojectIdrequiredfeaturePackage

deleteEnum

Delete a project enum

Delete an enum identified by name. Referencing fields are changed to String by Bootify's consistency rules.

ParametersnamerequiredprojectIdrequired

addDataObject

Add a project data object

Add 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/hibernate-json-type.html

ParametersnamerequiredfieldsrequiredappModuleprojectIdrequiredfeaturePackage

updateDataObject

Update a project data object

Update or rename 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/hibernate-json-type.html

ParametersnamerequiredfieldsnewNameappModuleprojectIdrequiredfeaturePackage

deleteDataObject

Delete a project data object

Delete 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/hibernate-json-type.html

ParametersnamerequiredprojectIdrequired

addEntity

Add a project entity

Add an entity to an existing Bootify project. Entity, field, module, inheritance and custom field-type references use names.

ParametersnamerequiredfieldsrequiredinheritsappModuleprojectIdrequiredsuperclassrestEnabledfeaturePackagefrontendEnabledpaginationEnabledsearchFilterEnabled

updateEntity

Update a project entity

Update or rename an entity identified by its current name. Only provided properties are changed; a provided fields array replaces all fields.

ParametersnamerequiredfieldsnewNameinheritsappModuleprojectIdrequiredsuperclassrestEnabledfeaturePackagefrontendEnabledpaginationEnabledsearchFilterEnabled

deleteEntity

Delete a project entity

Delete an entity identified by name. Bootify applies its consistency rules to dependent project data.

ParametersnamerequiredprojectIdrequired

importSqlSchema

Import an SQL schema

Parse SQL DDL and reconcile its tables, fields and relations with an existing Bootify project. Matching entities are updated and new entities are added.

ParameterssqlrequiredprojectIdrequired

addBreakpoint

Add a schema breakpoint

Available 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 are blueprints and must be adapted to production data. Use this tool only after the user has explicitly confirmed adding a breakpoint.

ParametersprojectIdrequired

removeBreakpoint

Remove a schema breakpoint

Available 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 removing the breakpoint.

ParametersprojectIdrequiredbreakpointIdrequired

addRelation

Add an entity relation

Add 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 canonical owning-side value as identifier. Bidirectional relations require both fields. Background information: https://bootify.io/docs/jpa-relationship-types-with-examples.html. fromEntity and toEntity must already exist. The owning entity's application module must depend on the target entity's module.

ParameterstyperequiredtoFieldrequiredtoEntityrequiredfromFieldprojectIdrequiredtableNamefromEntityrequiredunidirectional

updateRelation

Update an entity relation

Update 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 canonical owning-side value as identifier. Bidirectional relations require both fields. Background information: https://bootify.io/docs/jpa-relationship-types-with-examples.html. Identify the existing relation with its current identifier returned by addRelation, updateRelation or getProject; do not reconstruct internal IDs. Only provided relation properties are changed. If an update changes the owning entity or field, use the newly returned identifier for subsequent calls.

ParameterstypetoFieldrequiredtoEntityfromFieldprojectIdrequiredtableNamefromEntityidentifierrequiredunidirectional

deleteRelation

Delete an entity relation

Delete 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 ownership is on the to side.

ParametersprojectIdrequiredidentifierrequired

addIndex

Add a database index

Add 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.

ParametersentityrequiredfieldsrequireduniquerequiredprojectIdrequired

updateIndex

Update a database index

Update an index by its current Entity.field1-field2 identifier. Only provided properties are changed; the response contains its updated identifier.

ParametersnamerequiredentityfieldsuniqueprojectIdrequired

deleteIndex

Delete a database index

Delete an index by its current name.

ParametersnamerequiredprojectIdrequired

addRestController

Add a REST controller

Available 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.

ParametersnamerequiredpathrequiredappModuleendpointsrequiredprojectIdrequiredparametersrequiredfeaturePackage

updateRestController

Update a REST controller

Available with Bootify Professional. Update or rename 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.

ParametersnamerequiredpathnewNameappModuleendpointsprojectIdrequiredparametersfeaturePackage

deleteRestController

Delete a REST controller

Available 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.

ParametersnamerequiredprojectIdrequired

addFrontendController

Add a frontend controller

Available 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.

ParametersnamerequiredpathrequiredappModuleendpointsrequiredprojectIdrequiredparametersrequiredfeaturePackage

updateFrontendController

Update a frontend controller

Available with Bootify Professional. Update or rename 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.

ParametersnamerequiredpathnewNameappModuleendpointsprojectIdrequiredparametersfeaturePackage

deleteFrontendController

Delete a frontend controller

Available 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.

ParametersnamerequiredprojectIdrequired

listSecurityPaths

List selectable security paths

Return 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_CLIENT. Successful calls record MCP usage and activity for this project.

ParametersprojectIdrequiredsecurityConfigName

addSecurityConfig

Add a security configuration

Create a config with safe defaults. Configure roles, login and an optional user source through their dedicated tools.

ParametersnamerequiredtyperequiredappModuleprojectIdrequiredfeaturePackage

updateSecurityConfig

Update basic security configuration

Change only the identity, type, module or authentication mode. Changing type resets type-specific settings to defaults.

ParametersnamerequiredtypenewNameappModuleprojectIdrequiredfeaturePackageauthenticationMethod

configureSecurityLogin

Configure security login

Configure only login, JWT, Keycloak and session behavior. Provide just the fields that should change.

ParametersnamerequiredprojectIdrequiredrememberMejwtAlgorithmloginMethodsloginClientIdskeycloakRealmIdkeycloakClientIdregistrationEndpoint

configureSecurityUserSource

Configure security user source

Configure the user entity and its credential, OAuth mapping, password reset and token fields. Provide just the fields that should change.

ParametersnamerequiredhashFieldprojectIdrequiredsourceEntitymapEmailFieldresetUidFieldusernameFieldloginTypeFieldexternalIdFieldresetStartFieldmapLastNameFieldrefreshTokenPath+2 more

setSecurityRoles

Set security roles and paths

Replace the role setup. Call listSecurityPaths first and use its exact METHOD /path values.

ParametersnamerequiredrolesrequiredroleEnumprojectIdrequiredroleSourcerequiredroleFieldEnumPath

deleteSecurityConfig

Delete a security configuration

Delete a security configuration by name.

ParametersnamerequiredprojectIdrequired

getOpenApiPreview

Get the generated OpenAPI preview

Available 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 exporting the project. Successful calls record MCP usage and activity for this project.

ParametersprojectIdrequired

listProjectFiles

List generated project files

Return 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 for this project.

ParametersprojectIdrequired

getProjectFile

Read a generated project file

Return 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 MCP usage and activity for this project. Generated files can include private signing keys for RSA JWT configurations; treat them as sensitive.

ParameterspathrequiredprojectIdrequired

exportProject

Export a Bootify project

Return 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 unless the user already explicitly requested the export in the current context. The client can download and extract it when the environment supports it. Export fails when the project plan has expired. Successful calls record MCP usage and activity for this project. Generated files can include private signing keys for RSA JWT configurations; treat them as sensitive.

ParametersprojectIdrequired

getGitExportStatus

Inspect Git export configuration

Available 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. Credentials are never returned. If unconfigured, open configurationUrl to configure Git in the builder. Successful calls record MCP usage and activity for this project.

ParametersprojectIdrequired

exportProjectToGit

Export a Bootify project to Git

Available 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 authorized the Git export. Inspect getGitExportStatus first. The optional message overrides defaultCommitMessage; when omitted it is calculated at export time. No commit is created when generated files have not changed; commitSha is then null. Requires saved Git credentials and active export access. Successful calls record MCP usage and activity.

ParametersmessageprojectIdrequired

Version history

1
  1. v1.0.0LatestSep 29, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.