We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/trsdn/markitdown-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server
README.md•1.95 kB
# Documentation
This directory contains comprehensive documentation for the MarkItDown MCP server.
## 📁 Documentation Structure
### `/api/`
API documentation and technical specifications
- Tool schemas and parameters
- MCP protocol implementation details
- Response formats and error codes
### `/development/`
Development and contribution documentation
- **[CONTRIBUTING.md](development/CONTRIBUTING.md)** - How to contribute to the project
- **[TESTING_STRATEGY.md](development/TESTING_STRATEGY.md)** - Testing approach and guidelines
- **[CI_CD_SYSTEM.md](development/CI_CD_SYSTEM.md)** - Complete CI/CD architecture and workflows
### `/guides/`
User guides and troubleshooting
- **[KNOWN_ISSUES.md](guides/KNOWN_ISSUES.md)** - Known issues and workarounds
- Installation guides
- Configuration tutorials
## 📖 Quick Links
### For Users
- [Main README](../README.md) - Project overview and quick start
- [Configuration Examples](../examples/) - MCP client configurations
- [Known Issues](guides/KNOWN_ISSUES.md) - Common problems and solutions
### For Developers
- [Contributing Guide](development/CONTRIBUTING.md) - How to contribute
- [Testing Strategy](development/TESTING_STRATEGY.md) - Testing approach
- [AGENTS Documentation](../AGENTS.md) - AI agent integration guide
### For API Consumers
- [Tool Documentation](api/) - Detailed tool specifications
- [MCP Protocol](api/) - Protocol implementation details
## 🔄 Documentation Updates
This documentation is maintained alongside the codebase. When making changes:
1. Update relevant documentation files
2. Add new guides for significant features
3. Update the changelog for documentation changes
4. Ensure examples remain current with code changes
## 📋 Documentation Standards
- Use clear, concise language
- Include practical examples
- Keep guides up-to-date with latest features
- Follow Markdown best practices
- Include troubleshooting sections where appropriate