[FEATURE] Ability to run locally against the emulator

[TWolversonReply]

Feature Description

I am trying to set up an entirely local development approach including CosmosDb accessed by Agents using the Cosmos MCP. The blocker for this seems to be that the MCP Toolkit uses DefaultAzureCredential for both the Foundry embedding access and the CosmosClient, and even when a valid AzureCli (for example) credential is available, the token requested is for a scope https://localhost/.default, which Entra will never recognise.

Problem or Use Case

Ability to configure a local MCP with a local instance of CosmosDb run by the emulator.

Proposed Solution

An alternative credential path for both the CosmosDb and the embeddings client, to use a connection string with a default key and whatever authentication model that Foundry Local supports, respectively

Benefits

Who would benefit from this feature?

• Microsoft Foundry users
• MCP client developers
• Enterprise deployments
• Local development
• Vector search scenarios
• Other: ___________

Additional Context

Add any other context, screenshots, mockups, or examples about the feature request here.

Priority

How important is this feature to you?

• Critical - Blocking my use of the toolkit
• High - Would significantly improve my workflow
• Medium - Nice to have
• Low - Minor improvement

---

Checklist:

• I have searched existing issues to avoid duplicates
• I have clearly described the use case and benefits
• I have provided examples where applicable