# Claude and Market Monolith

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

Last reviewed: 2026-08-28.

Plan a Claude connection without confusing a remote connector with a local tool. A Market Monolith Claude connection is not available in this release.

## The client model

Anthropic's [remote-connector guidance](https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp) distinguishes remote MCP connections from local desktop servers. Remote connector traffic is handled through Anthropic infrastructure, including when the user is in a desktop client.

That distinction matters for private business sources, customer data and regional restrictions. A local-looking interface is not proof that processing stays local.

## Decide the data boundary

Before a future setup, record the account, application and allowed resources. Determine whether the client may receive raw source material or only a customer-safe result. Include workspace sharing and organization approval requirements.

Keep secrets out of conversations. Never reuse a provider credential as a Market Monolith key.

## Required future contract

A usable connection would need a published server address, authentication method, authorized tool list and revocation behavior. It must distinguish reads, governed work and paid approval. This release supplies none of those connection details.

Use [Security, privacy and data ownership](/docs/security-privacy-ownership) when deciding which evidence may be shared.

## Availability and support

Instructions are published; connection is not available. Anthropic owns Claude's connector UI and organization controls. Market Monolith owns any future public connector contract. No native listing or account-level connection has been verified.