Will there be MCP coverage?

[BradKML]

I see that other tools have similar functions, but they do include MCP adaptors
Cross-reference https://github.com/intellectronica/ruler

[danielmeppiel]

I see that other tools have similar functions, but they do include MCP adaptors

Cross-reference https://github.com/intellectronica/ruler

There is MCP support already and an adapter architecture. Currently tested with Copilot CLI and Codex CLI.

Ideally we should build on top of projects like ruler instead of reinventing the wheel.

[RobCannon]

@danielmeppiel I just wanted you to know that I have read your blog post many times trying to internalize this as I try to create a set of standardized instructions and rules that we can deploy to each of our repos. But I kept wondering if an MCP server might be a better way to centralize something like this, and here is my answer!
I think GitHub should offer this as a feature/service for organizations.

[RobCannon]

@danielmeppiel Hmm, I got this discussion wrong. I thought it was about supporting exposing this information via MCP, not configuring other MCP servers.

So, my original thought still stands: Would it make sense to package this information into a container that exposes this info via the MCP protocol? That way, I could configure MANY repos to use this server and I only have to update this server once to deliver those updates to many repos. The downside is that I have to host that, but that is not a big deal for my org. But if delivering instructions via MCP is valid, then I still think a GitHub service that simplifies this would be a great offering.

The APM solution is more desirable for us than ruler, because it does support storing this info in once place and distributing it. We have a "maintance" job that runs on all of our repos where we can easily add a step to automate 'apm install' to get updates push to developers.

[danielmeppiel]

@RobCannon great thoughts. Let me see if I can recap and capture your use case:

• You want to be able to centralize in one single place your org's instructions, reusable prompts, etc
• If you update them, you want these updates to be propagated immediately without intervention

If that's correct, I agree with the problem is there and it is worth solving.

I am trying now to match that to a solution. At the moment, APM allows you to centrally store your instructions and prompts in a GitHub or Azure DevOps repository. If you update the instructions/prompts in that repository, your users just need to run apm install && apm compile to get the updates. Projects which would want to carefully evaluate the impact of any new updates you ship could "cling" to an older commit hash with APM and wait a bit before updating to your latest changes.

In contrast, if you have an MCP server, aside of hosting it as a server on some infrastructure, you'd need your users to prompt an agent and then trust the agent will do the actual tool calling that's needed, correct?

I am trying to figure out where an MCP server actually bring value to this problem space.