Recommend and install MCP servers for Gravitee APIM development — GitHub, databases, Docker, and more
You are running the /gravitee-dev-workflow:install-mcp-servers skill. Follow these instructions to recommend and install MCP servers.
Present the following categorized list to the Dev:
| Server | Note |
|---|---|
github |
| Official GitHub MCP server — manage repos, PRs, issues, and code reviews directly from the terminal. Required for any GitHub-based workflow. |
| Server | Note |
|---|---|
mongodb | Official MongoDB MCP server — query collections, inspect schemas, and manage data in the Gravitee persistence layer. Default APIM database. |
elasticsearch | Official Elastic MCP server — search indices, analyze mappings, and query the Gravitee analytics backend. |
postgres | PostgreSQL MCP server — for teams using the JDBC alternative to MongoDB. Query tables, explore schemas. |
| Server | Note |
|---|---|
docker | Manage Docker containers from Claude Code — inspect running APIM services, view logs, restart containers without leaving the terminal. |
| Server | Note |
|---|---|
atlassian | Official Atlassian MCP server — read Jira issues, update ticket status, and link PRs to stories. Connects via OAuth. |
| Server | Note |
|---|---|
maven-tools | Maven Central dependency intelligence — check dependency freshness, find latest versions, and analyze release history for Gravitee's Java dependencies. |
| Server | Note |
|---|---|
sentry | Connect to Sentry for real-time error monitoring — view stack traces, track regressions, and analyze production issues from Claude Code. |
Ask the Dev:
Which database backend does your APIM setup use?
- MongoDB + Elasticsearch (default)
- PostgreSQL + Elasticsearch (JDBC alternative)
- All three (MongoDB, PostgreSQL, and Elasticsearch)
Pre-select the relevant database servers based on their answer for the next step.
Ask the Dev which MCP servers they want to install. Present it as a multi-select with the database servers pre-selected based on Step 2. They can pick individual servers, entire categories, or "all".
Do NOT proceed until the Dev has made their selection.
For each selected server, run the corresponding install command:
GitHub:
claude mcp add --transport http github https://api.githubcopilot.com/mcp/
MongoDB:
claude mcp add --transport stdio mongodb --env MONGODB_URI=mongodb://localhost:27017/gravitee -- npx -y @mongodb-mcp/server
Elasticsearch:
claude mcp add --transport stdio elasticsearch --env ELASTICSEARCH_URL=http://localhost:9200 -- npx -y @elastic/mcp-server-elasticsearch
PostgreSQL:
claude mcp add --transport stdio postgres --env DATABASE_URL=postgresql://grvt:pswd@localhost:5432/gravitee -- npx -y postgres-mcp
Docker:
claude mcp add --transport stdio docker -- npx -y docker-mcp
Atlassian:
claude mcp add --transport http atlassian https://mcp.atlassian.com/mcp
Maven Tools:
claude mcp add --transport stdio maven-tools -- npx -y maven-tools-mcp
Sentry:
claude mcp add --transport http sentry https://mcp.sentry.dev/mcp
Track the outcome of each install: installed / already present / failed.
For servers that require authentication, remind the Dev:
Authentication required: The following servers need you to authenticate before they can be used. Run
/mcpand complete the auth flow for each:
List only the servers that were actually installed and need auth (GitHub, Atlassian, Sentry).
Print a checklist of all selected servers with their outcomes:
## MCP Server Installation Summary
- [x] github — installed (run /mcp to authenticate)
- [x] mongodb — installed
- [x] elasticsearch — installed
- [ ] docker — failed (reason)
...
If any servers use placeholder connection strings (like the PostgreSQL DATABASE_URL or MongoDB MONGODB_URI), remind the Dev:
Connection strings: Some servers were installed with default connection strings. If your local setup uses different ports or credentials, update them via
/mcp.
Then congratulate the Dev on completing the onboarding journey:
Setup complete! You've finished the Gravitee APIM onboarding journey. Your dev environment, Claude Code plugins, and external integrations are all configured. Start coding, or run
/gravitee-dev-workflow:helloany time to see all available skills.