Add an MCP Server Manager

[gopar]

Right now, a connection is reset every time a new Coder instance is created (which is extremely frequently). To better handle resources and make switching modes faster (not waiting on establishing MCP server(s) connection again), we'll delegate all this to a manager that we can just pass around.

[dwash96]

So this block already prevents the recreation/reconnection to mcp servers that have already been declared and added to the list

[dwash96]

I generally support having a central MCP manager but there are a few things it should do/interventions we should make to be considered complete:

Minimum:

• You probably already do this, but the MCP manager should maintain structures of both the available servers and the server a specific tool name corresponds to and expose simple methods for accessing these structures so the act of MCP server tool calling is less iterative inside of base_coder.py

Possibly another PR

• MCP configuration blocks should have a "enabled" flag that determines if they start on load or not
• The MCP manager should have enable/disable commands (or probably load/remove for naming consistency with skills) that can remove an MCP server/it's associated tools to and from the returned server list and tools list
• We should add user facing commands for these two internal methods

Possibly yet another PR

• Add one more "/register-mcp" command that can accept either a configuration json or yml file path that can perform the registration for any server configurations inside of it, and NOT making the immediately available, but available to load

[gopar]

Right now, we have a base implementation that sets the ground for separate PRs. I dont want to add too much into a single PR.

For the rest of the points, we can create tickets and track them via that way.

[gopar]

Also, can we squash these commits when we merge them? There's no history loss here if its all condensed into a single commit (i believe github has a setting to allow this when merging PRs to make it easier)

[gopar]

Still valid since this is a minimal PR to get the codebase using the mcp manager

[dwash96]

Hey, there's quite a decent surface area still expecting and accessing "mcp_servers" vs "mcp_manager"

Which causes errors with starting up in agent mode

[gopar]

Hey, there's quite a decent surface area still expecting and accessing "mcp_servers" vs "mcp_manager"
Which causes errors with starting up in agent mode

Oh! Weird how I missed that. The only one that is an actual issue is the agent_coder.py file, the other ones are related to passing the arg mcp_servers which is still required. I updated agent related code, and tested it out. Its able to complete its task w/ no errors.