Pack local or remote codebases into AI-friendly files that LLMs and coding agents can read or search
Bootify is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Build Spring Boot applications, ready for coding agents, including best practices.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http bootify-mcp https://bootify.io/mcp
# 2 — ask your agent for something these tools do
# startProject, getProject, linkProject and 54 more
Bootify costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http bootify-mcp https://bootify.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
57 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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 retu
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | no | A project name such as my-project |
| group | string | no | A group name such as com.my-group, used for build settings and package name |
| buildType | string | no | — |
| language | string | no | — |
| lombokEnabled | boolean | no | Ignored for Kotlin projects |
| developerPreferences | object | no | — |
| database | object | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| projectId | string | yes | The project ID returned by startProject |
| details | array | no | Without details, only basic configuration and plan information are returned. Select additional areas explicitly, for example ENTITIES, RELATIONS and INDEXES. APP_MODULES, BREAKPOINTS, REST_CONTROLLERS |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| projectUrl | string | yes | The project URL or 12-character project ID |
Copy a project owned by the bearer-authenticated user. Projects with an active one-time upgrade cannot be copied.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| projectId | string | yes | The project ID returned by startProject |
Close a project owned by the bearer-authenticated user.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| projectId | string | yes | The project ID returned by startProject |
Update one or more basic settings of an existing Bootify project. Background information: https://bootify.io/docs/general-tab.html
| Parameter | Type | Required | Notes |
|---|---|---|---|
| projectId | string | yes | The project ID returned by startProject |
| name | string | no | A project name such as my-project |
| group | string | no | A group name such as com.my-group, used for build settings and package name |
| buildType | string | no | — |
| language | string | no | — |
| lombokEnabled | boolean | no | Ignored for Kotlin projects |
Update one or more developer preferences of an existing Bootify project. Background information: https://bootify.io/docs/general-tab.html
| Parameter | Type | Required | Notes |
|---|---|---|---|
| projectId | string | yes | The project ID returned by startProject |
| applicationFormat | string | no | Format of the generated Spring application configuration |
| packageStructure | string | no | Package layout: TECHNICAL groups classes by technical type in packages such as domain, repos, service and rest; DOMAIN_DRIVEN groups all classes related to an entity in a package named after that enti |
| includeAgentInstructions | boolean | no | Generate AGENTS.md with coding agent instructions |
| openApiEnabled | boolean | no | Generate OpenAPI documentation and Swagger UI |
| dockerComposeEnabled | boolean | no | Generate Docker Compose support for local development |
| javaVersion | integer | no | — |
| deployment | string | no | — |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| projectId | string | yes | The project ID returned by startProject |
| modularization | string | no | NONE generates a monolith; MODULITH and MULTI_MODULE activate the application-module graph |
| multiModulePrefix | boolean | no | Prefix generated module artifact names with the project name in MULTI_MODULE mode |
| testSetup | string | no | Generated test setup |
| springSession | string | no | Spring Session persistence; JDBC uses the configured relational or embedded database |
| actuatorEnabled | boolean | no | Add Spring Boot Actuator |
| actuatorEndpoints | array | no | Actuator endpoints to expose; an empty list exposes all available endpoints |
| hateoasEnabled | boolean | no | Use HATEOAS for the REST API |
| mapStructEnabled | boolean | no | Use MapStruct instead of generated mapping code |
| serviceInterfaceEnabled | boolean | no | Generate separate service interfaces and implementations |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| projectId | string | yes | The project ID returned by startProject |
| includeFileHandling | boolean | no | Include file handling services and database storage |
| includeInputRow | boolean | no | Include inputRow and supporting form utilities; requires Thymeleaf, jte, Angular or React |
| includePaginationAndSorting | boolean | no | Include frontend pagination and sorting utilities; requires a frontend framework |
| includeSearchFilter | boolean | no | Include frontend search filter utilities; requires a frontend framework |
Available with Bootify Professional. Enable or disable mail support and configure the generated application's SMTP connection.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| projectId | string | yes | The project ID returned by startProject |
| enabled | boolean | no | — |
| connection | string | no | — |
| host | string/null | no | — |
| username | string/null | no | — |
| from | string/null | no | — |
| displayName | string/null | no | — |
Update one or more frontend settings of an existing Bootify project. Background information: https://bootify.io/docs/frontend-settings.html
| Parameter | Type | Required | Notes |
|---|---|---|---|
| projectId | string | yes | The project ID returned by startProject |
| framework | string | no | — |
| buildTool | string | no | — |
| cssFramework | string | no | — |
| htmxEnabled | boolean | no | Used only with Thymeleaf and JTE |
| typescriptEnabled | boolean | no | Used only with Vite or Webpack for Thymeleaf and JTE |
Update the database and schema management settings of an existing Bootify project. Background information: https://bootify.io/docs/general-tab.html
| Parameter | Type | Required | Notes |
|---|---|---|---|
| projectId | string | yes | The project ID returned by startProject |
| type | string | no | — |
| schemaType | string | no | — |
| mongoSchemaType | string | no | — |
Update one or more database naming settings of an existing Bootify project. Background information: https://bootify.io/docs/general-tab.html
| Parameter | Type | Required | Notes |
|---|---|---|---|
| projectId | string | yes | The project ID returned by startProject |
| namingStrategy | string | no | — |
| pluralizeTableName | boolean | no | — |
| tablePrefix | string/null | no | — |
| tableSuffix | string/null | no | — |
Enable or disable generated date fields and configure their names. Background information: https://bootify.io/docs/general-tab.html
| Parameter | Type | Required | Notes |
|---|---|---|---|
| projectId | string | yes | The project ID returned by startProject |
| enabled | boolean | no | — |
| dateCreatedName | string | no | — |
| lastUpdatedName | string | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| projectId | string | yes | The project ID returned by startProject |
| query | string | no | Optional case-insensitive text contained in the coordinates |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| projectId | string | yes | The project ID returned by startProject |
| dependency | string | yes | Maven coordinates: groupId:artifactId[:version] |
Remove a dependency from the generated Maven or Gradle build using groupId:artifactId. A version may be supplied but is not used for matching.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| projectId | string | yes | The project ID returned by startProject |
| dependency | string | yes | Maven coordinates: groupId:artifactId[:version] |
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 cus
| Parameter | Type | Required | Notes |
|---|---|---|---|
| projectId | string | yes | The project ID returned by startProject |
| name | string | yes | Name of the new custom module |
| references | array | no | Unique names of existing custom modules used as direct dependencies. References already available through another selected module are removed automatically. Omit or use an empty array to depend on the |
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 integ
| Parameter | Type | Required | Notes |
|---|---|---|---|
| projectId | string | yes | The project ID returned by startProject |
| name | string | yes | Current name of the custom module |
| newName | string | no | New module name; omit to keep its name |
| references | array | no | Unique names of existing custom modules used as direct dependencies. References already available through another selected module are removed automatically. Omit or use an empty array to depend on the |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| projectId | string | yes | The project ID returned by startProject |
| name | string | yes | Name of the custom module to delete |
Add an enum to an existing Bootify project, identified by name.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| projectId | string | yes | The project ID returned by startProject |
| name | string | yes | Name of the new enum |
| appModule | string/null | no | Custom app module name; null selects base. Available with Bootify Professional. |
| featurePackage | string/null | no | Optional dot-separated package path for domain-driven or mixed structure; null uses automatic assignment |
| values | array | yes | Ordered, unique enum values such as DRAFT and PUBLISHED |
Update or rename an enum identified by its current name. Provide newName, values, appModule, featurePackage, or several.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| projectId | string | yes | The project ID returned by startProject |
| name | string | yes | Current name of the enum to update |
| newName | string | no | New enum name; omit to keep the current name |
| appModule | string/null | no | Custom app module name; null selects base. Available with Bootify Professional. |
| featurePackage | string/null | no | Optional dot-separated package path for domain-driven or mixed structure; null uses automatic assignment |
| values | array | no | Ordered, unique enum values such as DRAFT and PUBLISHED |
Delete an enum identified by name. Referencing fields are changed to String by Bootify's consistency rules.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| projectId | string | yes | The project ID returned by startProject |
| name | string | yes | Name of the enum to delete |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| projectId | string | yes | The project ID returned by startProject |
| name | string | yes | Name of the new data object |
| appModule | string/null | no | Custom app module; null selects base. Available with Bootify Professional. |
| featurePackage | string/null | no | Optional dot-separated package path for domain-driven or mixed structure; null uses automatic assignment |
| fields | array | yes | Complete ordered data object field list. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| projectId | string | yes | The project ID returned by startProject |
| name | string | yes | Current name of the data object |
| newName | string | no | New data object name; omit to keep its name |
| appModule | string/null | no | Custom app module; null selects base. Available with Bootify Professional. |
| featurePackage | string/null | no | Optional dot-separated package path for domain-driven or mixed structure; null uses automatic assignment |
| fields | array | no | Complete ordered data object field list. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| projectId | string | yes | The project ID returned by startProject |
| name | string | yes | Current name of the data object |
Add an entity to an existing Bootify project. Entity, field, module, inheritance and custom field-type references use names.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| appModule | string/null | no | App module name; null selects the base module. Available with Bootify Professional. |
| featurePackage | string/null | no | Optional dot-separated package path for domain-driven or mixed structure; null uses automatic assignment |
| superclass | boolean | no | — |
| inherits | string/null | no | Name of the superclass entity; null removes inheritance |
| restEnabled | boolean | no | — |
| frontendEnabled | boolean | no | — |
| paginationEnabled | boolean | no | — |
| searchFilterEnabled | boolean | no | — |
| fields | array | yes | Complete ordered entity field list. Exactly one primary key is required for a concrete entity unless inherited; abstract superclasses may omit it. A primary key must be the first field and use INTEGER |
| projectId | string | yes | The project ID returned by startProject |
| name | string | yes | Name of the new entity |
Update or rename an entity identified by its current name. Only provided properties are changed; a provided fields array replaces all fields.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| appModule | string/null | no | App module name; null selects the base module. Available with Bootify Professional. |
| featurePackage | string/null | no | Optional dot-separated package path for domain-driven or mixed structure; null uses automatic assignment |
| superclass | boolean | no | — |
| inherits | string/null | no | Name of the superclass entity; null removes inheritance |
| restEnabled | boolean | no | — |
| frontendEnabled | boolean | no | — |
| paginationEnabled | boolean | no | — |
| searchFilterEnabled | boolean | no | — |
| fields | array | no | Complete ordered entity field list. Exactly one primary key is required for a concrete entity unless inherited; abstract superclasses may omit it. A primary key must be the first field and use INTEGER |
| projectId | string | yes | The project ID returned by startProject |
| name | string | yes | Current name of the entity to update |
| newName | string | no | New entity name; omit to keep the current name |
Delete an entity identified by name. Bootify applies its consistency rules to dependent project data.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| projectId | string | yes | The project ID returned by startProject |
| name | string | yes | Name of the entity to delete |
Parse SQL DDL and reconcile its tables, fields and relations with an existing Bootify project. Matching entities are updated and new entities are added.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| projectId | string | yes | The project ID returned by startProject |
| sql | string | yes | SQL DDL containing CREATE TABLE statements |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| projectId | string | yes | The project ID returned by startProject |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| projectId | string | yes | The project ID returned by startProject |
| breakpointId | string | yes | — |
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-e
| Parameter | Type | Required | Notes |
|---|---|---|---|
| type | string | yes | Cardinality from fromEntity to toEntity |
| fromEntity | string | yes | Entity on the from side of the cardinality |
| fromField | string/null | no | Field generated on fromEntity. Required unless an unidirectional ONE_TO_MANY relation omits this reverse field |
| toEntity | string | yes | Entity on the to side of the cardinality |
| toField | string/null | no | Field generated on toEntity. Required for ONE_TO_MANY and bidirectional relations; also required for self-referencing MANY_TO_MANY relations |
| tableName | string/null | no | Join-table name; required only for MANY_TO_MANY |
| required | boolean | no | Whether the owning foreign key is required. Not applicable to MANY_TO_MANY or self-relations |
| unidirectional | boolean | no | Omit the reverse field. Relations across application modules must be unidirectional |
| projectId | string | yes | The project ID returned by startProject |
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-wit
| Parameter | Type | Required | Notes |
|---|---|---|---|
| type | string | no | Cardinality from fromEntity to toEntity |
| fromEntity | string | no | Entity on the from side of the cardinality |
| fromField | string/null | no | Field generated on fromEntity. Required unless an unidirectional ONE_TO_MANY relation omits this reverse field |
| toEntity | string | no | Entity on the to side of the cardinality |
| toField | string/null | no | Field generated on toEntity. Required for ONE_TO_MANY and bidirectional relations; also required for self-referencing MANY_TO_MANY relations |
| tableName | string/null | no | Join-table name; required only for MANY_TO_MANY |
| required | boolean | no | Whether the owning foreign key is required. Not applicable to MANY_TO_MANY or self-relations |
| unidirectional | boolean | no | Omit the reverse field. Relations across application modules must be unidirectional |
| projectId | string | yes | The project ID returned by startProject |
| identifier | string | yes | Current identifier copied verbatim from addRelation, updateRelation or getProject RELATIONS |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| projectId | string | yes | The project ID returned by startProject |
| identifier | string | yes | Current identifier copied verbatim from addRelation, updateRelation or getProject RELATIONS |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| entity | string | yes | Entity containing the indexed fields or owning-side relations |
| unique | boolean | yes | Whether the index enforces a unique field combination |
| fields | array | yes | Ordered field or owning-side relation names. Order affects index usage; many-to-many relations are not available and a primary key cannot be used alone. |
| projectId | string | yes | The project ID returned by startProject |
Update an index by its current Entity.field1-field2 identifier. Only provided properties are changed; the response contains its updated identifier.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| entity | string | no | Entity containing the indexed fields or owning-side relations |
| unique | boolean | no | Whether the index enforces a unique field combination |
| fields | array | no | Ordered field or owning-side relation names. Order affects index usage; many-to-many relations are not available and a primary key cannot be used alone. |
| projectId | string | yes | The project ID returned by startProject |
| name | string | yes | Current Entity.field1-field2 identifier |
Delete an index by its current name.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| projectId | string | yes | The project ID returned by startProject |
| name | string | yes | Current Entity.field1-field2 identifier |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| projectId | string | yes | The project ID returned by startProject |
| name | string | yes | Name of the new REST controller |
| appModule | string/null | no | Custom application module name; null selects the web module |
| featurePackage | string/null | no | Optional dot-separated package path for domain-driven or mixed structure; null uses automatic assignment |
| path | string | yes | Controller base path, with optional {name} placeholders |
| parameters | array | yes | Types for every placeholder and query declaration, in the same order as path. Bootify derives whether each parameter is a path or query parameter. |
| endpoints | array | yes | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| projectId | string | yes | The project ID returned by startProject |
| name | string | yes | Current name of the REST controller |
| newName | string | no | New controller name; omit to keep its name |
| appModule | string/null | no | Custom application module name; null selects the web module |
| featurePackage | string/null | no | Optional dot-separated package path for domain-driven or mixed structure; null uses automatic assignment |
| path | string | no | Controller base path, with optional {name} placeholders |
| parameters | array | no | Types for every placeholder and query declaration, in the same order as path. Bootify derives whether each parameter is a path or query parameter. |
| endpoints | array | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| projectId | string | yes | The project ID returned by startProject |
| name | string | yes | Current name of the REST 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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| projectId | string | yes | The project ID returned by startProject |
| name | string | yes | Name of the new frontend controller |
| appModule | string/null | no | Custom application module name; null selects the web module |
| featurePackage | string/null | no | Optional dot-separated package path for domain-driven or mixed structure; null uses automatic assignment |
| path | string | yes | Controller base path, with optional {name} placeholders |
| parameters | array | yes | Types for every placeholder and query declaration, in the same order as path. Bootify derives whether each parameter is a path or query parameter. |
| endpoints | array | yes | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| projectId | string | yes | The project ID returned by startProject |
| name | string | yes | Current name of the frontend controller |
| newName | string | no | New controller name; omit to keep its name |
| appModule | string/null | no | Custom application module name; null selects the web module |
| featurePackage | string/null | no | Optional dot-separated package path for domain-driven or mixed structure; null uses automatic assignment |
| path | string | no | Controller base path, with optional {name} placeholders |
| parameters | array | no | Types for every placeholder and query declaration, in the same order as path. Bootify derives whether each parameter is a path or query parameter. |
| endpoints | array | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| projectId | string | yes | The project ID returned by startProject |
| name | string | yes | Current name of the frontend controller |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| projectId | string | yes | The project ID returned by startProject |
| securityConfigName | string | no | Existing config being edited |
Create a config with safe defaults. Configure roles, login and an optional user source through their dedicated tools.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| projectId | string | yes | The project ID returned by startProject |
| name | string | yes | Security config name |
| type | string | yes | — |
| appModule | string/null | no | Custom app module; null selects base |
| featurePackage | string/null | no | Optional dot-separated package path for domain-driven or mixed structure; null uses automatic assignment |
Change only the identity, type, module or authentication mode. Changing type resets type-specific settings to defaults.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| projectId | string | yes | The project ID returned by startProject |
| name | string | yes | Current config name |
| newName | string | no | New config name |
| type | string | no | — |
| appModule | string/null | no | Custom app module; null selects base |
| featurePackage | string/null | no | Optional dot-separated package path for domain-driven or mixed structure; null uses automatic assignment |
| authenticationMethod | string | no | — |
Configure only login, JWT, Keycloak and session behavior. Provide just the fields that should change.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| projectId | string | yes | The project ID returned by startProject |
| name | string | yes | Security config name |
| loginMethods | array | no | — |
| loginClientIds | object | no | — |
| jwtAlgorithm | string/null | no | — |
| keycloakRealmId | string/null | no | — |
| keycloakClientId | string/null | no | — |
| rememberMe | string/null | no | — |
| registrationEndpoint | boolean | no | — |
Configure the user entity and its credential, OAuth mapping, password reset and token fields. Provide just the fields that should change.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| projectId | string | yes | The project ID returned by startProject |
| name | string | yes | Security config name |
| sourceEntity | string/null | no | User source entity; null uses in-memory users |
| usernameField | string/null | no | — |
| hashField | string/null | no | — |
| externalIdField | string/null | no | — |
| loginTypeField | string/null | no | — |
| resetUidField | string/null | no | — |
| resetStartField | string/null | no | — |
| mapEmailField | string/null | no | — |
| mapFirstNameField | string/null | no | — |
| mapLastNameField | string/null | no | — |
| refreshTokenPath | string/null | no | — |
| refreshTokenExpiryPath | string/null | no | — |
Replace the role setup. Call listSecurityPaths first and use its exact METHOD /path values.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| projectId | string | yes | The project ID returned by startProject |
| name | string | yes | Security config name |
| roleSource | string | yes | — |
| roles | array | yes | — |
| roleEnum | string/null | no | Enum supplying role names |
| roleFieldEnumPath | string/null | no | — |
Delete a security configuration by name.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| projectId | string | yes | The project ID returned by startProject |
| name | string | yes | Security config to delete |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| projectId | string | yes | The project ID returned by startProject |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| projectId | string | yes | The project ID returned by startProject |
Return one generated project file. The path must exactly match a value returned by listProjectFiles. 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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| projectId | string | yes | The project ID returned by startProject |
| path | string | yes | An exact generated path returned by listProjectFiles |
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 fa
| Parameter | Type | Required | Notes |
|---|---|---|---|
| projectId | string | yes | The project ID returned by startProject |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| projectId | string | yes | The project ID returned by startProject |
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 c
| Parameter | Type | Required | Notes |
|---|---|---|---|
| projectId | string | yes | — |
| message | string | no | — |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Bootify or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Bootify can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.