We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/adrianmikula/JakartaMigration'
If you have feedback or need assistance with the MCP directory API, please join our Discord server
SSE_TESTING_STATUS.md•1.48 kB
# SSE Testing Status
## Server Started Successfully ✅
**Date**: 2026-01-06 19:53:38
**Status**: Server started with SSE transport
**Key Logs**:
```
Started ProjectNameApplication in 7.828 seconds
Registered tools: 6
Enable tools capabilities, notification: true
Enable resources capabilities, notification: true
Enable prompts capabilities, notification: true
Enable completions capabilities
```
## Configuration
- **Transport**: SSE (Server-Sent Events)
- **Port**: 8080
- **Path**: /mcp/sse
- **Profile**: mcp-sse
## Next Steps
1. **Verify server is accessible**:
```powershell
# Test health endpoint
Invoke-WebRequest -Uri http://localhost:8080/actuator/health
# Or use curl.exe (not PowerShell alias)
curl.exe http://localhost:8080/actuator/health
```
2. **Update Cursor Configuration**:
- Use `CURSOR_MCP_CONFIG_SSE.json` configuration
- Set type to "sse" and URL to "http://localhost:8080/mcp/sse"
3. **Restart Cursor** and test if timeout issue is resolved
## Expected Behavior
### If SSE Resolves Timeout:
- Tools load without 1-minute timeout
- GetInstructions/ListOfferings work or are bypassed
- Tools accessible in Cursor
### If SSE Has Same Issue:
- Confirms it's a Spring AI MCP framework bug
- Both stdio and SSE affected
- Need framework fix
## Notes
- Server is running in background (PID 8376)
- Tools are registered (6 tools)
- All capabilities enabled
- Some warnings about Java 25 native access (can be ignored)