Auditor MCP - Is there a way to run this not on the server itself?

Maybe I did something wrong, but I could not get the Auditor MCP searching to work in Claude when I loaded Claude and the MCP component on my PC where I have the auditor client installed.

I read a little more and saw the MCP server needed to be installed where the Auditor service was running … so I put the MCP server on the Auditor server. That doesn’t appear to work either because I believe Claude needs a physical local path the MCP executable.

So that means loading MCP and Claude on my server. Which I did for testing, it works, but it’s not an ideal situation long term.

Is there a way now (or could there be in the future) for the MCP component to run as a service on the server which could be accessed by the desktop AI component?

Hi Matt,

You’ve correctly identified the current limitation. At the moment, the Claude Desktop component and the MCP must be installed on the same machine.

This is because they are designed to communicate directly via a local process (stdio), not over a network.

To answer your question about the future: yes, we are actively considering a solution. We are exploring a move to a network-based communication protocol (HTTP + SSE). This change would make your ideal scenario possible—running MCP as a service on the server that can be accessed by Claude Desktop from your PC.

So, while it’s not possible today, it is a key improvement we are looking into for the future.

2 Likes

Excellent, thank you!

1 Like