Oauth2 Authorization Server MCP Server

OAuth2 Authorization Server with MariaDB, Docker OpenTelemetry LGTM, and Redis Integrations with Spring Boot 4, Java 25 and Docker. Integration Tests with Testcontainers and unit Tests with Junit 5, and Mockito. Exposed over MCP by the oauth2 authorization server mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

1. Run one of the below commands in the terminal - mvn test -Dmaven.surefire.debug - If port 5005 is already in use, you can specify a custom port - mvn test -Dmaven.surefire.debug="-Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=8000" 2. Open IntelliJ IDEA 3. Go to Run > Attach to Process (or use shortcut) - Windows/Linux: Ctrl + Alt + 5 - Mac: Cmd + Alt + 5 4. Select the Java process running your tests 5. The test will pause until you connect your debugger. Once connected, you can use breakpoints and step through your code.

Its toolset

Everything the assistant can do here goes through one of these:

• Swagger — http://localhost:9000/swagger-ui/index.html
• client_id — client
• client_secret — secret
• username — Developer password: password
• Actuator — http://localhost:9000/actuator/
• url — jdbc:mariadb://localhost:3306/oauth2_authorization_server
• password — test
• Redis — host: localhost
• port — 6379
• Ollama — http://localhost:3000/ sign up for an account for local environment
• Mac — Cmd + Alt + 5
• Warning — ** for real projects make sure to not leak sensitive data in CRaC files since they contain a snapshot of the

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Configuration

You will need 5 environment variables: JAVA_HOME, OPENAI_API_KEY, DEEPSEEK_API_KEY, ANTHROPIC_API_KEY, GOOGLE_GENAI_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• Java 25 should be installed --> export JAVA_HOME=$(/usr/libexec/java_home -v 25) - Maven should be installed - Docker should be installed - Postman can be installed

When to reach for it

Plenty of database access servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Oauth2 Authorization Server's toolset — Swagger, client_id, client_secret and 11 more — is a fair guide to whether it matches your workflow. It is maintained by musabbozkurt; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Oauth2 Authorization Server.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the oauth2 authorization server mcp server does with a few real requests.