Your own agent, working in Shingle
Connect Claude Code, Cursor or Codex. It works as you, and asks before anything goes out.





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.
Give it Shingle's address
Add https://shinglesites.com/api/v1/mcp wherever your agent takes an MCP server.
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.
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


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].
Yes. Shingle's MCP server is at https://shinglesites.com/api/v1/mcp. Claude Code, Cursor, Codex, Gemini CLI, VS Code, Windsurf and any other agent that takes an MCP server over HTTP can connect to it. An app signs in through your browser, and a script uses a key an admin makes on the Agents page.
Yes. A key reads and writes the same API the app uses, under /api/v1, with the key in an Authorization header. A read is a GET, and a change is a POST, PATCH or DELETE. Anything that would leave your team, such as publishing a site or emailing a customer, waits for a person's OK first.
Yes, after your OK. The request waits in Ready for you, where you can read exactly what Shingle will send. 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. Billing, people and keys always stay a person's.
No. Connecting an agent costs nothing, and neither does what it reads. Building and changing sites with AI uses your team's credits at the same prices as when you do it yourself, and each agent has a number of credits a day it may spend before it asks you.
An admin or the owner, with a confirmed email. Each agent works at the role of the person who connected it, and a team can have up to 20 connected apps and keys working at once.
Read next
- Ask DormerAsk about your leads, deals and sites in plain words.
- WorkflowsFollow-ups and reviews, with your OK where you want it.
- IntegrationsAnalytics, ads, webhooks, embeds and your own code.
- Web design agenciesMany client sites, one team, your brand to clients.
- Pricing7 days for $1, then one plan at $49 a month.
- Connect your own agentLet an agent you already use work in your team as you.
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.




