# VS Code and Market Monolith

Availability: Instructions published.
Connection status: Connection not available.

Last reviewed: 2026-08-28.

Plan a VS Code workflow with explicit server trust and configuration scope. A Market Monolith VS Code connection is not available in this release.

## The client model

The official [VS Code MCP documentation](https://code.visualstudio.com/docs/agent-customization/mcp-servers) describes server configuration and trust prompts. Configuration may live in a workspace or a user profile, and sharing or synchronization can change who can see it.

Review configuration before trusting a server. Do not place a secret in a shared workspace file or assume that a configuration file is private because it lives on your computer.

## Prepare the integration boundary

Choose the account and application identity independently of your editor login. List the permitted workspaces and results. Determine whether tool output is allowed in chat history, logs or shared development sessions.

Repository content and returned evidence cannot grant new account access.

## Required future behavior

A published connection needs a supported transport, authentication flow, tool inventory and revocation behavior. Paid work requires its own authority; an editor confirmation is not a payment approval.

This release documents only the authentication foundation and planned business outcomes. See [Capability availability](/docs/capability-availability).

## Availability and support

Instructions are published; connection is not available. Microsoft owns VS Code client behavior, trust controls and settings synchronization. Market Monolith owns any future public connection contract. No extension, MCP URL or install step is offered here.