We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/keyurgolani/TasksMultiServer'
If you have feedback or need assistance with the MCP directory API, please join our Discord server
pull_request_template.md•2.11 kB
## Description
<!-- Provide a brief description of the changes in this PR -->
## Type of Change
<!-- Mark the relevant option with an "x" -->
- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
- [ ] Documentation update
- [ ] Refactoring (no functional changes)
- [ ] Performance improvement
- [ ] Test coverage improvement
- [ ] CI/CD changes
## Related Issues
<!-- Link to related issues using #issue_number -->
Fixes #
Relates to #
## Changes Made
<!-- List the main changes made in this PR -->
-
-
-
## Testing
<!-- Describe the testing you've done -->
### Unit Tests
- [ ] All existing unit tests pass
- [ ] New unit tests added for new functionality
- [ ] Coverage remains above 82%
### Integration Tests
- [ ] All integration tests pass
- [ ] New integration tests added if applicable
### Manual Testing
- [ ] Tested locally with filesystem backing store
- [ ] Tested locally with PostgreSQL backing store
- [ ] Tested MCP server interface
- [ ] Tested REST API interface
- [ ] Tested React UI interface
## Checklist
<!-- Mark completed items with an "x" -->
- [ ] Code follows the project's style guidelines
- [ ] Code has been formatted with Black and isort
- [ ] Linting passes (pylint, flake8)
- [ ] Type checking passes (mypy)
- [ ] All tests pass locally
- [ ] Documentation has been updated (if applicable)
- [ ] No new security vulnerabilities introduced (pip-audit passes)
- [ ] Commit messages are clear and descriptive
- [ ] PR title follows conventional commits format
## Screenshots (if applicable)
<!-- Add screenshots for UI changes -->
## Additional Notes
<!-- Any additional information that reviewers should know -->
## Reviewer Checklist
<!-- For reviewers to complete -->
- [ ] Code review completed
- [ ] Tests are adequate and pass
- [ ] Documentation is clear and complete
- [ ] No security concerns
- [ ] Performance impact is acceptable
- [ ] Breaking changes are documented