Improve Gram configuration, documentation and CI processes

[matthewelwell]

As per documentation written in notion here, we want to achieve the following tasks in order to create a more production-ready MCP server hosted on Gram.

• Audit OpenAPI spec descriptions (see Section 4)
  • Generate MCP specs only including exposed endpoints
• Configure custom domain (mcp.flagsmith.com)
• Create proper Gram environment, source, and MCP server configuration
  • Explore how to avoid user prefixing his token with Api-key:
    The authentication schema is picked up directly from the open-api specs. This is what make the MCP aware of authentication. They do not allow transformation (it could be done via a Custom Tool but that would double the consumption of tool calls.
    Possible solution would be to add a dedicated MCP authentication that would also ease monitoring
• Setup toolsets from generated tools
• Enable Dynamic Toolsets (as a start, to reduce token consumption for users)
• Curate tool list (remove unnecessary endpoints)
• Document user installation steps

[Zaimwa9]

For transparency, I added an item to explore whether the token header can be configured/transformed in Gram (and configure it in that case) or document how we could improve this UX on our side

[Zaimwa9]

1. Setting up locally
2. Update the doc
3. Remove the prefix (check custom gram mcp header)
4. Ask for the transformer on the auth