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.
Build Spring Boot applications, ready for coding agents, including best practices.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
addAppModule | 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 Inputs: projectId, name, references |
addBreakpoint | 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 Inputs: projectId |
addDataObject | 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/hibernat Inputs: projectId, name, appModule, featurePackage, fields |
addDependency | 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 groupI Inputs: dependency, projectId |
addEntity | Add 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 |
addEnum | Add an enum to an existing Bootify project, identified by name. Inputs: projectId, name, appModule, featurePackage, values |
addFrontendController | 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. Inputs: projectId, name, appModule, featurePackage, path, parameters |
addIndex | 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. Inputs: entity, unique, fields, projectId |
addRelation | 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 canon Inputs: type, fromEntity, fromField, toEntity, toField, tableName |
addRestController | 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. Inputs: projectId, name, appModule, featurePackage, path, parameters |
addSecurityConfig | Create a config with safe defaults. Configure roles, login and an optional user source through their dedicated tools. Inputs: projectId, name, type, appModule, featurePackage |
configureSecurityLogin | Configure only login, JWT, Keycloak and session behavior. Provide just the fields that should change. Inputs: projectId, name, loginMethods, loginClientIds, jwtAlgorithm, keycloakRealmId |
configureSecurityUserSource | Configure 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 |
copyProject | Copy a project owned by the bearer-authenticated user. Projects with an active one-time upgrade cannot be copied. Inputs: projectId |
deleteAppModule | 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. Inputs: name, projectId |
deleteDataObject | 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/hiber Inputs: projectId, name |
deleteEntity | Delete an entity identified by name. Bootify applies its consistency rules to dependent project data. Inputs: name, projectId |
deleteEnum | Delete an enum identified by name. Referencing fields are changed to String by Bootify's consistency rules. Inputs: name, projectId |
deleteFrontendController | 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. Inputs: projectId, name |
deleteIndex | Delete an index by its current name. Inputs: name, projectId |
deleteProject | Close a project owned by the bearer-authenticated user. Inputs: projectId |
deleteRelation | 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 owners Inputs: projectId, identifier |
deleteRestController | 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. Inputs: projectId, name |
deleteSecurityConfig | Delete a security configuration by name. Inputs: projectId, name |
exportProject | 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 un Inputs: projectId |
exportProjectToGit | 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 auth Inputs: message, projectId |
getGitExportStatus | 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. Inputs: projectId |
getOpenApiPreview | 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 export Inputs: projectId |
getProject | 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 act Inputs: projectId, details |
getProjectFile | 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 Inputs: projectId, path |
importSqlSchema | Parse 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 |
linkProject | 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. Inputs: projectUrl |
listAvailableDependencies | 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. Inputs: projectId, query |
listProjectFiles | 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 fo Inputs: projectId |
listSecurityPaths | 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_ Inputs: projectId, securityConfigName |
removeBreakpoint | 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 Inputs: projectId, breakpointId |
removeDependency | Remove 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 |
setSecurityRoles | Replace the role setup. Call listSecurityPaths first and use its exact METHOD /path values. Inputs: projectId, name, roleSource, roles, roleEnum, roleFieldEnumPath |
startProject | 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 setti Inputs: name, group, buildType, language, lombokEnabled, developerPreferences |
updateAdvancedOptions | 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 applicat Inputs: projectId, modularization, multiModulePrefix, testSetup, springSession, actuatorEnabled |
updateAppModule, updateDataObject, updateDatabase, updateDatabaseNaming, updateDateFields, updateDeveloperPreferences, updateEntity, updateEnum, updateFrontend, updateFrontendController, updateIndex, updateMailSettings, updateRelation, updateRestController, updateSecurityConfig, updateSettings, updateUtilities
Every block below points at https://bootify.io/mcp. Pick your client and copy.
claude mcp add --transport http bootify https://bootify.io/mcp
{
"mcpServers": {
"bootify": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://bootify.io/mcp"]
}
}
}{
"mcpServers": {
"bootify": {
"url": "https://bootify.io/mcp"
}
}
}{
"servers": {
"bootify": {
"type": "http",
"url": "https://bootify.io/mcp"
}
}
}{
"context_servers": {
"bootify": {
"url": "https://bootify.io/mcp"
}
}
}{
"mcpServers": {
"bootify": {
"serverUrl": "https://bootify.io/mcp"
}
}
}{
"mcpServers": {
"bootify": {
"url": "https://bootify.io/mcp"
}
}
}name: Bootify
version: 0.0.1
schema: v1
mcpServers:
- name: Bootify
type: streamable-http
url: https://bootify.io/mcp{
"mcpServers": {
"bootify": {
"httpUrl": "https://bootify.io/mcp"
}
}
}{
"mcpServers": {
"bootify": {
"type": "http",
"url": "https://bootify.io/mcp"
}
}
}{
"mcpServers": {
"bootify": {
"url": "https://bootify.io/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fbootify.io%2Fmcp&type=streamable_http&id=bootify&name=Bootify
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.
Yes. It is published by bootify.io and served from bootify.io, the vendor's own domain: https://bootify.io/mcp.
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.
It answered our last check on 15 November 2026 in 80 ms. Over 4 checks since 29 September 2026 it answered 4.
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.
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.
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.