Monarchic LLC logo Monarchic LLC

MCP tutorial

Connect
A Client

Monarchic MCPs are accessed through account-scoped routes. This guide shows the setup shape without publishing private endpoints or implying same-day activation from the public website.

View Products Join Waitlist

Account

Get gated access

Join the waitlist or use an approved account. The dashboard shows the MCP routes and adapter packages enabled for that account.

Key

Create an MCP API key

Use a scoped key for agent clients. The adapter sends it as bearer auth; Monarchic still enforces tenant access and entitlements server-side.

Client

Paste the MCP config

Use the dashboard snippet for your client. It pins the route package, API base URL, and credential environment variable.

Verify

Run a small read-only task first

Start with initialize, tools/list, or a read-only tool call before letting an agent mutate files, browse authenticated pages, or trigger workflows.

Access model

Hosted product, small adapter.

Dashboard-issued config

Hosted route

The MCP capability runs on Monarchic AWS

The product is account-scoped hosted execution, metering, receipts, and route controls. Your client calls Monarchic infrastructure for each workflow.

Adapter

Clients launch a tiny registry package

The package handles stdio transport, auth headers, retries, and version checks. It contains no product logic and should not contain secrets.

Artifacts

S3 is supporting infrastructure

S3 can store receipts, release artifacts, checksums, or binary outputs. Normal MCP access starts from the dashboard-issued client config.

Adapter example

One route, one package.

RepoIntel uses @monarchic-ai/repointel-mcp. Other hosted MCPs follow the same pattern, such as @monarchic-ai/explicitmem-mcp and @monarchic-ai/browserops-mcp.

Supported clients

Claude Desktop Claude Code Codex Cursor Continue.dev Cline Windsurf VS Code Copilot Zed Goose

The dashboard renders the right wrapper for each client. The underlying server definition remains the same: launch pnpm dlx, pass the route package, and provide the hosted API credential in environment variables.

Generic MCP JSON

Many clients use a top-level mcpServers object. Keep the package name route-specific, and replace the credential placeholder with the generated API key. 

{
  "mcpServers": {
    "repointel": {
      "command": "pnpm",
      "args": ["dlx", "@monarchic-ai/repointel-mcp"],
      "env": {
        "MONARCHIC_API_BASE_URL": "https://api.monarchic.io",
        "MONARCHIC_API_KEY": "<copy-from-dashboard>"
      }
    }
  }
}

Codex TOML

Codex uses TOML instead of JSON. The same hosted adapter contract still applies: package-registry launch, hosted API base URL, and scoped API key. 

[mcp_servers.repointel]
command = "pnpm"
args = ["dlx", "@monarchic-ai/repointel-mcp"]
startup_timeout_sec = 30
tool_timeout_sec = 120

[mcp_servers.repointel.env]
MONARCHIC_API_BASE_URL = "https://api.monarchic.io"
MONARCHIC_API_KEY = "<copy-from-dashboard>"

First workflows

Start small, then expand.

Read Research

ExplicitMem

Store and retrieve a scoped project note, then inspect the returned receipt.

Product Evidence

RepoIntel

Ask for repository context around one file or symbol before planning a code change.

Product Evidence

BrowserOps

Observe one public page and check screenshots, console output, and network notes.

Product Evidence

Validate

Confirm the client can list available tools and run one scoped operation before handing it a broad task.

Observe

Keep receipts, screenshots, logs, or returned evidence attached to the work so reviewers can inspect the result. Paid/test accounts should see hosted MCP usage in the dashboard after a billable tool call.

Limit

Treat each MCP as a bounded tool. Product and research pages name the scope; do not turn a narrow proof into a universal claim.

Access boundary

This tutorial is a setup model for gated access. It does not expose private routes, credentials, or instant activation. Join the waitlist for account onboarding and route availability updates.

Join Waitlist