# Claude Code and Market Monolith

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

Last reviewed: 2026-08-28.

Plan a Claude Code workflow with a clear project and secret boundary. A Market Monolith Claude Code connection is not available in this release.

## The client model

The official [Claude Code MCP documentation](https://code.claude.com/docs/en/mcp) describes remote and local servers, configuration scopes and environment-variable expansion. Project configuration can be shared with collaborators; local configuration has a different visibility boundary.

These are client capabilities, not evidence of a Market Monolith server or supported install command.

## Prepare a safe project

Document which application will own calls and which account's resources it may reach. Decide whether configuration belongs to an individual or a shared project. Keep secret values out of checked-in files and review any shared server configuration before trusting it.

A repository instruction cannot authorize new spending, disclose private sources or widen access.

## Future execution boundaries

Separate read-only result retrieval from research, outreach, purchases and other actions. A tool invocation should preserve the approved scope and identity, not silently create prerequisites.

The initial authentication check is not an MCP tool connection. See [Authentication](/docs/authentication) and [MCP concepts](/docs/mcp).

## Availability and support

Instructions are published; connection is not available. Anthropic owns Claude Code's runtime and configuration behavior. Market Monolith owns any future published MCP contract. This page intentionally contains no server address, package or command to install a Market Monolith integration.