Skip to main content

​
Authors & Contributors

SEC Edgar MCP is built and maintained by a dedicated team of developers and contributors from around the world.

​
Core Team

​
Contributors

We’re grateful to all the contributors who have helped make SEC Edgar MCP better:

​
How to Contribute

We welcome contributions from developers of all skill levels! There are many ways to contribute to SEC Edgar MCP:

​
🐛 Bug Reports

Found a bug? Please open an issue on our GitHub repository with:
  • A clear description of the issue
  • Steps to reproduce the problem
  • Expected vs actual behavior
  • Your environment details (Python version, OS, etc.)

​
💡 Feature Requests

Have an idea for a new feature? We’d love to hear it! Open an issue and describe:
  • The problem you’re trying to solve
  • Your proposed solution
  • Any alternative approaches you’ve considered

​
🔧 Code Contributions

Ready to contribute code? Here’s how:
1

Fork the repository

Fork the SEC Edgar MCP repository to your GitHub account.
2

Clone your fork

git clone https://github.com/your-username/sec-edgar-mcp.git
cd sec-edgar-mcp
3

Create a feature branch

git checkout -b feature/your-feature-name
4

Set up development environment

python -m venv .venv
source .venv/bin/activate  # On Windows: .venv\\Scripts\\activate
pip install -e ".[dev]"
5

Make your changes

Implement your feature or bug fix, following our coding standards.
6

Test your changes

pytest
mypy sec_edgar_mcp/
ruff check .
7

Submit a pull request

Push your changes and create a pull request with a clear description.

​
📝 Documentation

Help improve our documentation by:
  • Fixing typos or unclear explanations
  • Adding examples and use cases
  • Translating content
  • Improving API documentation

​
💬 Community Support

Help other users by:
  • Answering questions in GitHub discussions
  • Sharing your use cases and examples
  • Writing blog posts or tutorials

​
Development Guidelines

When contributing code, please follow these guidelines:

​
Code Style

  • Use Black for code formatting
  • Follow PEP 8 style guidelines
  • Use type hints for all functions and methods
  • Write comprehensive docstrings

​
Testing

  • Write tests for new features and bug fixes
  • Ensure all existing tests pass
  • Aim for high test coverage
  • Use descriptive test names

​
Documentation

  • Update documentation for any API changes
  • Include docstrings for all public methods
  • Add examples for new features
  • Update the changelog

​
Recognition

All contributors are recognized in our:

​
Acknowledgments

Special thanks to:
  • The SEC for providing free access to EDGAR filings data
  • EdgarTools library maintainers for the excellent Python SEC data toolkit
  • Anthropic for the Model Context Protocol specification
  • All our users who provide feedback and help improve the project

​
Contact

Have questions about contributing? Reach out to:
By contributing to SEC Edgar MCP, you agree that your contributions will be licensed under the same license as the project.
⌘I