Skip to content

Your own agent, working in Shingle

Connect Claude Code, Cursor or Codex. It works as you, and asks before anything goes out.

Agents: Dormer, two connected apps and three keys, one chosen, with what it does alone and a request waiting for your OK

How to connect one

An app signs in with nothing to paste. A script, or a tool that can't sign in, uses a key.

  1. Give it Shingle's address

    Add https://shinglesites.com/api/v1/mcp wherever your agent takes an MCP server.

  2. Sign in and choose what it may do

    Shingle opens in your browser. Pick read only or read and work, and the credits it may spend a day.

  3. Ask it something

    Try "Which leads came in this week?" and it answers from your team's own records.

What your agent can do

It works under your role, and asks before anything leaves your team.

Reads

  • Your sites and how each is doing
  • Forms, bookings, customers and the Inbox
  • Deals, prospects, workflows and Activity

Does at once

  • Builds a site, changes one or restores a version
  • Writes a post, a newsletter or a reply for you to send
  • Notes, tasks, deals, Radar searches and demos

Asks you first

  • Publishing a site or taking it down
  • Sending anything to a customer or a client
  • Deleting, domains, webhooks and workflows

Stays yours

  • Billing and the plan
  • People and their roles
  • Keys, connected apps and every OK

Your OK, before it goes out

When your agent wants to publish a site, reply to a customer or delete something, the request waits in Ready for you and on the agent's own page in Agents. It says what the agent wants to do, which app or key asked and why it waits, and you can read exactly what Shingle will send. OK runs it once, as you. No means it never runs.

If you keep saying OK to the same thing, an admin can let that agent do it without asking, up to a number of times a day. Publishing a site, publishing a post, replying to or emailing a customer, adding a booking, sending a client report, making a review link and sending a test newsletter can each be handed over this way.

  • A request waits one day, then expires
  • Each agent has credits a day it may spend before it asks
  • Activity names the agent and the person it works for
An agent's request in Ready for you: what it wants to do, who asked, what Shingle will send, and No or OK

It works as you

An agent reads and does only what the person who connected it may.

  • Your role is its role

    If your role changes, your agent's changes with it. If you leave the team, it stops.

  • Customers' words stay data

    What customers write is marked as written outside your team. For 15 minutes after, it asks first.

  • A practice team to try it in

    Sample data where nothing is sent, published or billed, so your agent can try everything.

For developers

Shingle's MCP server is at https://shinglesites.com/api/v1/mcp. It answers the Model Context Protocol over HTTP and keeps no session. An app finds how to sign in from the address itself, using the standard sign-in for MCP servers (OAuth 2.1 with PKCE), and registers itself. A script sends a key in the Authorization header instead.

The same key works with Shingle's API directly. A read is a GET under /api/v1, and a change is the same POST, PATCH or DELETE a click in Shingle makes. A change that waits for a person answers 403 with the code approval_required, the request's id and where a person answers it. Help lists every route an agent can call and how each one runs.

  • Up to 20 connected apps and keys per team
  • A key lasts 30 days, 90 days or a year; a connected app, a year
  • 600 calls a minute for each agent

Common questions

Can't find your answer? Read Shingle Help or email [email protected].

Build your first site

Start from a Google listing or a few notes. Demos usually take 5–15 minutes.

7 days for $1, then $49 a month. Cancel any time.