Documentation menu

MCP Overview

anymrkt exposes a single MCP (Model Context Protocol) server that unifies every product into one surface an AI agent can connect to. The server runs as an HTTP endpoint at /mcp, authenticated with a bearer token. Any MCP-compliant client can connect.

The three layers

1. MCP Server — what anymrkt runs today

Built on @modelcontextprotocol/sdk, our server registers 119 tools across 7 product categories and serves them over HTTP. The server is per-request: each connection resolves a ResolvedMcpToken from the bearer header, and the tool list is filtered based on that token's permissions and optional tool_filters allow-list.

CategoryToolsProducts
Listings & brand14Inventory, conversations, brand content
Builder6Page editor — sections, templates, layout
Scheduler9Meeting types, availability, bookings
GRAIL3Property records, GIS signals, imagery
MACP38Boards, tasks, sessions, connectors, webhooks
Kanban29Kanban boards, cards, journeys, sprints, epics
Studio20API keys, connectors, usage analytics

2. MCP Client — agents connecting to anymrkt

This is the direction you use today. Configure your agent with our HTTP endpoint and a bearer token.

See the transport guide for per-client setup.

3. MCP App — interactive UI inside agents (planned)

MCP 2026 introduced MCP Apps: interactive applications that render UI inside the AI client. anmrkt does not yet ship an MCP App, but the architecture is ready. Potential apps:

  • Builder page preview inside Claude Code — edit, see a live render, confirm
  • Calendar availability grid — click to toggle open/closed blocks
  • Kanban board view — drag cards, the agent proposes moves, you confirm
  • GRAIL map with signal markers — click a pin for parcel details

Security model at a glance

LayerMechanismPrevents
TransportDPoP optional bindingStolen bearer token is useless without the client key
AuthPer-token permissions + brand scopingToken for brand A can't touch brand B
WritesPermission-gatedAgent can't act outside granted permissions
Public actionsconfirm: true requiredCan't happen as a side effect
All mutationspreview: true dry-runAgent shows what it will change first
Auditmcp_operations log + revert_runFull revert per agent session
Tool filteringPer-token tool_filtersAgent only sees tools you enabled