> ## Documentation Index
> Fetch the complete documentation index at: https://sec-edgar-mcp.amorelli.tech/llms.txt
> Use this file to discover all available pages before exploring further.

# Authors & Contributors

> Meet the people behind SEC Edgar MCP

# Authors & Contributors

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

## Core Team

<CardGroup cols={1}>
  <Card title="Stefano Amorelli" icon="user" href="mailto:stefano@amorelli.tech">
    **Project Creator & Lead Maintainer**

    📧 [stefano@amorelli.tech](mailto:stefano@amorelli.tech)
  </Card>
</CardGroup>

## Contributors

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

<CardGroup cols={2}>
  <Card title="Harin Lee" icon="code" href="https://github.com/harinlee83">
    **Contributor**

    🔗 [GitHub](https://github.com/harinlee83)\
    📧 [harinlee83@gmail.com](mailto:harinlee83@gmail.com)
  </Card>

  <Card title="Davide Rutigliano" icon="code" href="https://github.com/DavideRutigliano">
    **Contributor**

    🔗 [GitHub](https://github.com/DavideRutigliano)
  </Card>

  <Card title="JC (Jonathan Chen)" icon="code" href="https://github.com/dijonkitchen">
    **Contributor**

    🔗 [GitHub](https://github.com/dijonkitchen)\
    📧 [jc@dijonkitchen.org](mailto:jc@dijonkitchen.org)
  </Card>

  <Card title="Scott Goley" icon="code" href="https://github.com/sgoley">
    **Contributor**

    🔗 [GitHub](https://github.com/sgoley)\
    📧 [scottmgoley@gmail.com](mailto:scottmgoley@gmail.com)
  </Card>

  <Card title="GERWARIC" icon="code" href="https://github.com/gerwaric">
    **Contributor**

    🔗 [GitHub](https://github.com/gerwaric)\
    📧 [gerwaric@gmail.com](mailto:gerwaric@gmail.com)
  </Card>
</CardGroup>

## 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](https://github.com/stefanoamorelli/sec-edgar-mcp) 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:

<Steps>
  <Step title="Fork the repository">
    Fork the [SEC Edgar MCP repository](https://github.com/stefanoamorelli/sec-edgar-mcp) to your GitHub account.
  </Step>

  <Step title="Clone your fork">
    ```bash theme={null}
    git clone https://github.com/your-username/sec-edgar-mcp.git
    cd sec-edgar-mcp
    ```
  </Step>

  <Step title="Create a feature branch">
    ```bash theme={null}
    git checkout -b feature/your-feature-name
    ```
  </Step>

  <Step title="Set up development environment">
    ```bash theme={null}
    python -m venv .venv
    source .venv/bin/activate  # On Windows: .venv\\Scripts\\activate
    pip install -e ".[dev]"
    ```
  </Step>

  <Step title="Make your changes">
    Implement your feature or bug fix, following our coding standards.
  </Step>

  <Step title="Test your changes">
    ```bash theme={null}
    pytest
    mypy sec_edgar_mcp/
    ruff check .
    ```
  </Step>

  <Step title="Submit a pull request">
    Push your changes and create a pull request with a clear description.
  </Step>
</Steps>

### 📝 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](https://black.readthedocs.io/) for code formatting
* Follow [PEP 8](https://pep8.org/) 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:

* [AUTHORS](https://github.com/stefanoamorelli/sec-edgar-mcp/blob/main/AUTHORS) file
* [CONTRIBUTORS](https://github.com/stefanoamorelli/sec-edgar-mcp/blob/main/CONTRIBUTORS) file
* Release notes and changelogs

## 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:

* **Primary Contact:** Stefano Amorelli ([stefano@amorelli.tech](mailto:stefano@amorelli.tech))
* **GitHub Issues:** [Report issues or ask questions](https://github.com/stefanoamorelli/sec-edgar-mcp/issues)
* **Discussions:** [Join community discussions](https://github.com/stefanoamorelli/sec-edgar-mcp/discussions)

***

<Note>
  By contributing to SEC Edgar MCP, you agree that your contributions will be licensed under the same license as the project.
</Note>