JavaBytes
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JAVABYTES_DB_URL | No | MySQL JDBC URL. Default is jdbc:mysql://localhost:3306/mydb. | |
| JAVABYTES_ENABLE | No | Enable/disable tools by group or name. Defaults to the category defaults. | |
| JAVABYTES_DB_USER | No | MySQL user. Default is user. | |
| JAVABYTES_DISABLE | No | Disable specific tools. Defaults to the category defaults. | |
| JAVABYTES_LOG_FILE | No | Optional JSON-RPC trace log. Unset by default. | |
| JAVABYTES_DB_PASSWORD | No | MySQL password. Default is password. | |
| JAVABYTES_ALLOWED_DIRS | No | Fallback filesystem sandbox roots. Defaults to the working directory plus the JVM temp directory. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
JavaBytes is a general-purpose Java tool server. It does not require an MCP SDK.
Environment:
File tools are sandboxed to the client's MCP roots when the client advertises them, otherwise to JAVABYTES_ALLOWED_DIRS, otherwise to the working directory plus the JVM temporary directory. Paths outside the current sandbox are rejected.
Database tools are read-only: one SELECT/SHOW/DESCRIBE/EXPLAIN/WITH statement, capped at 1000 rows with a query timeout.
Workflow:
Inspect before changing: get_version, list_services, get_file_info, read_text_file, search_files.
Prefer evidence over guesses. project_diagnostic and analyze_springboot_project report what they actually found; they do not invent missing dependencies.
Generation tools emit templates. They do not compile, run, or verify their output. Write the result and verify it with your own build or test command.
Keep file edits inside the sandbox; ask the user for a new root instead of escaping it.
Tool groups:
Enabled by default: files, database, system, json, javafx, analysis, diagnostics.
Opt-in generators: ui, design, codegen, springboot. Enable groups or individual tools with JAVABYTES_ENABLE=springboot,codegen (or "all"); disable with JAVABYTES_DISABLE=. A tool disabled by name always wins.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| javafx_draw_canvasB | Draw shapes and primitives onto the active off-screen canvas. |
| explain_queryB | Run MySQL EXPLAIN (or EXPLAIN ANALYZE) on a read-only SELECT and return the plan. |
| verify_generatedA | Deterministic antislop gate: checks generated Java files for TODO comments, raw types, missing nullability annotations, var in fields, missing Javadoc, and Object return types. Runs as a pipeline gate before Prove (compile + start). |
| extract_design_systemC | Extract colors, typography and spacing tokens from CSS or HTML into a design system. |
| fix_allC | Run all diagnostics, apply safe fixes and summarize what changed. |
| analyze_schema_normalizationA | Review keys, foreign keys, indexes and sampled list-like columns for likely normal-form problems. |
| delete_fileA | Delete a file or an empty directory inside an allowed directory. |
| create_mysql_clientB | Generate a MySQL JDBC client helper class with safe connection handling. |
| environment_variablesA | List, read or explain environment variables. Secret-like values are masked. |
| fix_maven_dependenciesB | Detect and report incorrect or missing Maven dependencies with suggested fixes. |
| list_directoryB | List the entries of a directory with type and size information. |
| write_fileA | Create or overwrite a text file inside an allowed directory. |
| extract_data_modelsA | Parse mongoose, prisma, sequelize, SQL or JSON data declarations into tables and columns, with per-field confidence and an honest limitations list. |
| javafx_export_imageC | Export the active off-screen canvas to a PNG image file. |
| describe_tableB | Describe the columns, types, keys and defaults of a database table. |
| analyze_javascriptA | Inventory a JS/TS file or project: frameworks, npm dependencies, routes, components, browser APIs and migration risks. |
| read_text_fileB | Read a UTF-8 text file inside an allowed directory and return its contents. |
| javafx_clear_canvasB | Clear the active off-screen canvas. |
| project_diagnosticA | Check a project for build, dependency and configuration problems without modifying it. |
| get_system_infoA | Report JVM, operating-system and hardware information. |
| get_file_infoA | Return existence, type, size, timestamps and permissions for a path. |
| list_servicesA | List all tools currently registered by this JavaBytes server. |
| find_todosB | Find TODO, FIXME and HACK markers in a source tree. |
| javafx_init_canvasA | Create an off-screen JavaFX canvas with the given width and height. |
| models_to_schemaA | Convert parsed schema models into normalized schema proposals: proposed DDL, pass-through verdicts, and a verification list of medium/low-confidence fields. |
| check_securityA | Scan Java source for common security issues such as injection and weak crypto. |
| query_databaseB | Run a read-only SQL query against the configured MySQL database and return rows. |
| javafx_set_colorA | Set the current fill or stroke color used by canvas drawing operations. |
| get_versionA | Return the JavaBytes server and Java runtime versions. |
| make_directoryA | Create a directory and any missing parents inside an allowed directory. |
| analyze_springboot_projectB | Inspect a Spring Boot project and report missing layers, configuration and dependency issues. |
| backup_fileA | Copy a file to a timestamped sibling backup without overwriting existing backups. |
| list_tablesB | List the tables and views in the configured MySQL database. |
| convert_timeA | Convert a timestamp between time zones or between epoch and ISO-8601 formats. |
| analyze_codeB | Analyze Java source for complexity, smells and structural problems. |
| list_foreign_keysA | List foreign keys with referenced tables, columns and delete/update rules. |
| html_css_to_javafx_cssA | Translate HTML/CSS declarations into valid JavaFX CSS and report unsupported properties. |
| export_schema_ddlA | Export SHOW CREATE TABLE DDL for one table or every base table. |
| json_queryB | Query a JSON document with a dot/bracket path and optionally return pretty output. |
| compare_filesB | Compare two text files and report whether they differ, with a diff summary. |
| fix_javafx_headlessB | Detect and explain headless JavaFX problems and generate the required configuration. |
| generate_databaseA | Execute proposed normalized DDL against a user-supplied JDBC URL to create the schema (creates only; refuses existing-table collision unless confirm=true). |
| search_filesC | Find files by glob name pattern and, optionally, a regular expression on their contents. |
| list_indexesA | List indexes, uniqueness and column order for a table or the whole schema. |
| analyze_ui_layoutB | Analyze a UI layout description and report spacing, hierarchy and accessibility concerns. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 45 tools
Most tools target distinct resources (file ops, MySQL introspection, JavaFX canvas ops), but the diagnostic/analysis cluster is muddy: analyze_code, check_security, verify_generated, project_diagnostic, fix_all, find_todos, analyze_springboot_project and fix_maven_dependencies all sound like 'scan the project and report problems', so an agent could easily pick the wrong one. The mix of unrelated domains (time conversion, json_query, JS analysis) alongside Java tooling further blurs the set's center of gravity.
The dominant pattern is snake_case verb_noun (list_tables, describe_table, export_schema_ddl, write_file, search_files), applied consistently enough to be predictable. A handful of noun-phrase or X_to_Y names (environment_variables, project_diagnostic, models_to_schema, html_css_to_javafx_css) break the verb-first convention but remain clear.
45 tools is well past the comfortable range and the surface spans at least five unrelated domains (MySQL, file system, Java/JS static analysis, JavaFX canvas rendering, system/utility helpers). It reads as several servers bundled into one rather than a scoped toolset, making discovery and selection costly.
Each individual domain is partly covered — DB introspection is strong (tables, indexes, FKs, DDL, explain, generation) and file ops near-complete — but there are visible gaps: no ALTER/DML path for databases, no compose/run step linking verify_generated to a build, and no canvas dispose/teardown after javafx_init_canvas. Coverage is broad but shallow and uneven across the bundled domains.