infobip-openapi-mcp: Instructions file for Claude Code

CLAUDE.md

This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.

Project Overview

infobip-openapi-mcp is an open-source Java framework for exposing OpenAPI-documented HTTP APIs as MCP (Model Context Protocol) servers. It is built on Spring AI and Spring Boot, and is published to Maven Central.

Build & Development Commands

Project uses Java 21. Make sure that local tooling supports this version. DO NOT attempt to downgrade the source code to earlier Java versions. Look for newer JKD instead, for example using the SDKMAN version manager.

# Build the project (runs tests + spotless format check)
mvn verify

# Build skipping tests
mvn package -DskipTests

# Run all tests
mvn test

# Run tests for a specific module
mvn test -pl infobip-openapi-mcp-core
mvn test -pl infobip-openapi-mcp-spring-boot-starter -am

# Run a single test class
mvn test -pl infobip-openapi-mcp-core -Dtest=DiscriminatorFlattenerTest
mvn test -pl infobip-openapi-mcp-spring-boot-starter -am -Dtest=ToolCallIntegrationTest

# Apply code formatting (Palantir Java Format via Spotless)
mvn spotless:apply

# Check formatting without applying
mvn spotless:check

# Install git hooks (runs spotless:apply on pre-commit)
mvn install -Pgit-hook

# Check version of Java that is used by maven
mvn --version

# Check available Java versions with sdkman
PAGER=cat sdk list java | grep -E 'installed|local'

# Pick identifier of installed Java version equal or greater than 21 (for example 25-tem) and enable it with sdkman
sdk use java <identifier>

ALWAYS do this after completing any coding task:

• Run mvn spotless:apply as the final step before presenting results.
• Update CHANGELOG.md under the [Unreleased] section using the Keep a Changelog format (Added, Changed, Fixed, Removed). Write entries from a user perspective — describe the feature and its value, not the classes or internal mechanics behind it. It is fine to mention configuration properties needed to enable or customize a feature, or java interfaces that users can implement such as OpenApiFilter or ApiRequestEnricher. Avoid class names, method names, test names, and other implementation details. Before adding a new sub-section (### Changed, ### Fixed, etc.) to [Unreleased], ask: has any part of the thing being documented ever appeared in a released version? If not, it all belongs under ### Added — update or extend the existing bullet rather than creating a new sub-section. The Changed/Fixed/Removed categories are meaningful only relative to a released version, not between commits on an unreleased branch.
• If you added or changed an external configuration property, add or update its row in the properties table in README.md.
• Check and update CLAUDE.md to reflect the new state of the project.