modelcontextprotocol/financial-services-interest-group
Watch
1
0
Fork
You've already forked financial-services-interest-group
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
financial-services-interest.../CONTRIBUTING.md
Sambhav Kothari 735294b15f Update link to publicly accessible doc 
Signed-off-by: Sambhav Kothari <skothari44@bloomberg.net>
2025-10-01 21:21:13 +01:00

3.9 KiB
Raw Blame History

Contributing to FSIG

Thank you for your interest in contributing to the MCP Financial Services Interest Group!

Quick Start

  1. Join the Community

    • Join the #financial-services-ig channel on MCP Discord
    • Introduce yourself and your interests
    • Review recent meeting notes

  2. Understand the Scope

    • Read the README for an overview
    • Review the CHARTER for mission and scope
    • Check GOVERNANCE for roles and decision-making

  3. Start Contributing

    • Attend bi-weekly meetings (no approval needed!)
    • Browse open issues
    • Open issues for new ideas or questions
    • Submit PRs for extensions, documentation, or improvements

General Guidelines

For general contribution guidelines, please follow the MCP Contributing Guide.

FSIG-Specific Considerations

Antitrust Compliance: All contributions and discussions must comply with the MCP Antitrust Policy.

Do NOT discuss:

  • Pricing, costs, or margins
  • Customer lists or strategies
  • Market division or competitive coordination
  • Confidential business information

Focus on:

  • Technical standards and specifications
  • Implementation approaches
  • Interoperability patterns
  • Documentation and testing

Extension Development

When developing MCP extensions for financial services:

  1. Start with a Proposal

    • Open an issue describing the extension
    • Discuss use cases and requirements
    • Get feedback before implementation

  2. Follow MCP Standards

    • Align with the MCP Specification
    • Use standard MCP patterns and conventions
    • Document deviations clearly

  3. Include Documentation & Examples

    • Clear README with purpose and usage
    • Working examples demonstrating the extension
    • Implementation notes and considerations

  4. Consider Broad Applicability

    • Could this extension benefit other domains?
    • Is there potential for promotion to core spec?
    • Document use cases beyond financial services

Proposing Core Spec Enhancements

If you believe an extension should be promoted to the core MCP spec:

  1. Gather Implementation Experience — Deploy in real scenarios and collect feedback
  2. Discuss with FSIG — Present at a meeting and get consensus from maintainers
  3. Contact Core Maintainer Liaison — Reach out to David Soria Parra
  4. Draft SEP — Follow the MCP SEP process with liaison support

See CHARTER.md for more details.

Communication Channels

  • Discord: #financial-services-ig — Real-time chat and questions
  • GitHub Issues: Proposals, bugs, and structured discussions
  • GitHub Discussions: Longer-form conversations
  • Meetings: Bi-weekly sync (see README)

Recognition

Active contributors are recognized in GOVERNANCE.md. After attending 2+ meetings or making substantive contributions, you can:

  • Self-nominate by opening a PR
  • Or a maintainer may add you

Getting Help

  • Ask in Discord — The #financial-services-ig channel is welcoming and responsive
  • Open an issue — For specific questions or proposals
  • Attend a meeting — Get face-time with maintainers and other contributors
  • Contact maintainers — See GOVERNANCE.md for current maintainers

Thank you for contributing to FSIG! Together we're making MCP more accessible and useful for financial services. 🎉