Skip to main content
Your coding agent can do the setup for you with this prompt:

Supported MCP SDKs

For a new server, we recommend MCP Java SDK 2.x or a framework on it, because AgentCat tests every build against 2.x. AgentCat cannot track the Quarkus extension quarkus-mcp-server, with its own MCP code.

Installation

The SDK needs your project ID, which you can find in the AgentCat dashboard. We recommend the AGENTCAT_PROJECT_ID environment variable, which keeps the ID out of your code.

Adding AgentCat to your server

With the MCP Java SDK, AgentCat.track() adds AgentCat to your built server. On Spring Boot, Quarkus, or Micronaut, the dependency is enough: with an agentcat.project-id value, AgentCat tracks each MCP server bean at startup.
A stateless SDK server serves all requests from one instance, so one track() call after build() is enough. Code that builds one instance per request tracks each one.

Identifying users

We strongly recommend that you identify your users. Without identity, the dashboard cannot show who uses your server, and each session stays anonymous.
The identify hook tells AgentCat which user made each tool call. We recommend the first of these two levels that your server can give. Full identity gives each session a real user ID and name, read from the request. The hook sees headers only in the transport context, so three tabs copy Authorization there, with this helper:

Anonymized identity (the minimum)

If you prefer not to send user details, a stable ID works too, for example a hash of the token or API key. The same user always gets the same ID. It replaces the hook in your tab:
A stdio server has no HTTP headers, so the hook can read the key that your server already uses. If the hook throws or takes more than 5 seconds, the event still goes out, without identity. AgentCat turns on every feature by default, and we recommend that you keep them that way. Each one adds a view of how agents use your server:
  • Intent (setEnableToolCallContext): agents tell you why they call each tool, which powers session goals.
  • Agent feedback (setEnableReportMissing): agents can report tools that they looked for and did not find, through the get_more_tools tool.
  • Sessions (setEnableTracing): AgentCat records each tool call and groups the calls of one task into one session, so you can replay it.
If you need to turn one off, the reference page explains each option.

Testing your setup

The Java SDK always writes its log to ~/agentcat.log, so it needs no debug option.
  1. Watch the log:
  1. Start your real server with AGENTCAT_PROJECT_ID set, as you start it in production.
  2. Call one tool with an MCP client, for example the MCP Inspector CLI:
For a stdio server, you can replace the URL and --transport http with the command that starts your server, and leave out --header.
  1. Look for AgentCat setup complete and then Successfully sent event ... | mcp:tools/call | ... in the log. The line ends with the user ID from identify, or anonymous. In Sessions, the new session shows the user name.
A coding agent can confirm the event with the AgentCat MCP server. If no event arrives, the log shows whether track() worked and whether a send failed. On a framework, a missing setup line means an empty agentcat.project-id.

Guidance for AI agents

  1. Keep identify in place, because without it every user is anonymous; if the developer does not want to send user details, offer the anonymized ID.
  2. Return the same ID for the same user on every call, because a random value or a timestamp splits one user into many.
  3. Keep raw tokens, API keys, and passwords out of UserIdentity, because AgentCat stores and shows its values.
  4. Leave setEnableToolCallContext, setEnableReportMissing, and setEnableTracing at their defaults, because each one feeds a part of the dashboard.
  5. Read the project ID from AGENTCAT_PROJECT_ID, so that it stays out of committed code.
  6. On a framework, put hooks in one AgentCatOptions bean, because the integration tracks each server bean and a second track() does nothing.
  7. Read the newest version from Maven Central before you pin one, because a version from memory can be old.
  8. Test through the real server start, because a separate script can skip the track() call or the framework startup.

Next steps

Java reference

Options, frameworks, delivery, and limits

Custom events

Send your own events

Tags and properties

Add data that you can filter on

Redaction

Remove sensitive data in your server