Skip to main content
Q-Code

Accounts and agents · 4 modules

What are the accounts and agents modules?

The accounts and agents modules are the four behind who can act on a site and how a machine reaches it: admin, auth, Google and agent access.

Admin and auth decide who can change anything, Google connects the site to Business Profile, Search Console and review data, and agent access turns the site into an MCP server so an assistant can call its tools instead of scraping its pages.

Why this group exists

What accounts and agents is for.

Every other module needs somewhere to be managed and somebody allowed to manage it. Admin is the dashboard every panel adds itself to, and auth is the sign-in that gates it, extended to a members area when a project needs logged-in visitors rather than only a logged-in owner.

The other two are here because a growing share of visits are not from a browser at all. Google still decides most of what a person finds, so the Google module keeps Business Profile, Search Console and reviews in step with the site, and agent access publishes the same information as tools an assistant can call rather than pages it has to guess at.

The modules

4 in this group.

Admin dashboard

@ccd/admin

The private dashboard every other module adds its panel to, with one login for the owner.

  • Adds a card to the dashboard for each installed module that has something worth summarising.
  • Groups every panel into a consistent navigation, so a new module never needs its own menu.
  • Sits behind noindex, nofollow and the owner’s own session, never a public page.

Sign-in and members

@ccd/auth

Sign-in for the site’s owner and, where a project needs it, its members.

  • Gates the admin panel behind a real session rather than a shared password.
  • Extends to a members area when a project needs logged-in visitors, not only a logged-in owner.
  • Holds nothing itself; sessions and identities live in the project’s own database.

Google connections

@ccd/google

Connects the site to Google: Business Profile, Search Console and review data, in one panel.

  • Pulls reviews and ratings in for the testimonials module to place, rather than asking for them twice.
  • Verifies the site with Search Console and reports what Google itself has indexed.
  • Keeps opening hours and location in step between the site and the Business Profile listing.

Agent access

@ccd/agent-api

Makes the site an MCP server, so an assistant can call its tools instead of scraping its pages.

  • Derives its tools from the modules already installed, so it never offers a door that leads nowhere.
  • Publishes the discovery cards agents look for, and registers the same tools inside the browser.
  • Stays off until you switch it on, and gates writes behind consent and a rate limit per email address.

Q&A

Questions about the accounts and agents modules

Is the admin panel public?

No. It sits behind noindex, nofollow and the owner’s own session, and is never linked from a public page.

What does the auth module add beyond the owner’s own login?

A members area, when a project needs one: logged-in visitors with their own accounts, gated content, and sessions held in the project’s own database rather than a shared one.

What is the difference between the Google module and agent access?

Google connects the site to Business Profile, Search Console and review data, aimed at a person searching. Agent access publishes an MCP server at /mcp that an assistant calls directly and gets data back from. Both are off until switched on.

The other groups

Where to look next.

  • Foundations

    Visibility engine, Analytics, Security baseline, Legal pages, Cookie consent.

  • Content

    Self-improving blog, FAQ, Testimonials, Gallery, Footer.

  • Catalogue and booking

    Listings, Booking.

  • Engagement

    Contact form and inbox, Newsletter, Social profiles, AI chat.

Describe the feature, not the module.

You are not expected to know which of these you need. Say what the site should do and the build reaches for the parts that already exist.