WIP: allow for restrictions and enable/disable of API endpoints

[cooktheryan]

Currently there is no way to enable or disable specific endpoints. This is fine when using claude but when attempting to use smaller models the amount of tools available may overwhelm smaller models.

[cooktheryan]

A couple screenshots using the disabling feature defined in the test data

[mattt]

Hi @cooktheryan. Thanks so much for your PR!

I totally agree that reducing the number of tools made available to the MCP server is important — especially for smaller models.

The design philosophy with emcee is to keep it small and sharp, favoring composition with other tools. Our prescribed approach is described in the README under "Transforming OpenAPI Operations":

You can transform OpenAPI specifications before passing them to emcee using standard Unix utilities. This is useful for:

• Selecting specific endpoints to expose as tools with jq or yq
• Modifying descriptions or parameters with OpenAPI Overlays
• Combining multiple specifications with Redocly

The approach this PR takes, of using a configuration file, is totally valid approach. Without weighing in on the specific implementation here, I'd be hesitant to create new API surface area if it's unnecessary.

When configuration files are warranted, my go-to is viper, which pairs nicely with cobra.