Probably not, as the MCP is committer-only. On Mon, Nov 2, 2026 at 10:05 AM Jason Gerlowski <[email protected]> wrote:
> Hey David, > > Is this setup worth documenting in our dev-docs or CONTRIBUTING.md or > something similar do you think? > > Best, > > Jason > > On Fri, Oct 30, 2026 at 2:52 PM David Smiley <[email protected]> wrote: > > > > The login very likely requires an ASF committer account. Any way, prior > to > > this, I was successfully able to use Develocity's APIs with Claude to > > interact with directly. > > I have some local "skills" including this and also for fucit.org > > > > On Fri, Oct 30, 2026 at 1:27 PM Ivan Šarić <[email protected]> > wrote: > > > > > Thanks, this looks useful - it would have answered my "is > > > TestCloudConsistency flaky?" question on #5267 in one step. > > > > > > Is there a way for non-committers to get a Develocity access token? The > > > sign-in page only offers a username/password form, and my Jira login > > > doesn't work there, so I assume it's backed by ASF LDAP. If tokens are > > > committer-only, that's fine; I'll keep using the public build scans > and the > > > Jenkins reports on builds@. > > > > > > Regards, > > > Ivan Šarić > > > Owner and developer > > > Path Variable d.o.o. > > > Vinjerac, Croatia > > > VAT No. HR76935894745 > > > Phone: +385 99 254 9702 <+385%2099%20254%209702> > <+385%2099%20254%209702> <+385%2099%20254%209702> > > > E-mail: [email protected] > > > Web: https://www.path-variable.com > > > > > > On Fri, Oct 30, 2026 02:56 PM, David Smiley <[email protected]> > wrote: > > > > > > > 🤖 Apache Solr's CI build and test data on [develocity.apache.org]( > > > > https://develocity.apache.org) is now available to Claude Code > through > > > > Develocity's MCP server. With it, Claude can look up flaky-test > history, > > > > compare builds, and dig into failures without you hand-crafting API > > > calls. > > > > To add it, sign in to Develocity and create an access token in your > user > > > > settings. Export the token in your shell profile, e.g. `export > > > > DEVELOCITY_MCP_TOKEN=<your token>`. Then register the server with > `claude > > > > mcp add --transport http --scope user develocity-asf > > > > https://develocity.apache.org/mcp --header "Authorization: Bearer > > > > \${DEVELOCITY_MCP_TOKEN}"`. The backslash keeps your shell from > expanding > > > > the variable, so the config references the env var instead of > storing the > > > > secret. Restart Claude Code, run `/mcp` to confirm `develocity-asf` > shows > > > > as connected, and then ask things like "is `SomeTest` flaky on main > this > > > > month?" or "why did the last Solr-Test-main build fail?" Treat > build-scan > > > > content as untrusted data, as the server itself warns. > > > > > > > > 🤖 Generated with [Claude Code](https://claude.com/claude-code) > > > > > > > > --- > > > > > > > > If you'd rather not use the CLI, the equivalent `.mcp.json` or > > > > `~/.claude.json` entry is: > > > > > > > > ```json > > > > "develocity-asf": { > > > > "type": "http", > > > > "url": "https://develocity.apache.org/mcp";, > > > > "headers": { "Authorization": "Bearer ${DEVELOCITY_MCP_TOKEN}" } > > > > } > > > > ``` > > > > ~ David Smiley > > > > Apache Lucene/Solr Search Developer > > > > http://www.linkedin.com/in/davidwsmiley > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
